From: Krzysztof Kozlowski <krzk@kernel.org>
To: Olivier Louvignes <olivier@mgcrea.io>,
Jonathan Cameron <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Paul Cercueil" <paul@crapouillou.net>,
"H . Nikolaus Schaller" <hns@goldelico.com>,
"Joshua Crofts" <crofts@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: iio: adc: Add the Ingenic X1600 ADC
Date: Fri, 6 Nov 2026 08:05:35 +0100 [thread overview]
Message-ID: <49e69d9c-6cb1-453f-bbf5-e2202f97e4ef@kernel.org> (raw)
In-Reply-To: <20261105213210.87457-2-olivier@mgcrea.io>
On 05/11/2026 22:32, Olivier Louvignes wrote:
> The X1600's SAR ADC has four auxiliary channels and none of the
> touchscreen or battery engines of the JZ47xx ADCs in ingenic,adc.yaml,
> so it gets a binding of its own.
>
> Signed-off-by: Olivier Louvignes <olivier@mgcrea.io>
> Tested-by: H. Nikolaus Schaller <hns@goldelico.com> # LX16 - driver only, no real world test
Drop, did not happen. Even comment says it did not happen!
Otherwise please explain me how this code was executed on a device.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-06 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 21:32 [PATCH v5 0/2] " Olivier Louvignes
2026-11-05 21:32 ` [PATCH v5 1/2] dt-bindings: " Olivier Louvignes
2026-11-06 7:05 ` Krzysztof Kozlowski [this message]
2026-11-06 8:05 ` H. Nikolaus Schaller
2026-11-06 8:11 ` Krzysztof Kozlowski
2026-11-06 8:18 ` H. Nikolaus Schaller
2026-11-06 8:23 ` Krzysztof Kozlowski
2026-11-06 9:59 ` Olivier Louvignes
2026-11-06 10:05 ` Krzysztof Kozlowski
2026-11-05 21:32 ` [PATCH v5 2/2] iio: adc: Add a driver for " Olivier Louvignes
2026-11-06 8:08 ` [PATCH v5 0/2] iio: adc: Add " H. Nikolaus Schaller
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=49e69d9c-6cb1-453f-bbf5-e2202f97e4ef@kernel.org \
--to=krzk@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=crofts@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=hns@goldelico.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=olivier@mgcrea.io \
--cc=paul@crapouillou.net \
--cc=robh@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
all inboxes | Powered by JetHome®