From: Jonathan Cameron <jic23@kernel.org>
To: Xander Huff <xander.huff@ni.com>,
lars@metafoo.de, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org
Cc: michal.simek@xilinx.com, soren.brinkmann@xilinx.com,
knaack.h@gmx.de, pmeerw@pmeerw.net, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org,
ben.shelton@ni.com, joshc@ni.com, joe.hershberger@ni.com
Subject: Re: [PATCH v2 2/2] iio: adc: xilinx-xadc: Add label as an optional argument for aux channels
Date: Sun, 07 Jun 2015 17:49:26 +0100 [thread overview]
Message-ID: <55747616.1010901@kernel.org> (raw)
In-Reply-To: <1432135352-29848-2-git-send-email-xander.huff@ni.com>
On 20/05/15 16:22, Xander Huff wrote:
> To better facilitate user-mode access to optional aux channels, allow
> device trees to specify a custom label for defined channels.
>
> Signed-off-by: Xander Huff <xander.huff@ni.com>
> Reviewed-by: Joe Hershberger <joe.hershberger@ni.com>
> Reviewed-by: Josh Cartwright <joshc@ni.com>
> ---
> drivers/iio/adc/xilinx-xadc-core.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/iio/adc/xilinx-xadc-core.c b/drivers/iio/adc/xilinx-xadc-core.c
> index ce93bd8..bda4241 100644
> --- a/drivers/iio/adc/xilinx-xadc-core.c
> +++ b/drivers/iio/adc/xilinx-xadc-core.c
> @@ -1119,6 +1119,9 @@ static int xadc_parse_dt(struct iio_dev *indio_dev, struct device_node *np,
> if (ret || reg > 16)
> continue;
>
> + of_property_read_string(child, "label",
> + &chan->extend_name);
> +
> if (of_property_read_bool(child, "xlnx,bipolar"))
> chan->scan_type.sign = 's';
>
>
I think what Lars was suggesting was a change to the IIO side of this rather than
just changing the device tree binding. Perhaps an additional per channel attribute
called _label which would allow for board specific labelling?
next prev parent reply other threads:[~2015-06-07 16:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 22:44 [PATCH 1/2] devicetree: xilinx-xadc: Add optional xlnx,extend-name property Xander Huff
2015-05-07 22:44 ` [PATCH 2/2] iio: adc: xilinx-xadc: Add xlnx,extend-name as an optional argument for aux channels Xander Huff
2015-05-19 17:53 ` Lars-Peter Clausen
2015-05-20 15:22 ` [PATCH v2 1/2] devicetree: xilinx-xadc: Add optional label property Xander Huff
2015-05-20 15:22 ` [PATCH v2 2/2] iio: adc: xilinx-xadc: Add label as an optional argument for aux channels Xander Huff
2015-06-07 16:49 ` Jonathan Cameron [this message]
2015-06-08 13:49 ` Josh Cartwright
2015-06-14 11:20 ` Jonathan Cameron
2015-05-23 11:23 ` [PATCH 2/2] iio: adc: xilinx-xadc: Add xlnx,extend-name " Jonathan Cameron
2015-05-26 9:38 ` Lars-Peter Clausen
2015-05-26 19:05 ` Xander Huff
2015-05-08 18:43 ` [PATCH 1/2] devicetree: xilinx-xadc: Add optional xlnx,extend-name property Jonathan Cameron
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=55747616.1010901@kernel.org \
--to=jic23@kernel.org \
--cc=ben.shelton@ni.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=joe.hershberger@ni.com \
--cc=joshc@ni.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=soren.brinkmann@xilinx.com \
--cc=xander.huff@ni.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;
as well as URLs for NNTP newsgroup(s).