From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Timur Tabi <timur@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] pinctrl: msm: allow the gpio base to be configurable
Date: Sun, 28 Jan 2018 15:23:10 -0800 [thread overview]
Message-ID: <20180128232310.GA12728@builder> (raw)
In-Reply-To: <1516915209-28295-1-git-send-email-timur@codeaurora.org>
On Thu 25 Jan 13:20 PST 2018, Timur Tabi wrote:
> Add an integer to the msm_pinctrl_soc_data struct that pinctrl-msm
> client drivers can use to specify the gpio base. This is useful
> if the client driver wants to register multiple TLMM devices, because
> each one needs a distinct base.
>
> pinctrl-msm currently sets the base to 0, which ensures that GPIOs
> of the first TLMM are numbered 0..n-1. It could specify -1 as the
> base, which would tell gpiolib to choose a unique base, but this
> has the side-effect of choosing a non-zero base for all TLMMs:
What platform has multiple TLMMs?
[..]
> diff --git a/drivers/pinctrl/qcom/pinctrl-msm.c b/drivers/pinctrl/qcom/pinctrl-msm.c
> index b7b6849625ec..4dc76e15bd14 100644
> --- a/drivers/pinctrl/qcom/pinctrl-msm.c
> +++ b/drivers/pinctrl/qcom/pinctrl-msm.c
> @@ -901,7 +901,7 @@ static int msm_gpio_init(struct msm_pinctrl *pctrl)
> return -EINVAL;
>
> chip = &pctrl->chip;
> - chip->base = 0;
My bad, this should have been -1.
Regards,
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: bjorn.andersson@linaro.org (Bjorn Andersson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: msm: allow the gpio base to be configurable
Date: Sun, 28 Jan 2018 15:23:10 -0800 [thread overview]
Message-ID: <20180128232310.GA12728@builder> (raw)
In-Reply-To: <1516915209-28295-1-git-send-email-timur@codeaurora.org>
On Thu 25 Jan 13:20 PST 2018, Timur Tabi wrote:
> Add an integer to the msm_pinctrl_soc_data struct that pinctrl-msm
> client drivers can use to specify the gpio base. This is useful
> if the client driver wants to register multiple TLMM devices, because
> each one needs a distinct base.
>
> pinctrl-msm currently sets the base to 0, which ensures that GPIOs
> of the first TLMM are numbered 0..n-1. It could specify -1 as the
> base, which would tell gpiolib to choose a unique base, but this
> has the side-effect of choosing a non-zero base for all TLMMs:
What platform has multiple TLMMs?
[..]
> diff --git a/drivers/pinctrl/qcom/pinctrl-msm.c b/drivers/pinctrl/qcom/pinctrl-msm.c
> index b7b6849625ec..4dc76e15bd14 100644
> --- a/drivers/pinctrl/qcom/pinctrl-msm.c
> +++ b/drivers/pinctrl/qcom/pinctrl-msm.c
> @@ -901,7 +901,7 @@ static int msm_gpio_init(struct msm_pinctrl *pctrl)
> return -EINVAL;
>
> chip = &pctrl->chip;
> - chip->base = 0;
My bad, this should have been -1.
Regards,
Bjorn
next prev parent reply other threads:[~2018-01-28 23:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 21:20 [PATCH] pinctrl: msm: allow the gpio base to be configurable Timur Tabi
2018-01-25 21:20 ` Timur Tabi
2018-01-26 13:01 ` Linus Walleij
2018-01-26 13:01 ` Linus Walleij
2018-01-26 13:16 ` Timur Tabi
2018-01-26 13:16 ` Timur Tabi
2018-01-26 22:13 ` Bartosz Golaszewski
2018-01-26 22:13 ` Bartosz Golaszewski
2018-01-28 23:23 ` Bjorn Andersson [this message]
2018-01-28 23:23 ` Bjorn Andersson
2018-01-28 23:29 ` Timur Tabi
2018-01-28 23:29 ` Timur Tabi
2018-01-29 0:51 ` Bjorn Andersson
2018-01-29 0:51 ` Bjorn Andersson
2018-02-07 13:19 ` Linus Walleij
2018-02-07 13:19 ` Linus Walleij
2018-02-07 14:50 ` Timur Tabi
2018-02-07 14:50 ` Timur Tabi
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=20180128232310.GA12728@builder \
--to=bjorn.andersson@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=timur@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.