public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "John Chew" <yuinyee.chew@starfivetech.com>
To: Ard Biesheuvel <ardb@kernel.org>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v3 2/5] DesignWare/DwEmmcDxe: Add CPU little endian option
Date: Sun, 26 Nov 2023 23:09:05 -0800	[thread overview]
Message-ID: <9575.1701068945988795618@groups.io> (raw)
In-Reply-To: <CAMj1kXG0n4kr38oOoiCB8U_tn8R3Kq4Zm4D4MiGGgD8ywmLikw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]

Hi Ard,

I take it this means that the IP can be synthesized in both little and big endian versions, right?

Yes, correct.

Is there no ID register in the hardware you can derive this information from?

Yes, in RISC-V we can determine the CPU endianness based on mstatus.MBE and mstatus.SBE register in M-Mode and S-Mode respectively.

However, this driver will be used for other architecture, so reading this register will not make sense for other architectures such as ARM and x86.

I have not seen any API to call in EDK2 in order to check for CPU endiness.

Alternatively, I can update the handling by using software checking for the CPU endianness as follows:

This will not use PCD to determine the CPU endianness.

I will change this handling in the coming patch series if you think it is okay.

Thank you for your time =)

Regards,

John


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111727): https://edk2.groups.io/g/devel/message/111727
Mute This Topic: https://groups.io/mt/102357273/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #1.2: Type: text/html, Size: 2192 bytes --]

[-- Attachment #2: dummyfile.0.part --]
[-- Type: image/png, Size: 6851 bytes --]

[-- Attachment #3: dummyfile.1.part --]
[-- Type: image/png, Size: 18994 bytes --]

  reply	other threads:[~2023-11-27  7:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03  2:51 [edk2-devel] [PATCH v3 0/5] Designware MMCDXE changes and enhancement John Chew
2023-11-03  2:51 ` [edk2-devel] [PATCH v3 1/5] DesignWare/DwEmmcDxe: Enabled Internal IDMAC interrupt RX/TX register John Chew
2023-11-22 15:41   ` Ard Biesheuvel
2023-11-27  7:10     ` John Chew
2023-11-03  2:51 ` [edk2-devel] [PATCH v3 2/5] DesignWare/DwEmmcDxe: Add CPU little endian option John Chew
2023-11-22 15:45   ` Ard Biesheuvel
2023-11-27  7:09     ` John Chew [this message]
2023-11-03  2:51 ` [edk2-devel] [PATCH v3 3/5] DesignWare/DwEmmcDxe: Remove ARM dependency library John Chew
2023-11-22 15:46   ` Ard Biesheuvel
2023-11-03  2:51 ` [edk2-devel] [PATCH v3 4/5] DesignWare/DwEmmcDxe: Add handling for SDMMC John Chew
2023-11-22 15:47   ` Ard Biesheuvel
2023-11-03  2:51 ` [edk2-devel] [PATCH v3 5/5] DesignWare/DwEmmcDxe: Force DMA buffer to allocate below 4GB John Chew
2023-11-22 15:49   ` Ard Biesheuvel
2023-11-07  1:09 ` [edk2-devel] [PATCH v3 0/5] Designware MMCDXE changes and enhancement John Chew
2023-11-22  4:06 ` John Chew

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=9575.1701068945988795618@groups.io \
    --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