From: Florian Fainelli <f.fainelli@gmail.com>
To: justinpopo6@gmail.com, linux-gpio@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com, f.fainelli@gmail.com,
computersforpeace@gmail.com, linus.walleij@linaro.org,
gregory.0xf0@gmail.com
Subject: Re: [PATCH] gpio: brcmstb: allow 0 width GPIO banks
Date: Wed, 15 Aug 2018 17:14:05 -0700 [thread overview]
Message-ID: <d52fd4f0-1589-86e5-9dfd-4748bdab9bde@gmail.com> (raw)
In-Reply-To: <1534289517-1805-1-git-send-email-justinpopo6@gmail.com>
On 08/14/2018 04:31 PM, justinpopo6@gmail.com wrote:
> From: Justin Chen <justinpopo6@gmail.com>
>
> Sometimes we have empty banks within the GPIO block. This commit allows
> proper handling of 0 width GPIO banks. We handle 0 width GPIO banks by
> incrementing the bank and number of GPIOs, but not initializing them.
> This will mean a call into the non-existent GPIOs will return an error.
>
> Also remove banks and GPIO information from the dev_info print. This
> information is misleading since the incremented banks and gpio_base do
> not reflect the actual GPIOs that got initialized. We leave this
> information out since it is already printed with dev_dbg.
>
> Signed-off-by: Justin Chen <justinpopo6@gmail.com>
> ---
> drivers/gpio/gpio-brcmstb.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpio/gpio-brcmstb.c b/drivers/gpio/gpio-brcmstb.c
> index 16c7f9f..8658910 100644
> --- a/drivers/gpio/gpio-brcmstb.c
> +++ b/drivers/gpio/gpio-brcmstb.c
> @@ -664,6 +664,18 @@ static int brcmstb_gpio_probe(struct platform_device *pdev)
> struct brcmstb_gpio_bank *bank;
> struct gpio_chip *gc;
>
> + /*
> + * If bank_width is 0, then there is an empty bank in the
> + * register block. Special handling for this case.
> + */
> + if (bank_width == 0) {
> + dev_dbg(dev, "Width 0 found: Empty bank @ %d\n",
> + num_banks);
Stylistic nit: you would want the second line to be aligned at the start
of the opening parenthesis
> + num_banks++;
> + gpio_base += MAX_GPIO_PER_BANK;
> + continue;
> + }
> +
> bank = devm_kzalloc(dev, sizeof(*bank), GFP_KERNEL);
> if (!bank) {
> err = -ENOMEM;
> @@ -740,8 +752,7 @@ static int brcmstb_gpio_probe(struct platform_device *pdev)
> goto fail;
> }
>
> - dev_info(dev, "Registered %d banks (GPIO(s): %d-%d)\n",
> - num_banks, priv->gpio_base, gpio_base - 1);
> + dev_info(dev, "Brcmstb GPIO registered\n");
Not sure if there much value in preserving that message anymore, if the
controller is not there, nothing will show up in /sys/class/gpio, so you
would pretty quickly find out that something went wrong?
>
> if (priv->parent_wake_irq && need_wakeup_event)
> pm_wakeup_event(dev, 0);
>
--
Florian
prev parent reply other threads:[~2018-08-16 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 23:31 justinpopo6
2018-08-16 0:14 ` Florian Fainelli [this message]
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=d52fd4f0-1589-86e5-9dfd-4748bdab9bde@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=gregory.0xf0@gmail.com \
--cc=justinpopo6@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®