From: Bhupesh Sharma <bhupesh.sharma@nxp.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@ml01.01.org" <edk2-devel@ml01.01.org>,
Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>
Subject: Re: [PATCH 1/1] MdePkg/IoLib: Add support for big-endian MMIO
Date: Mon, 17 Oct 2016 09:57:58 +0000 [thread overview]
Message-ID: <AM4PR0401MB228984E04BE53F7D1A4219BE88D00@AM4PR0401MB2289.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAKv+Gu_5AB_gNW4es-BJG0=Ur25-8oQphDLcNvx14j3W-BCGFA@mail.gmail.com>
Hi Ard,
> -----Original Message-----
> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
> Sent: Monday, October 17, 2016 1:12 PM
> To: Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: Gao, Liming <liming.gao@intel.com>; Bhupesh Sharma
> <bhupesh.sharma@nxp.com>; edk2-devel@ml01.01.org
> Subject: Re: [edk2] [PATCH 1/1] MdePkg/IoLib: Add support for big-
> endian MMIO
>
> On 17 October 2016 at 05:10, Kinney, Michael D
> <michael.d.kinney@intel.com> wrote:
> > Bhupesh,
> >
> > It is also possible to add an ARM specific PCD to select endianness
> > and update MdePkg/Library/BaseIoLibIntrinsic/IoLibArm.c to use that
> > PCD in MmioRead/Write() APIs in that file to support both endian
> > types. You can use the SwapBytesxx() functions from BaseLib(as
> Laszlo
> > suggested) based on the setting of this ARM specific PCD.
> >
> > Modules that link against this lib can select endianness by setting
> > PCD in the scope of that module.
> >
> > The IPF version of IoLib uses an IPF specific PCD to translate I/O
> > port accesses to MMIO accesses. So there is already an example of an
> > arch specific PCD in this lib instance.
> >
>
> This is not a platform wide thing, it is a per-device property whether
> the MMIO occurs in big endian or little endian manner.
>
> So I think Liming's suggestion makes sense: create an IoLib
> implementation that performs the byte swapping, and selectively
> incorporate it into drivers that require it using
>
> BeMmioDeviceDxe.inf {
> <LibraryClasses>
> IoLib|SomePkg/Library/BigEndianIoLib.inf
> }
That's correct. I think creating a separate IoLib for byte-swapping makes sense.
We will rework the patch accordingly.
Regards,
Bhupesh
next prev parent reply other threads:[~2016-10-17 9:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 9:33 [PATCH 1/1] MdePkg/IoLib: Add support for big-endian MMIO Bhupesh Sharma
2016-10-14 12:06 ` Laszlo Ersek
2016-10-14 13:17 ` Bhupesh Sharma
2016-10-14 13:32 ` Laszlo Ersek
2016-10-17 3:10 ` Gao, Liming
2016-10-17 4:10 ` Kinney, Michael D
2016-10-17 7:42 ` Ard Biesheuvel
2016-10-17 9:57 ` Bhupesh Sharma [this message]
2017-10-13 6:07 ` Meenakshi Aggarwal
2017-10-16 3:17 ` Gao, Liming
2017-10-23 7:07 ` Udit Kumar
2017-11-27 6:06 ` Meenakshi Aggarwal
2017-11-27 11:07 ` Leif Lindholm
2017-11-29 12:51 ` Leif Lindholm
2017-11-29 19:25 ` Kinney, Michael D
2017-11-29 19:48 ` Leif Lindholm
2017-11-30 4:15 ` Meenakshi Aggarwal
2017-12-01 10:57 ` Leif Lindholm
2017-12-01 17:57 ` Udit Kumar
2017-12-01 22:41 ` Kinney, Michael D
2017-12-04 6:18 ` Meenakshi Aggarwal
2017-12-04 12:36 ` Leif Lindholm
2017-12-04 15:31 ` Kinney, Michael D
2017-12-04 15:54 ` Leif Lindholm
2017-12-04 16:19 ` Kinney, Michael D
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=AM4PR0401MB228984E04BE53F7D1A4219BE88D00@AM4PR0401MB2289.eurprd04.prod.outlook.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