Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, "Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Chen-Yu Tsai" <wens@kernel.org>,
	"Jernej Skrabec" <jernej.skrabec@gmail.com>,
	"Samuel Holland" <samuel@sholland.org>,
	"Hans de Goede" <hansg@kernel.org>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Andre Przywara" <andre.przywara@arm.com>,
	"Jun Yan" <jerrysteve1101@gmail.com>,
	"Lukas Schmid" <lukas.schmid@netcube.li>,
	"J. Neuschäfer" <j.ne@posteo.net>,
	"Eric Biggers" <ebiggers@kernel.org>,
	"Michal Simek" <michal.simek@amd.com>,
	"Luca Weiss" <luca@lucaweiss.eu>, "Sven Peter" <sven@kernel.org>,
	"Maxime Ripard" <mripard@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org
Subject: Re: [PATCH v5 4/6] dt-bindings: input: sun4i-lradc-keys: Add A100/A133 compatible
Date: Wed, 24 Jun 2026 08:51:47 +0200	[thread overview]
Message-ID: <20260624-awesome-demonic-guppy-d494a7@quoll> (raw)
In-Reply-To: <20260623204824.691832-5-alexander.sverdlin@gmail.com>

On Tue, Jun 23, 2026 at 10:48:16PM +0200, Alexander Sverdlin wrote:
> The Allwinner A100/A133 SoCs have an LRADC which is compatible with the
> versions in existing SoCs. Add a compatible string for A100, with the R329
> fallback.
> 
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
> ---

Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof



  reply	other threads:[~2026-06-24  6:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23 20:48 [PATCH v5 0/6] Add support for Baijie Helper A133 board Alexander Sverdlin
2026-06-23 20:48 ` [PATCH v5 1/6] arm64: defconfig: Enable Allwinner LRADC input driver Alexander Sverdlin
2026-06-23 20:48 ` [PATCH v5 2/6] dt-bindings: vendor-prefixes: Add Shenzhen Baijie Technology Co., Ltd Alexander Sverdlin
2026-06-23 20:48 ` [PATCH v5 3/6] dt-bindings: arm: sunxi: Add Baijie HelperBoard A133 compatible Alexander Sverdlin
2026-06-23 20:48 ` [PATCH v5 4/6] dt-bindings: input: sun4i-lradc-keys: Add A100/A133 compatible Alexander Sverdlin
2026-06-24  6:51   ` Krzysztof Kozlowski [this message]
2026-06-23 20:48 ` [PATCH v5 5/6] arm64: dts: allwinner: a100: Add LRADC node Alexander Sverdlin
2026-06-23 20:48 ` [PATCH v5 6/6] arm64: dts: allwinner: A133: add support for Baijie Helper A133 board Alexander Sverdlin

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=20260624-awesome-demonic-guppy-d494a7@quoll \
    --to=krzk@kernel.org \
    --cc=alexander.sverdlin@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=ebiggers@kernel.org \
    --cc=hansg@kernel.org \
    --cc=j.ne@posteo.net \
    --cc=jernej.skrabec@gmail.com \
    --cc=jerrysteve1101@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=luca@lucaweiss.eu \
    --cc=lukas.schmid@netcube.li \
    --cc=michal.simek@amd.com \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    --cc=samuel@sholland.org \
    --cc=sven@kernel.org \
    --cc=wens@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