From: John Keeping <john@metanate.com>
To: Johan Jonker <jbx6244@gmail.com>
Cc: u-boot@lists.denx.de,
Quentin Schulz <quentin.schulz@theobroma-systems.com>,
Simon Glass <sjg@chromium.org>,
Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH] rockchip: derive GPIO bank from alias if available
Date: Wed, 18 Jan 2023 16:13:29 +0000 [thread overview]
Message-ID: <Y8gaqasu9ho0vl8X@donbot> (raw)
In-Reply-To: <98e06ac6-511a-28a7-c659-4cd91c064ad7@gmail.com>
On Tue, Jan 17, 2023 at 08:52:22PM +0100, Johan Jonker wrote:
>
>
> On 1/17/23 19:15, John Keeping wrote:
> > Upstream device trees now use standard node names like "gpio@ff..." but
> > the rk_gpio driver expects a name like "gpio0@ff..." (note the index
> > before the @).
> >
> > This is not a change that can be made in a -u-boot.dtsi file, so
> > updating to the latest upstream device trees requires updating the
> > driver.
> >
> > Other GPIO drivers already use the sequence number to derive the bank.
> > This can be set explicitly using an alias in the device tree (which can
> > be added in a -u-boot.dtsi file) but Rockchip GPIO banks are defined in
> > order in the device tree anyway so when no aliases are supplied the
> > indexes should still be correct.
> >
> > Note that the bank name is only used by the `gpio` command or
> > potentially by board code via dm_gpio_lookup_name() and related
> > functions; it is not used by driver code which will lookup GPIOs from
> > the device tree by phandle. No Rockchip platforms make any use of
> > dm_gpio_lookup_name() or `gpio` in the boot scripts.
> >
> > Cc: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> > Cc: Johan Jonker <jbx6244@gmail.com>
> > Signed-off-by: John Keeping <john@metanate.com>
> > ---
> > drivers/gpio/rk_gpio.c | 6 ++----
> > 1 file changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/gpio/rk_gpio.c b/drivers/gpio/rk_gpio.c
> > index 68f30157a9..8568f10cd0 100644
> > --- a/drivers/gpio/rk_gpio.c
> > +++ b/drivers/gpio/rk_gpio.c
> > @@ -142,7 +142,6 @@ static int rockchip_gpio_probe(struct udevice *dev)
> > {
> > struct gpio_dev_priv *uc_priv = dev_get_uclass_priv(dev);
> > struct rockchip_gpio_priv *priv = dev_get_priv(dev);
> > - char *end;
> > int ret;
> >
> > priv->regs = dev_read_addr_ptr(dev);
> > @@ -151,9 +150,8 @@ static int rockchip_gpio_probe(struct udevice *dev)
> > return ret;
> >
> > uc_priv->gpio_count = ROCKCHIP_GPIOS_PER_BANK;
> > - end = strrchr(dev->name, '@');
> > - priv->bank = trailing_strtoln(dev->name, end);
> > - priv->name[0] = 'A' + priv->bank;
>
> > +
> > + priv->name[0] = 'A' + dev_seq(dev);
>
> Some comments. Have a look if it's useful.
> ===
> 1:
> Tested with rk3066a mk808 in only full u-boot.
>
> The gpio banks have a number gap.
>
> aliases {
> gpio0 = &gpio0;
> gpio1 = &gpio1;
> gpio2 = &gpio2;
> gpio3 = &gpio3;
> gpio4 = &gpio4;
>
> gpio6 = &gpio6;
> };
>
> With aliases gpio6 is called G.
> Without gpio6 is called F.
> There's no name consistency for command scripts.
True, but those scripts are going to be board specific and already
depend on board data. The name will be consistent per board.
> ===
> 2:
> For example: rk3288-evb-u-boot.dtsi
>
> What happens in tpl or spl with only gpio3 and gpio8 in dt-plat.c.
Is the bank name used in tpl/spl at all? There's no script support
there and it could only be used in board code.
> Or with SPL FDT blob:
>
> [v1,01/17] rockchip: spl: fix reloc gd and FDT blob pointer
> http://patchwork.ozlabs.org/project/uboot/patch/20220508150825.21711-2-jbx6244@gmail.com/
>
> Not in use in mainline. Just saying there's more possible in SPL/TPL.
> ===
> The use of aliases is more of something of an additional thing that we not always can count on that is there.
Again this is board specific - if a board wants this scheme of GPIO
naming it can enable aliases and rely on that.
I have been thinking of another option which is a bigger change to the
bank name - it doesn't have to be a letter, could we use the register
address as the bank name? So the GPIO would be something like
ff750000.1 (although I don't know how the naming scheme works, so having
a separator may not work).
What do you think of that idea?
Regards,
John
next prev parent reply other threads:[~2023-01-18 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 18:15 [PATCH] rockchip: derive GPIO bank from alias if available John Keeping
2023-01-17 19:52 ` Johan Jonker
2023-01-18 16:13 ` John Keeping [this message]
2023-01-19 10:17 ` Johan Jonker
2023-02-22 8:41 ` Kever Yang
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-all 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=Y8gaqasu9ho0vl8X@donbot \
--to=john@metanate.com \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--cc=quentin.schulz@theobroma-systems.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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