public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
	Jagadeesh Ujja <jagadeesh.ujja@arm.com>
Cc: Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [edk2-devel] [edk2] [PATCH v2 edk2-platforms] Platform/ARM/Drivers: Add Nor Flash Driver
Date: Mon, 29 Apr 2019 08:52:46 +0200	[thread overview]
Message-ID: <CAKv+Gu93L7=n+8b_t5p88+TLGkur=Pnn3NSY+7WRcCgxR+kfEQ@mail.gmail.com> (raw)
In-Reply-To: <CADpYukYbf=eW6hHiez5uBMRrbRH5Zm+UD6y_eEsm8n-HMUx_CQ@mail.gmail.com>

On Mon, 29 Apr 2019 at 07:59, Jagadeesh Ujja <jagadeesh.ujja@arm.com> wrote:
>
> hi Ard
>
> On Wed, Apr 24, 2019 at 6:37 PM Ard Biesheuvel
> <ard.biesheuvel@linaro.org> wrote:
> >
> > On Wed, 24 Apr 2019 at 11:05, Jagadeesh Ujja <jagadeesh.ujja@arm.com> wrote:
> > >
> > > Fwd to new EDKII development mailing list.
> > >
> > > hi Ard,
> > >
> > > Sorry about missing your previous comment and adding here.
> > >
> > >  "Hello Jagadeesh,
> > >
> > >  Why are you moving this driver into edk2-platforms? I'd prefer to have
> > >
> > > it alongside the non-MM version instead.
> > >
> > > That would allow us to share a lot more code between the two versions."
> > > -----------------
> > >
> > > my Point of view:
> > >
> > > In ArmPlatformPkg/Drivers/NorFlashDxe driver supports block I/O and
> > > disk  I/O protocols.
> > > In case of StandaloneMM norflash driver the block I/O and disk I/O
> > > protocols are not required
> > >
> > > We don’t want to remove support of block I/O and disk I/O protocols in
> > > “ArmPlatformPkg/Drivers/NorFlashDxe”
> > > In this case “NOR_FLASH_INSTANCE” is different in both
> > > drivers(DXE/STANDALONEMM). So we end up with  having 2 different
> > > drivers.
> > >
> > > Even if we want to share common code then we end up with multiple
> > > files as  “NOR_FLASH_INSTANCE” is used in almost all files
> > > Ex: “NorFlash.c”  “NorFlash.h” NorFlashFvb.c
> > > In this case “NorFlash.c”  will have 2 copies one used by DXE and
> > > other by STANDALONE_MM driver
> > >
> > > So instead of having 2 different drivers in one place
> > > “ArmPlatformPkg/Drivers/NorFlashDxe”
> > > added a new refactored nor flash driver in "Platform/ARM/Drivers"
> > >
> > > I am not sure if any other platform is using
> > > “ArmPlatformPkg/Drivers/NorFlashDxe” and may require block I/O and
> > > disk  I/O protocols
> > > if we remove “support of block I/O and disk  I/O protocols” then we
> > > can share the common code easily.
> > >
> >
> > I see your point.
> >
> > The only reason you need block i/o and disk i/o is to use ordinary
> > partition and filesystem drivers. I guess Juno uses this for its magic
> > filesystem? If not, I'd be glad to get rid of it.
> >
> >
> Yes  "block i/o and disk i/o  of “ArmPlatformPkg/Drivers/NorFlashDxe”
> driver is used even
> in RD-platforms(edk2-platforms/Platform/ARM/SgiPkg/)(and JUNO) to list
> partition. we don't want to break
> legacy and want to have separate
> "Platform/ARM/Drivers/StandaloneMmNorFlash/" driver.
>

In that case, could we move the existing code into
edk2-platforms/Platform/ARM first? And then rip out the block i/o and
disk i/o parts from the common driver?

Leif, any thoughts?

  reply	other threads:[~2019-04-29  6:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 13:10 [PATCH v2 edk2-platforms] Platform/ARM/Drivers: Add Nor Flash Driver Jagadeesh Ujja
     [not found] ` <CADpYukZHE6NY-U=EycJBVGbQ-XcxXpeT9w6svzWMePjvQXFciQ@mail.gmail.com>
2019-04-24  9:05   ` [edk2] " jagadeesh.ujja
2019-04-24 13:06     ` [edk2-devel] " Ard Biesheuvel
2019-04-29  5:59       ` Jagadeesh Ujja
2019-04-29  6:52         ` Ard Biesheuvel [this message]
2019-04-29  7:58           ` Leif Lindholm
2019-04-29  8:17             ` Ard Biesheuvel
2019-04-29  8:52               ` Leif Lindholm
2019-04-29 12:21                 ` Jagadeesh Ujja
2019-05-02  8:48                   ` Ard Biesheuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKv+Gu93L7=n+8b_t5p88+TLGkur=Pnn3NSY+7WRcCgxR+kfEQ@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox