public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Haojian Zhuang <haojian.zhuang@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH v2 edk-platforms 1/4] Platform/Hisilicon/HiKey960: add gpio platform driver
Date: Fri, 4 May 2018 11:26:35 +0100	[thread overview]
Message-ID: <20180504102634.tvn2hn42qnxlf7bf@bivouac.eciton.net> (raw)
In-Reply-To: <CAD6h2NQKCyVvtsNnvrwP=9_FqjJoKgRrORvQmvCPtANENBzaXw@mail.gmail.com>

On Fri, May 04, 2018 at 11:29:33AM +0800, Haojian Zhuang wrote:
> On 2 May 2018 at 23:14, Leif Lindholm <leif.lindholm@linaro.org> wrote:
> >> +  { 0xe8a0b000, 0, 8 },    // GPIO0
> >
> > It would not improve readability to request all of these live-coded
> > values to be replaced by #defines, but barring that, could you add a
> > comment header before the definition?:
> >
> > //  { base address, gpio index, gpio count }
> >
> 
> OK
> >> +  { 0xe8a0c000, 8, 8 },    // GPIO1
> >> +  { 0xe8a0d000, 16, 8 },   // GPIO2
> >> +  { 0xe8a0e000, 24, 8 },   // GPIO3
> >> +  { 0xe8a0f000, 32, 8 },   // GPIO4
> >> +  { 0xe8a10000, 40, 8 },   // GPIO5
> >> +  { 0xe8a11000, 48, 8 },   // GPIO6
> >> +  { 0xe8a12000, 56, 8 },   // GPIO7
> >> +  { 0xe8a13000, 64, 8 },   // GPIO8
> >> +  { 0xe8a14000, 72, 8 },   // GPIO9
> >> +  { 0xe8a15000, 80, 8 },   // GPIO10
> >> +  { 0xe8a16000, 88, 8 },   // GPIO11
> >> +  { 0xe8a17000, 96, 8 },   // GPIO12
> >> +  { 0xe8a18000, 104, 8 },  // GPIO13
> >> +  { 0xe8a19000, 112, 8 },  // GPIO14
> >> +  { 0xe8a1a000, 120, 8 },  // GPIO15
> >> +  { 0xe8a1b000, 128, 8 },  // GPIO16
> >> +  { 0xe8a1c000, 136, 8 },  // GPIO17
> >> +  { 0xff3b4000, 144, 8 },  // GPIO18
> >> +  { 0xff3b5000, 152, 8 },  // GPIO19
> >
> > I notice that these:
> >> +  { 0xe8a1f000, 160, 8 },  // GPIO20
> >> +  { 0xe8a20000, 168, 8 },  // GPIO21
> > are out of order, from their base address.
> > Are the names GPIO20/GPIO21 defined in the TRM?
> >
> 
> Yes, it's mentioned in the TRM.

Yeah, I figured as much, but was hoping for something else :)

> (https://github.com/96boards/documentation/blob/master/consumer/hikey960/hardware-docs/HiKey960_SoC_Reference_Manual.pdf)

Thanks for the link - that will be useful!

/
    Leif


  reply	other threads:[~2018-05-04 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 13:29 [PATCH v2 edk-platforms 1/4] Platform/Hisilicon/HiKey960: add gpio platform driver Haojian Zhuang
2018-05-02 15:14 ` Leif Lindholm
2018-05-04  3:29   ` Haojian Zhuang
2018-05-04 10:26     ` Leif Lindholm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-08 13:35 [PATCH v2 edk-platforms 0/4] enable virtual keyboards on hikey Haojian Zhuang
2018-03-08 13:35 ` [PATCH v2 edk-platforms 1/4] Platform/Hisilicon/HiKey960: add gpio platform driver Haojian Zhuang

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=20180504102634.tvn2hn42qnxlf7bf@bivouac.eciton.net \
    --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