From: Fenglin Wu <fenglinw@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, collinsd@codeaurora.org,
aghayal@codeaurora.org, wruan@codeaurora.org,
subbaram@codeaurora.org, kgunda@codeaurora.org
Subject: Re: [PATCH V1 2/2] pinctrl: qcom: spmi-gpio: Set is_enabled flag in set_mux()
Date: Tue, 17 Oct 2017 12:36:09 +0800 [thread overview]
Message-ID: <78f23ed8-7e3e-ffc9-bdbe-e10622e0c757@codeaurora.org> (raw)
In-Reply-To: <20171016222955.GQ1165@minitux>
On 10/17/2017 6:29 AM, Bjorn Andersson wrote:
> On Thu 12 Oct 23:15 PDT 2017, fenglinw@codeaurora.org wrote:
>
>> From: Fenglin Wu <fenglinw@codeaurora.org>
>>
>> The initial value of is_enabled flag is read out from hardware in
>> pmic_gpio_populate(), and it will be set in pmic_gpio_config_set() if
>> pinconf is defined. For any GPIOs disabled initially in hardware which
>> only have pinmux defined, they won't be enabled in pmic_gpio_set_mux()
>> calling. So set is_enabled flag in set_mux() to ensure the GPIO module
>> could be enabled in above case.
>>
>
> I'm still interested in knowing when it is valid to configure a pin with
> only mux, no config. I.e. in what cases does setting a alternative
> function make the pinconfig not count.
I agreed that any pins should be configured with pinmux as well as
pinconf, but the driver doesn't prevent the case of only pinmux defined,
right? I am not sure if this is valid case but it would happen: The
hardware or the sw prior to linux kernel has the default setting of the
function and config for one GPIO but we need to keep it disabled until
the consumer request it, in this case, we just need to define the pinmux
and ignore the pinconf definition in its device node.
>
> Regards,
> Bjorn
>
>> Signed-off-by: Fenglin Wu <fenglinw@codeaurora.org>
>> ---
>> drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c b/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
>> index 0a1e173..219c934 100644
>> --- a/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
>> +++ b/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
>> @@ -312,6 +312,7 @@ static int pmic_gpio_set_mux(struct pinctrl_dev *pctldev, unsigned function,
>> }
>>
>> pad = pctldev->desc->pins[pin].drv_data;
>> + pad->is_enabled = true;
>> /*
>> * Non-LV/MV subtypes only support 2 special functions,
>> * offsetting the dtestx function values by 2
>> --
>> Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
>> a Linux Foundation Collaborative Project.
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-10-17 4:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 6:15 [PATCH V1 0/2] *** Update is_enabled flag to be consistent *** fenglinw
2017-10-13 6:15 ` [PATCH V1 1/2] pinctrl: qcom: spmi-gpio: Read REG_EN_CTL to get initial enable state fenglinw
2017-10-16 22:19 ` Bjorn Andersson
2017-10-13 6:15 ` [PATCH V1 2/2] pinctrl: qcom: spmi-gpio: Set is_enabled flag in set_mux() fenglinw
2017-10-16 22:29 ` Bjorn Andersson
2017-10-17 4:36 ` Fenglin Wu [this message]
2017-10-20 9:51 ` 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=78f23ed8-7e3e-ffc9-bdbe-e10622e0c757@codeaurora.org \
--to=fenglinw@codeaurora.org \
--cc=aghayal@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=collinsd@codeaurora.org \
--cc=kgunda@codeaurora.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=subbaram@codeaurora.org \
--cc=wruan@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 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).