Linux IIO development
 help / color / mirror / Atom feed
From: "Sean Nyekjær" <sean.nyekjaer@prevas.dk>
To: Lars-Peter Clausen <lars@metafoo.de>, <linux-iio@vger.kernel.org>
Cc: <devicetree@vger.kernel.org>
Subject: Re: [PATCH 1/2] iio: ad5755: add support for dt bindings
Date: Wed, 3 Feb 2016 10:29:21 +0100	[thread overview]
Message-ID: <56B1C871.6070105@prevas.dk> (raw)
In-Reply-To: <56B0DB5E.7060608@metafoo.de>



On 2016-02-02 17:37, Lars-Peter Clausen wrote:
> On 02/02/2016 04:57 PM, Sean Nyekjær wrote:
>>
>> On 2016-02-02 16:33, Lars-Peter Clausen wrote:
>>> On 02/02/2016 01:36 PM, Sean Nyekjaer wrote:
>>>> Still missing a way to provide default modes and settings
>>>> for the driver from dt, but I see this as a start.
>>>>
>>>> Signed-off-by: Sean Nyekjaer <sean.nyekjaer@prevas.dk>
>>> Hi,
>>>
>>> Thanks for the patch.
>> :-)
>>>> ---
>>>>    drivers/iio/dac/ad5755.c | 10 ++++++++++
>>>>    1 file changed, 10 insertions(+)
>>>>
>>>> diff --git a/drivers/iio/dac/ad5755.c b/drivers/iio/dac/ad5755.c
>>>> index bfb350a..e1b6e78 100644
>>>> --- a/drivers/iio/dac/ad5755.c
>>>> +++ b/drivers/iio/dac/ad5755.c
>>>> @@ -607,6 +607,16 @@ static const struct spi_device_id ad5755_id[] = {
>>>>    };
>>>>    MODULE_DEVICE_TABLE(spi, ad5755_id);
>>>>    +static const struct of_device_id ad5755_of_match[] = {
>>>> +    { .compatible = "adi,ad5755" },
>>>> +    { .compatible = "adi,ad5755-1" },
>>>> +    { .compatible = "adi,ad5757" },
>>>> +    { .compatible = "adi,ad5735" },
>>>> +    { .compatible = "adi,ad5737" },
>>> This needs to set the ID for the device type, so that the driver gets
>>> instantiated for the correct devicetype. And in the probe function check if
>>> the driver was probed via DT (by checking spi->dev.of_node) and if it does
>>> get the ID from the of_device_id rather the spi_device_id.
If I probe the driver via DT the spi_get_device_id(spi)->driver_data 
returns the type...
So this works as it is :-)

I'll continue with the proposal...
>> I was planning on doing that.
>> And I was experimenting with providing modes and settings for every channel
>> from the dt.
>> Is the DAC the only output devices in IIO?
> There is also support for programmable potentiometers (sometimes called
> RDAC), but that's it.
>
>> I will send an proposal tomorrow :-) And thereby (maybe) pave the way for
>> the runtime mode switching
>>
>> Should we drop the platform data support and only rely on dt?
> No, there might still be some people depending on it. I don't think the
> burden of continuing to maintain the platform data support is that high.
>
> - Lars


      reply	other threads:[~2016-02-03  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 12:36 [PATCH 1/2] iio: ad5755: add support for dt bindings Sean Nyekjaer
2016-02-02 12:36 ` [PATCH 2/2] iio: ad5755: Add DT binding documentation Sean Nyekjaer
2016-02-02 21:55   ` Rob Herring
2016-02-02 15:33 ` [PATCH 1/2] iio: ad5755: add support for dt bindings Lars-Peter Clausen
2016-02-02 15:57   ` Sean Nyekjær
2016-02-02 16:37     ` Lars-Peter Clausen
2016-02-03  9:29       ` Sean Nyekjær [this message]

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=56B1C871.6070105@prevas.dk \
    --to=sean.nyekjaer@prevas.dk \
    --cc=devicetree@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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