linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
	konrad.dybcio@somainline.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] pinctrl: add support for SC8280XP LPASS LPI pinctrl
Date: Thu, 25 Aug 2022 14:33:06 +0200	[thread overview]
Message-ID: <CACRpkdY692EGPuTCbmr-rmpPg3BkGQBWtxA0cseGgOHrgsMRmg@mail.gmail.com> (raw)
In-Reply-To: <20220817113747.9111-1-srinivas.kandagatla@linaro.org>

On Wed, Aug 17, 2022 at 1:38 PM Srinivas Kandagatla
<srinivas.kandagatla@linaro.org> wrote:

> This patchset adds pinctrl driver to support pin configuration for LPASS
> (Low Power Audio SubSystem) LPI (Low Power Island) pinctrl on SC8280XP.
>
> This IP is an additional pin control block for Audio Pins on top the
> existing SoC Top level pin-controller.
>
> Tested this on Thinkpad X13s
>
> Thanks,
> Srini
>
> Changes since v1:
>         - removed unnecessary quotes in bindings
>         - remove lable in bindings
>         - fixed gpio pattern and removed an extra line after alt functions.

These patches applied too, same comment, if any further issues appear
the easiest is to just patch on top. It's nice to get some rotation in
linux-next
for these.

Yours,
Linus Walleij

      parent reply	other threads:[~2022-08-25 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 11:37 [PATCH v2 0/2] pinctrl: add support for SC8280XP LPASS LPI pinctrl Srinivas Kandagatla
2022-08-17 11:37 ` [PATCH v2 1/2] dt-bindings: pinctrl: qcom: Add sc8280xp lpass lpi pinctrl bindings Srinivas Kandagatla
2022-08-18 15:26   ` Rob Herring
2022-08-17 11:37 ` [PATCH v2 2/2] pinctrl: qcom: Add sc8280xp lpass lpi pinctrl driver Srinivas Kandagatla
2022-08-25 12:33 ` Linus Walleij [this message]

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=CACRpkdY692EGPuTCbmr-rmpPg3BkGQBWtxA0cseGgOHrgsMRmg@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.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).