From: David Lechner <david@lechnology.com>
To: Jonathan Cameron <jic23@kernel.org>,
devicetree@vger.kernel.org, linux-iio@vger.kernel.org
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] ti,ads7950 device tree bindings
Date: Sun, 15 Jan 2017 17:44:57 -0600 [thread overview]
Message-ID: <b60edc70-1d0f-fbfc-6ae9-1e6e5e3525d1@lechnology.com> (raw)
In-Reply-To: <c4c59921-d0dc-0858-8d66-c56fa38d3b50@kernel.org>
On 01/15/2017 07:58 AM, Jonathan Cameron wrote:
> On 11/01/17 17:52, David Lechner wrote:
>> This series adds device tree bindings for the TI ADS7950 family of A/DC chips.
>> The series includes the bindings documentation and some fixes to the iio driver
>> to make it work with the device tree bindings.
>>
>> FYI, the ads7950 driver has not made it into mainline yet, so no worries about
>> breaking anyone with these changes.
>>
> And here's the bit I failed to read!
>
> As an extra point, could you confirm what /sys/bus/iio/iio\:deviceX/name for this
> one reads? I have a feeling this is another case of what Lars has been pointing
> out in other drivers this morning. That name should be the device part number..
>
cat /sys/bus/iio/devices/iio\:device0/name
ads7957
This is the part number for the specific chip I am using. So, I am
guessing that it is correct unless it is supposed to be upper case or
something like that.
> Thanks,
>
> Jonathan
>> David Lechner (3):
>> DT/bindings: Add bindings for TI ADS7950 A/DC chips
>> iio: adc: ti-ads7950: Drop "ti-" prefix from module name
>> iio: adc: ti-ads7950: Change regulator matching string to "vref"
>>
>> .../devicetree/bindings/iio/adc/ti-ads7950.txt | 23 ++++++++++++++++
>> drivers/iio/adc/ti-ads7950.c | 32 +++++++++++-----------
>> 2 files changed, 39 insertions(+), 16 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/iio/adc/ti-ads7950.txt
>>
>
next prev parent reply other threads:[~2017-01-15 23:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 17:52 [PATCH 0/3] ti,ads7950 device tree bindings David Lechner
2017-01-11 17:52 ` [PATCH 1/3] DT/bindings: Add bindings for TI ADS7950 A/DC chips David Lechner
2017-01-14 12:53 ` Jonathan Cameron
2017-01-14 18:00 ` David Lechner
2017-01-15 13:52 ` Jonathan Cameron
2017-01-18 19:54 ` Rob Herring
2017-01-11 17:52 ` [PATCH 2/3] iio: adc: ti-ads7950: Drop "ti-" prefix from module name David Lechner
2017-01-14 12:49 ` Jonathan Cameron
2017-01-14 18:07 ` David Lechner
2017-01-15 13:54 ` Jonathan Cameron
2017-01-11 17:52 ` [PATCH 3/3] iio: adc: ti-ads7950: Change regulator matching string to "vref" David Lechner
2017-01-14 12:52 ` Jonathan Cameron
2017-01-14 18:09 ` David Lechner
2017-01-15 13:55 ` Jonathan Cameron
2017-01-15 13:58 ` [PATCH 0/3] ti,ads7950 device tree bindings Jonathan Cameron
2017-01-15 23:44 ` David Lechner [this message]
2017-01-21 15:08 ` 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=b60edc70-1d0f-fbfc-6ae9-1e6e5e3525d1@lechnology.com \
--to=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pmeerw@pmeerw.net \
--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).