[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210113223808.31626-2-hongweiz@ami.com>
Date: Fri, 5 Feb 2021 11:34:51 -0500
From: Hongwei Zhang <hongweiz@....com>
To: Andrew Jeffery <andrew@...id.au>
CC: Hongwei Zhang <hongweiz@....com>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Joel Stanley <joel@....id.au>,
Linus Walleij <linus.walleij@...aro.org>,
<linux-gpio@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-aspeed@...ts.ozlabs.org>, <linux-kernel@...r.kernel.org>,
<openbmc@...ts.ozlabs.org>
Subject: [PATCH, v1 1/1] gpio: aspeed: Add gpio base address reading
> Hello,
>
> On Thu, 14 Jan 2021, at 09:08, Hongwei Zhang wrote:
> > Add gpio base address reading in the driver; in old code, it just
> > returns -1 to gpio->chip.base.
>
> Why do you want to do this? It feels hacky. The base address only affects the legacy sysfs number-space,
> and even then if you're using the sysfs interface you can discover the base address for a specific gpiochip
> via the associated attribute. For example:
>
> # cat /sys/bus/platform/devices/1e780000.gpio/gpio/gpiochip*/base
> 816
>
> I feel that you should instead be changing your userspace not to assume a fixed value.
>
> Finally, the base value is a linux-specific thing and doesn't belong in the devicetree, and if it did, you
> would also need to update the devicetree binding in Documentation/.
>
> Cheers,
>
> Andrew
Hi Andrew,
Thanks for your review and advice.
--Hongwei
Powered by blists - more mailing lists