From: Patrice Chotard <patrice.chotard@st.com>
To: <gabriel.fernandez@st.com>,
Linus Walleij <linus.walleij@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Laxman Dewangan <ldewangan@nvidia.com>
Cc: <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: stm32: activate strict mux mode
Date: Fri, 16 Dec 2016 13:37:56 +0100 [thread overview]
Message-ID: <42c18683-6d2e-b717-2863-7f6c405cfa83@st.com> (raw)
In-Reply-To: <1481725456-1030-1-git-send-email-gabriel.fernandez@st.com>
On 12/14/2016 03:24 PM, gabriel.fernandez@st.com wrote:
> From: Gabriel Fernandez <gabriel.fernandez@st.com>
>
> This activates strict mode muxing for the STM32 pin controllers,
> as these do not allow GPIO and functions to use the same pin
> simultaneously.
>
> Signed-off-by: Gabriel Fernandez <gabriel.fernandez@st.com>
> ---
> drivers/pinctrl/stm32/pinctrl-stm32.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pinctrl/stm32/pinctrl-stm32.c b/drivers/pinctrl/stm32/pinctrl-stm32.c
> index efc4371..c983a1e 100644
> --- a/drivers/pinctrl/stm32/pinctrl-stm32.c
> +++ b/drivers/pinctrl/stm32/pinctrl-stm32.c
> @@ -631,6 +631,7 @@ static int stm32_pmx_gpio_set_direction(struct pinctrl_dev *pctldev,
> .get_function_groups = stm32_pmx_get_func_groups,
> .set_mux = stm32_pmx_set_mux,
> .gpio_set_direction = stm32_pmx_gpio_set_direction,
> + .strict = true,
> };
>
> /* Pinconf functions */
>
Hi Gaby
Acked-by: Patrice Chotard <patrice.chotard@st.com>
regards
next prev parent reply other threads:[~2016-12-16 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 14:24 [PATCH] pinctrl: stm32: activate strict mux mode gabriel.fernandez
2016-12-16 12:37 ` Patrice Chotard [this message]
2016-12-30 8:07 ` Linus Walleij
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=42c18683-6d2e-b717-2863-7f6c405cfa83@st.com \
--to=patrice.chotard@st.com \
--cc=alexandre.torgue@st.com \
--cc=gabriel.fernandez@st.com \
--cc=ldewangan@nvidia.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 \
--cc=mcoquelin.stm32@gmail.com \
/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).