public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: mark.kettenis@xs4all.nl, devel@edk2.groups.io
Subject: Re: [edk2-devel] Additional configuration options on Armada/Cn913x
Date: Fri, 12 Jun 2020 10:45:18 +0200	[thread overview]
Message-ID: <1886d7a0-cc28-54ce-6d57-b42f3525d6e2@arm.com> (raw)
In-Reply-To: <14107.1591915430415249079@groups.io>

On 6/12/20 12:43 AM, Mark Kettenis via Groups.Io wrote:
> On Thu, Jun 11, 2020 at 04:17 PM, Ard Biesheuvel wrote:
> 
>     On 6/11/20 4:07 PM, greg@unrelenting.technology wrote:
> 
>         June 11, 2020 4:19 PM, "Ard Biesheuvel" <ard.biesheuvel@arm.com>
>         wrote:
> 
>             On 6/5/20 5:19 PM, Marcin Wojtas via groups.io wrote:
> 
>                 Hi,
>                 I'd like to ask for comments before I develop the actual
>                 code - > currently we have 2 workarounds
>                 done specifically for Linux:
>                 a. ECAM shift in PCIE
>                 b. SPCR address space definition
> 
>             What does this mean?
> 
>         The SPCR in upstream edk2 is set up to work around some Linux
>         weirdness (?) and I have to do this:
> 
>         https://github.com/myfreeweb/edk2-platforms/commit/74ec98a6498e78d2ae6c861db88487bf75f2e1a1
> 
>         to make it work on FreeBSD.
> 
>     Surely, they can't both be correct. Marcin?
> 
> Assuming the serial port on Armada/Cn911x is the same as on Armada8k, 
> the following DT properties would be applicable:
> 
> reg-shift = <2>;
> reg-io-width = <1>
> 
> which means the registers are spaced 32-bits apart but have to be 
> accessed using 8-bit load/store instructions.  I'd say that
> means that the ACPI Generic Address Space should have RegisterBitWidth 
> set to 32 and AccessSize set to BYTE.
> In other words, I think that the current:
> 
> #define MV_UART_AS32(Address) { EFI_ACPI_5_0_SYSTEM_MEMORY, 32, 0, 
> EFI_ACPI_5_0_BYTE, Address }
> 
> is correct.  That certainly is what works for OpenBSD.

Thanks Mark

The struct type is defined as

typedef struct {
   UINT8   AddressSpaceId;
   UINT8   RegisterBitWidth;
   UINT8   RegisterBitOffset;
   UINT8   AccessSize;
   UINT64  Address;
} EFI_ACPI_5_0_GENERIC_ADDRESS_STRUCTURE;

so I agree that the current definition matches a UART that requires byte 
accesses on registers that are 32 bits apart.

So why does FreeBSD deviate from this?

  reply	other threads:[~2020-06-12  8:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 15:19 Additional configuration options on Armada/Cn913x Marcin Wojtas
2020-06-11 13:19 ` [edk2-devel] " Ard Biesheuvel
2020-06-11 14:07 ` greg
2020-06-11 14:17   ` Ard Biesheuvel
2020-06-11 22:43     ` Mark Kettenis
2020-06-12  8:45       ` Ard Biesheuvel [this message]
2020-06-12 15:07         ` Marcin Wojtas
2020-06-12 16:32           ` greg
2020-06-12 17:09             ` Marcin Wojtas
2020-06-20 15:44               ` Marcin Wojtas
2020-06-11 14:33   ` greg
2020-06-11 14:38     ` Ard Biesheuvel
2020-06-11 14:46     ` greg

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=1886d7a0-cc28-54ce-6d57-b42f3525d6e2@arm.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