linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Simon Horman <horms+renesas@verge.net.au>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH V5] iio: adc: Add Renesas GyroADC driver
Date: Sun, 15 Jan 2017 18:06:32 +0100	[thread overview]
Message-ID: <17180a96-784b-883b-a4b5-11a3f6a42b98@gmail.com> (raw)
In-Reply-To: <EE493617-D579-4439-B64C-337F887BB7BD@kernel.org>

On 01/15/2017 05:28 PM, Jonathan Cameron wrote:
> 
> 
> On 15 January 2017 15:47:31 GMT+00:00, Marek Vasut <marek.vasut@gmail.com> wrote:
>> On 01/15/2017 03:05 PM, Jonathan Cameron wrote:
>>> On 15/01/17 00:14, Marek Vasut wrote:
>>>> Add IIO driver for the Renesas RCar GyroADC block. This block is a
>>>> simple 4/8-channel ADC which samples 12/15/24 bits of data every
>>>> cycle from all channels.
>>>>
>>>> Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
>>>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>>>> Cc: Simon Horman <horms+renesas@verge.net.au>
>>>> Cc: Jonathan Cameron <jic23@kernel.org>
>>>> Cc: linux-renesas-soc@vger.kernel.org
>>> One question about the name attribute and what it gives you. Looks
>> like another
>>> case of what Lars has been pointing out this morning.
>>>
>>> We had a load of these sneak in.  Changing them would break userspace
>> code
>>> so we can't fix them, but that attribute ought to give you something
>>> related to the part number.
>>>
>>> Here it might even be cute to give an indication of what is connected
>>> to it as part of the name.
>>
>> You can extract that information from the of_node, so I don't think
>> that
>> is a good idea, it'd only bring in duplication:
>>
>> ~ # cat /sys/bus/iio/devices/iio\:device0/of_node/adc@*/compatible
>> maxim,max11100
>>
> Fair enough
>>> J
>>
>> [...]
>>
>>>> +	ret = rcar_gyroadc_parse_subdevs(indio_dev);
>>>> +	if (ret)
>>>> +		return ret;
>>>> +
>>>> +	ret = rcar_gyroadc_init_supplies(indio_dev);
>>>> +	if (ret)
>>>> +		return ret;
>>>> +
>>>> +	priv->model = (enum rcar_gyroadc_model)of_id->data;
>>>> +
>>>> +	platform_set_drvdata(pdev, indio_dev);
>>>> +
>>>> +	indio_dev->name = dev_name(dev);
>>> What do you then get when you read /sys/bus/iio/iio\:deviceX/name?
>>
>> e6e54000.adc
>>
>>> Should be something like the part number, rather than the id of the
>>> parent device (I'm not 100% sure what that even is in this case!)
>>
>> You mean like "rcar-gyroadc" ? That works for me, sure.
> Yes, that will do nicely.


Done and V6 is out.


-- 
Best regards,
Marek Vasut

  reply	other threads:[~2017-01-15 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15  0:14 [PATCH V5] iio: adc: Add Renesas GyroADC driver Marek Vasut
2017-01-15 14:05 ` Jonathan Cameron
2017-01-15 15:47   ` Marek Vasut
2017-01-15 16:28     ` Jonathan Cameron
2017-01-15 17:06       ` Marek Vasut [this message]
2017-01-15 19:53         ` Jonathan Cameron
2017-01-15 20:21           ` Marek Vasut
2017-01-20 17:57             ` Marek Vasut

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=17180a96-784b-883b-a4b5-11a3f6a42b98@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-renesas-soc@vger.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).