mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Linus Walleij <linusw@kernel.org>
To: xianwei.zhao@amlogic.com
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
	Kevin Hilman <khilman@baylibre.com>,
	 Jerome Brunet <jbrunet@baylibre.com>,
	 Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	linux-amlogic@lists.infradead.org,  linux-gpio@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: meson: a4: Add input enable pin configuration
Date: Fri, 14 Aug 2026 09:32:43 +0200	[thread overview]
Message-ID: <CAD++jLneywcc-c01_T+gn0B8R0eS-8L-uZaQFLFAP76d-+rMag@mail.gmail.com> (raw)
In-Reply-To: <20260812-input-enable-v1-1-81e5ca7772aa@amlogic.com>

On Wed, Aug 12, 2026 at 12:18 PM Xianwei Zhao via B4 Relay
<devnull+xianwei.zhao.amlogic.com@kernel.org> wrote:

> From: Xianwei Zhao <xianwei.zhao@amlogic.com>
>
> Add support for PIN_CONFIG_INPUT_ENABLE in the Amlogic A4 pinctrl
> driver.
>
> Use the existing output enable control to configure the input enable
> state, since the hardware uses the same control with inverse semantics.
>
> Also update PIN_CONFIG_OUTPUT_ENABLE handling to return the actual
> output enable state instead of treating any non-zero value as enabled.
>
> Signed-off-by: Xianwei Zhao <xianwei.zhao@amlogic.com>

I just applied this because we are close to the merge window and
it seems important and looks good to me.

I can always pull it out if the maintainers object.

Yours,
Linus Walleij

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      parent reply	other threads:[~2026-08-14  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12 10:17 Xianwei Zhao via B4 Relay
2026-08-12 10:28 ` sashiko-bot
2026-08-14  7:32 ` 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=CAD++jLneywcc-c01_T+gn0B8R0eS-8L-uZaQFLFAP76d-+rMag@mail.gmail.com \
    --to=linusw@kernel.org \
    --cc=jbrunet@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=xianwei.zhao@amlogic.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
all inboxes | Powered by JetHome®