public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Jordan Justen <jordan.l.justen@intel.com>
To: "Duran, Leo" <leo.duran@amd.com>,
	"'Laszlo Ersek'" <lersek@redhat.com>,
	"Gao, Liming" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Singh, Brijesh" <brijesh.singh@amd.com>,
	"Fan, Jeff" <jeff.fan@intel.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Ma, Maurice" <maurice.ma@intel.com>,
	"Agyeman, Prince" <prince.agyeman@intel.com>,
	"Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"Steele, Kelly" <kelly.steele@intel.com>,
	"Wei, David" <david.wei@intel.com>,
	 "Guo, Mang" <mang.guo@intel.com>
Subject: Re: [PATCH v3 0/4] BaseIoFifoLib
Date: Fri, 06 Jan 2017 16:49:38 -0800	[thread overview]
Message-ID: <148375017874.13659.3185969071926290103@jljusten-ivb> (raw)
In-Reply-To: <DM5PR12MB124386125FE587D09920245DF9630@DM5PR12MB1243.namprd12.prod.outlook.com>

On 2017-01-06 07:23:47, Duran, Leo wrote:
> 
> 
> > -----Original Message-----
> > From: Laszlo Ersek [mailto:lersek@redhat.com]
> > Sent: Friday, January 06, 2017 5:12 AM
> > To: Gao, Liming <liming.gao@intel.com>; Duran, Leo <leo.duran@amd.com>;
> > edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
> > Cc: Singh, Brijesh <brijesh.singh@amd.com>; Justen, Jordan L
> > <jordan.l.justen@intel.com>; Fan, Jeff <jeff.fan@intel.com>; Kinney,
> > Michael D <michael.d.kinney@intel.com>; Ma, Maurice
> > <maurice.ma@intel.com>; Agyeman, Prince <prince.agyeman@intel.com>;
> > Ni, Ruiyu <ruiyu.ni@intel.com>; Steele, Kelly <kelly.steele@intel.com>; Wei,
> > David <david.wei@intel.com>; Guo, Mang <mang.guo@intel.com>
> > Subject: Re: [PATCH v3 0/4] BaseIoFifoLib
> > 
> > On 01/06/17 07:02, Gao, Liming wrote:
> > > Leo:
> > > FifoIo is one width type of EFI_CPU_IO_PROTOCOL_WIDTH. So, how about
> > > add new APIs into IoLib together with other Io APIs? If so, no new
> > > library class is required. Platform DSC files are not required to be
> > > changed.
> > 
> > But then all of the IoLib instances will have to be extended too:
> > 
> > IntelFrameworkPkg/Library/DxeIoLibCpuIo/DxeIoLibCpuIo.inf
> > MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsic.inf
> > MdePkg/Library/DxeIoLibCpuIo2/DxeIoLibCpuIo2.inf
> > MdePkg/Library/DxeIoLibEsal/DxeIoLibEsal.inf
> > MdePkg/Library/PeiIoLibCpuIo/PeiIoLibCpuIo.inf
> > MdePkg/Library/SmmIoLibSmmCpuIo2/SmmIoLibSmmCpuIo2.inf
> > 
> > Thanks,
> > Laszlo
> > 
> [Duran, Leo] Correct.
> As I mentioned, one of the reasons for the new IoFifo library is to
> be able to override it without having to duplicate the complete
> IoLib.
> 

I agree with Liming about adding the functions to IoLib instead.

Perhaps a PCD could be added to control if rep i/o instructions are
used.

-Jordan


  reply	other threads:[~2017-01-07  0:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 21:49 [PATCH v3 0/4] BaseIoFifoLib Leo Duran
2017-01-05 21:49 ` [PATCH v3 1/4] MdePkg: Add BaseIoFifoLib library Leo Duran
2017-01-05 21:49 ` [PATCH v3 2/4] Modify .DSC files that include UefiCpuPkg/CpuIo2Dxe/CpuIo2Dxe.inf Leo Duran
2017-01-06 11:23   ` Laszlo Ersek
2017-01-06 15:28     ` Duran, Leo
2017-01-05 21:49 ` [PATCH v3 3/4] Modify UefiCpuPkg/CpuIo2Dxe to use new BaseIoFifoLib library Leo Duran
2017-01-05 21:49 ` [PATCH v3 4/4] Modify QemuFwCfgLib " Leo Duran
2017-01-06 11:36   ` Laszlo Ersek
2017-01-06 15:31     ` Duran, Leo
2017-01-06  6:02 ` [PATCH v3 0/4] BaseIoFifoLib Gao, Liming
2017-01-06 11:12   ` Laszlo Ersek
2017-01-06 15:23     ` Duran, Leo
2017-01-07  0:49       ` Jordan Justen [this message]
2017-01-07 17:16         ` Duran, Leo
2017-01-09  3:10           ` Gao, Liming
2017-01-09 14:22             ` Duran, Leo
2017-01-09 14:30               ` Duran, Leo
2017-01-09 14:36                 ` Duran, Leo
2017-01-09 15:13               ` Laszlo Ersek
2017-01-09 16:37                 ` Duran, Leo
2017-01-09 22:41                   ` Jordan Justen
2017-01-10  5:33               ` Gao, Liming
2017-01-10  5:48                 ` Duran, Leo

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=148375017874.13659.3185969071926290103@jljusten-ivb \
    --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