From: Linus Walleij <linus.walleij@linaro.org>
To: Rajendra Nayak <rnayak@codeaurora.org>,
John Stultz <john.stultz@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] pinctrl: qcom: Add sc7280 pinctrl driver
Date: Tue, 24 Nov 2020 09:38:55 +0100 [thread overview]
Message-ID: <CACRpkdbrOKct5v2YY6L8G5fweP=eOFpcS9=Z6nUyA2E4Of+h7Q@mail.gmail.com> (raw)
In-Reply-To: <1604570192-15057-2-git-send-email-rnayak@codeaurora.org>
On Thu, Nov 5, 2020 at 10:56 AM Rajendra Nayak <rnayak@codeaurora.org> wrote:
> Add initial pinctrl driver to support pin configuration with
> pinctrl framework for SC7280 SoC
>
> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
> ---
> v2: Consolidated functions under phase_flag and qdss
> Moved ufs reset pin to pin175 so its exposed as a gpio
> npios updated from 175 to 176
Patch applied.
> +config PINCTRL_SC7280
> + tristate "Qualcomm Technologies Inc SC7280 pin controller driver"
> + depends on GPIOLIB && OF
> + select PINCTRL_MSM
I changed this to depends on PINCTRL_MSM in the process to stay
consistent with John's changes to modularize the pin controllers.
Yours,
Linus Walleij
next prev parent reply other threads:[~2020-11-24 8:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 9:56 [PATCH v2 1/2] dt-bindings: pinctrl: qcom: Add sc7280 pinctrl bindings Rajendra Nayak
2020-11-05 9:56 ` [PATCH v2 2/2] pinctrl: qcom: Add sc7280 pinctrl driver Rajendra Nayak
2020-11-10 13:39 ` Linus Walleij
2020-11-10 21:23 ` Bjorn Andersson
2020-11-24 8:38 ` Linus Walleij [this message]
2020-11-10 21:24 ` [PATCH v2 1/2] dt-bindings: pinctrl: qcom: Add sc7280 pinctrl bindings Bjorn Andersson
2020-11-24 8:37 ` 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='CACRpkdbrOKct5v2YY6L8G5fweP=eOFpcS9=Z6nUyA2E4Of+h7Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@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 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.