public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Nick Xie <nick@khadas.com>,
	neil.armstrong@linaro.org, khilman@baylibre.com,
	martin.blumenstingl@googlemail.com, jbrunet@baylibre.com,
	dlechner@baylibre.com, andy@kernel.org, krzk+dt@kernel.org,
	robh@kernel.org, conor+dt@kernel.org, linux-iio@vger.kernel.org,
	linux-amlogic@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] iio: adc: meson-saradc: add support for Meson S4
Date: Tue, 24 Mar 2026 08:07:15 +0100	[thread overview]
Message-ID: <171e30f3-e294-40fb-8731-476fb51d5a3c@kernel.org> (raw)
In-Reply-To: <20260323200501.6c116226@jic23-huawei>

On 23/03/2026 21:05, Jonathan Cameron wrote:
> On Mon, 23 Mar 2026 08:54:21 +0100
> Krzysztof Kozlowski <krzk@kernel.org> wrote:
> 
>> On Mon, Mar 23, 2026 at 09:34:06AM +0800, Nick Xie wrote:
>>> Add support for the SARADC found on the Amlogic Meson S4 SoC.
>>> According to the documentation and current testing, it is fully
>>> compatible with the G12A parameter set, so we reuse
>>> `meson_sar_adc_g12a_data` for this new compatible string.
>>>
>>> Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
>>> Signed-off-by: Nick Xie <nick@khadas.com>
>>> ---
>>>  drivers/iio/adc/meson_saradc.c | 8 ++++++++
>>>  1 file changed, 8 insertions(+)
>>>
>>> diff --git a/drivers/iio/adc/meson_saradc.c b/drivers/iio/adc/meson_saradc.c
>>> index 47cd350498a0d..3ac48b7842c4f 100644
>>> --- a/drivers/iio/adc/meson_saradc.c
>>> +++ b/drivers/iio/adc/meson_saradc.c
>>> @@ -1313,6 +1313,11 @@ static const struct meson_sar_adc_data meson_sar_adc_g12a_data = {
>>>  	.name = "meson-g12a-saradc",
>>>  };
>>>  
>>> +static const struct meson_sar_adc_data meson_sar_adc_s4_data = {
>>> +	.param = &meson_sar_adc_g12a_param,
>>> +	.name = "meson-s4-saradc",
>>> +};
>>> +
>>>  static const struct of_device_id meson_sar_adc_of_match[] = {
>>>  	{
>>>  		.compatible = "amlogic,meson8-saradc",
>>> @@ -1341,6 +1346,9 @@ static const struct of_device_id meson_sar_adc_of_match[] = {
>>>  	}, {
>>>  		.compatible = "amlogic,meson-g12a-saradc",
>>>  		.data = &meson_sar_adc_g12a_data,
>>> +	}, {
>>> +		.compatible = "amlogic,meson-s4-saradc",  
>>
>> The point of compatible devices is to not add such entries. Drop.
> It's used for naming in the userspace ABI which is supposed to reflect the part number.

Indeed, I saw this pattern in more places. Does userspace need it? There
is no "compatible" entry shown?

If there is no, then probably this could be automated by taking the name
from compatible after ',', but that would be out of scope for this set,
so here it is fine.


Best regards,
Krzysztof

  reply	other threads:[~2026-03-24  7:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23  1:34 [PATCH v2 0/4] iio: adc: meson-saradc: add support for Meson S4 Nick Xie
2026-03-23  1:34 ` [PATCH v2 1/4] dt-bindings: iio: adc: amlogic,meson-saradc: add S4 compatible Nick Xie
2026-03-23  7:53   ` Krzysztof Kozlowski
2026-03-23 21:39     ` Martin Blumenstingl
2026-03-23  1:34 ` [PATCH v2 2/4] iio: adc: meson-saradc: add support for Meson S4 Nick Xie
2026-03-23  7:54   ` Krzysztof Kozlowski
2026-03-23 20:05     ` Jonathan Cameron
2026-03-24  7:07       ` Krzysztof Kozlowski [this message]
2026-03-24  9:06         ` Jonathan Cameron
2026-03-23  1:34 ` [PATCH v2 3/4] arm64: dts: amlogic: meson-s4: add internal SARADC controller Nick Xie
2026-03-23  1:34 ` [PATCH v2 4/4] arm64: dts: amlogic: meson-s4-s905y4-khadas-vim1s: add Function key support Nick Xie

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=171e30f3-e294-40fb-8731-476fb51d5a3c@kernel.org \
    --to=krzk@kernel.org \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jbrunet@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=khilman@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=neil.armstrong@linaro.org \
    --cc=nick@khadas.com \
    --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