From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Billy Tsai <billy_tsai@aspeedtech.com>,
linus.walleij@linaro.org, brgl@bgdev.pl, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, joel@jms.id.au,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
BMC-SW@aspeedtech.com
Subject: Re: [PATCH v2 2/4] gpio: aspeed: Remove the name for bank array
Date: Thu, 12 Sep 2024 17:21:27 +0930 [thread overview]
Message-ID: <7e2643f7586a7ed5d3cc90630d78fb3abd813a54.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20240830034047.2251482-3-billy_tsai@aspeedtech.com>
On Fri, 2024-08-30 at 11:40 +0800, Billy Tsai wrote:
> The bank array name is only used to determine if the GPIO offset is valid,
> and this condition can be replaced by checking if the offset exceeds the
> ngpio property.
>
> Signed-off-by: Billy Tsai <billy_tsai@aspeedtech.com>
> ---
> drivers/gpio/gpio-aspeed.c | 17 ++++-------------
> 1 file changed, 4 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpio/gpio-aspeed.c b/drivers/gpio/gpio-aspeed.c
> index 04c03402db6d..24f50a0ea4ab 100644
> --- a/drivers/gpio/gpio-aspeed.c
> +++ b/drivers/gpio/gpio-aspeed.c
> @@ -77,7 +77,6 @@ struct aspeed_gpio_bank {
> uint16_t debounce_regs;
> uint16_t tolerance_regs;
> uint16_t cmdsrc_regs;
> - const char names[4][3];
> };
>
> /*
> @@ -104,7 +103,6 @@ static const struct aspeed_gpio_bank aspeed_gpio_banks[] = {
> .debounce_regs = 0x0040,
> .tolerance_regs = 0x001c,
> .cmdsrc_regs = 0x0060,
> - .names = { "A", "B", "C", "D" },
> },
> {
> .val_regs = 0x0020,
> @@ -113,7 +111,6 @@ static const struct aspeed_gpio_bank aspeed_gpio_banks[] = {
> .debounce_regs = 0x0048,
> .tolerance_regs = 0x003c,
> .cmdsrc_regs = 0x0068,
> - .names = { "E", "F", "G", "H" },
> },
> {
> .val_regs = 0x0070,
> @@ -122,7 +119,6 @@ static const struct aspeed_gpio_bank aspeed_gpio_banks[] = {
> .debounce_regs = 0x00b0,
> .tolerance_regs = 0x00ac,
> .cmdsrc_regs = 0x0090,
> - .names = { "I", "J", "K", "L" },
> },
> {
> .val_regs = 0x0078,
> @@ -131,7 +127,6 @@ static const struct aspeed_gpio_bank aspeed_gpio_banks[] = {
> .debounce_regs = 0x0100,
> .tolerance_regs = 0x00fc,
> .cmdsrc_regs = 0x00e0,
> - .names = { "M", "N", "O", "P" },
> },
> {
> .val_regs = 0x0080,
> @@ -140,7 +135,6 @@ static const struct aspeed_gpio_bank aspeed_gpio_banks[] = {
> .debounce_regs = 0x0130,
> .tolerance_regs = 0x012c,
> .cmdsrc_regs = 0x0110,
> - .names = { "Q", "R", "S", "T" },
> },
> {
> .val_regs = 0x0088,
> @@ -149,7 +143,6 @@ static const struct aspeed_gpio_bank aspeed_gpio_banks[] = {
> .debounce_regs = 0x0160,
> .tolerance_regs = 0x015c,
> .cmdsrc_regs = 0x0140,
> - .names = { "U", "V", "W", "X" },
> },
> {
> .val_regs = 0x01E0,
> @@ -158,7 +151,6 @@ static const struct aspeed_gpio_bank aspeed_gpio_banks[] = {
> .debounce_regs = 0x0190,
> .tolerance_regs = 0x018c,
> .cmdsrc_regs = 0x0170,
> - .names = { "Y", "Z", "AA", "AB" },
> },
> {
> .val_regs = 0x01e8,
> @@ -167,7 +159,6 @@ static const struct aspeed_gpio_bank aspeed_gpio_banks[] = {
> .debounce_regs = 0x01c0,
> .tolerance_regs = 0x01bc,
> .cmdsrc_regs = 0x01a0,
> - .names = { "AC", "", "", "" },
> },
> };
>
> @@ -280,11 +271,11 @@ static inline const struct aspeed_bank_props *find_bank_props(
> static inline bool have_gpio(struct aspeed_gpio *gpio, unsigned int offset)
> {
> const struct aspeed_bank_props *props = find_bank_props(gpio, offset);
> - const struct aspeed_gpio_bank *bank = to_bank(offset);
> - unsigned int group = GPIO_OFFSET(offset) / 8;
>
> - return bank->names[group][0] != '\0' &&
> - (!props || ((props->input | props->output) & GPIO_BIT(offset)));
> + if (offset > gpio->chip.ngpio)
Should this be `>=`? ngpio is a count.
Andrew
> + return false;
> +
> + return (!props || ((props->input | props->output) & GPIO_BIT(offset)));
> }
>
> static inline bool have_input(struct aspeed_gpio *gpio, unsigned int offset)
next prev parent reply other threads:[~2024-09-12 7:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 3:40 [PATCH v2 0/4] Add Aspeed G7 gpio support Billy Tsai
2024-08-30 3:40 ` [PATCH v2 1/4] dt-bindings: gpio: aspeed,ast2400-gpio: Support ast2700 Billy Tsai
2024-08-30 14:04 ` Conor Dooley
2024-09-02 2:32 ` Billy Tsai
2024-08-31 5:49 ` Krzysztof Kozlowski
2024-08-30 3:40 ` [PATCH v2 2/4] gpio: aspeed: Remove the name for bank array Billy Tsai
2024-09-12 7:51 ` Andrew Jeffery [this message]
2024-09-12 7:57 ` Billy Tsai
2024-08-30 3:40 ` [PATCH v2 3/4] gpio: aspeed: Create llops to handle hardware access Billy Tsai
2024-08-30 16:07 ` kernel test robot
2024-08-31 1:46 ` kernel test robot
2024-08-31 16:05 ` Dan Carpenter
2024-09-12 8:18 ` Andrew Jeffery
2024-08-30 3:40 ` [PATCH v2 4/4] gpio: aspeed: Support G7 Aspeed gpio controller Billy Tsai
2024-08-31 3:39 ` kernel test robot
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=7e2643f7586a7ed5d3cc90630d78fb3abd813a54.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=BMC-SW@aspeedtech.com \
--cc=billy_tsai@aspeedtech.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).