From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Hugo Villeneuve <hugo@hugovil.com>,
hvilleneuve@dimonoff.com, lars@metafoo.de, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/3] dt-bindings: iio: adc: add ADS7924
Date: Fri, 23 Dec 2022 14:09:08 +0000 [thread overview]
Message-ID: <20221223140908.3b4a5458@jic23-huawei> (raw)
In-Reply-To: <01a5f912-10d2-d5fe-023e-e2e6613ac03b@linaro.org>
>
> > + description:
> > + Child nodes needed for each channel that the platform uses.
>
> I cannot understand this sentence at all. Instead describe the hardware
> you are here representing. What's this?
Needs rewording, but basically - "Which pins are connected to anything?"
next prev parent reply other threads:[~2022-12-23 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 20:36 [PATCH v1 0/3] iio: adc: ti-ads7924: add ADS7924 driver Hugo Villeneuve
2022-12-22 20:36 ` [PATCH v1 1/3] iio: adc: Kconfig: add SPI interface mention to AD7924 description Hugo Villeneuve
2022-12-23 14:12 ` Jonathan Cameron
2022-12-23 18:52 ` Hugo Villeneuve
2022-12-30 18:03 ` Jonathan Cameron
2022-12-22 20:36 ` [PATCH v1 2/3] iio: adc: ti-ads7924: add ADS7924 driver Hugo Villeneuve
2022-12-23 14:47 ` Jonathan Cameron
2023-01-10 15:38 ` Hugo Villeneuve
2022-12-22 20:36 ` [PATCH v1 3/3] dt-bindings: iio: adc: add ADS7924 Hugo Villeneuve
2022-12-23 8:19 ` Krzysztof Kozlowski
2022-12-23 14:09 ` Jonathan Cameron [this message]
2022-12-23 17:56 ` Hugo Villeneuve
2022-12-23 14:50 ` Jonathan Cameron
2022-12-23 19:24 ` Hugo Villeneuve
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=20221223140908.3b4a5458@jic23-huawei \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hugo@hugovil.com \
--cc=hvilleneuve@dimonoff.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).