From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
MSM <linux-arm-msm@vger.kernel.org>,
gpio <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v1] pinctrl: msm8998: Squash TSIF pins together
Date: Wed, 26 Jun 2019 16:46:16 +0200 [thread overview]
Message-ID: <2b531817-b1eb-da8c-9edf-25a0b9b2acda@free.fr> (raw)
In-Reply-To: <CAOCk7Nqi6j07TzH0tp8x8NzwqX1CAG8wj55Yvxw2tVC8cXhxmQ@mail.gmail.com>
On 26/06/2019 16:42, Jeffrey Hugo wrote:
> On Wed, Jun 26, 2019 at 8:40 AM Marc Gonzalez <marc.w.gonzalez@free.fr> wrote:
>
>> Preamble: Rename tsif1 to tsif0, tsif2 to tsif1.
>> Squash tsif0 pins into a single function. Same for tsif1.
>>
>> Signed-off-by: Marc Gonzalez <marc.w.gonzalez@free.fr>
>> ---
>> .../bindings/pinctrl/qcom,msm8998-pinctrl.txt | 19 ++---
>> drivers/pinctrl/qcom/pinctrl-msm8998.c | 76 +++++--------------
>> 2 files changed, 24 insertions(+), 71 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,msm8998-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/qcom,msm8998-pinctrl.txt
>> index 00174f08ba1d..47b0f30a39e9 100644
>> --- a/Documentation/devicetree/bindings/pinctrl/qcom,msm8998-pinctrl.txt
>> +++ b/Documentation/devicetree/bindings/pinctrl/qcom,msm8998-pinctrl.txt
>> @@ -124,9 +124,8 @@ to specify in a pin configuration subnode:
>> qlink_request, qua_mi2s, sd_card, sd_write, sdc40, sdc41,
>> sdc42, sdc43, sdc4_clk, sdc4_cmd, sec_mi2s, sp_cmu,
>> spkr_i2s, ssbi1, ssc_irq, ter_mi2s, tgu_ch0, tgu_ch1,
>> - tsense_pwm1, tsense_pwm2, tsif1_clk, tsif1_data, tsif1_en,
>> - tsif1_error, tsif1_sync, tsif2_clk, tsif2_data, tsif2_en,
>> - tsif2_error, tsif2_sync, uim1_clk, uim1_data, uim1_present,
>> + tsense_pwm1, tsense_pwm2, tsif0, tsif1,
>> + uim1_clk, uim1_data, uim1_present,
>> uim1_reset, uim2_clk, uim2_data, uim2_present, uim2_reset,
>> uim_batt, usb_phy, vfr_1, vsense_clkout, vsense_data0,
>> vsense_data1, vsense_mode, wlan1_adc0, wlan1_adc1,
>> @@ -179,15 +178,9 @@ Example:
>> #interrupt-cells = <2>;
>>
>> uart_console_active: uart_console_active {
>> - mux {
>> - pins = "gpio4", "gpio5";
>> - function = "blsp_uart8_a";
>> - };
>> -
>> - config {
>> - pins = "gpio4", "gpio5";
>> - drive-strength = <2>;
>> - bias-disable;
>> - };
>> + pins = "gpio4", "gpio5";
>> + function = "blsp_uart8_a";
>> + drive-strength = <2>;
>> + bias-disable;
>> };
>
> Whats with these "uart" changes? Modernizing the example? Doesn't
> seem related to the commit text...
Good point. I squashed one commit too many. I'll drop that hunk
in v2. (Yes, I meant to document the syntax recommended by Bjorn.)
Regards.
next prev parent reply other threads:[~2019-06-26 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 16:12 How to write "modern" pinctrl DT node Marc Gonzalez
2019-06-11 16:50 ` Jonathan Neuschäfer
2019-06-11 18:05 ` Bjorn Andersson
2019-06-20 11:02 ` Marc Gonzalez
2019-06-20 18:41 ` Bjorn Andersson
2019-06-26 14:38 ` [PATCH v1] pinctrl: msm8998: Squash TSIF pins together Marc Gonzalez
2019-06-26 14:42 ` Jeffrey Hugo
2019-06-26 14:46 ` Marc Gonzalez [this message]
2019-06-26 15:30 ` Jonathan Neuschäfer
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=2b531817-b1eb-da8c-9edf-25a0b9b2acda@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=bjorn.andersson@linaro.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).