From: Jonathan Cameron <jic23@kernel.org>
To: Daniel Baluta <daniel.baluta@intel.com>, Peter Rosin <peda@axentia.se>
Cc: Cristina Moraru <cristina.moraru09@gmail.com>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"lars@metafoo.de" <lars@metafoo.de>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"octavian.purdila@intel.com" <octavian.purdila@intel.com>
Subject: Re: [PATCH] iio: max5487: Add support for Maxim digital potentiometers
Date: Sun, 3 Apr 2016 10:25:55 +0100 [thread overview]
Message-ID: <5700E1A3.6020204@kernel.org> (raw)
In-Reply-To: <CAEnQRZBBVuYSBNPXTTSR0UeiQa8UH8TVndzn5AhrWWYp-iSQKA@mail.gmail.com>
On 01/04/16 09:28, Daniel Baluta wrote:
>> .wipers and .max_pos need not be in max5487_cfg, they are common.
>> .wipers isn't even used. Which means that if you like, you can
>> use the ohms reading as the driver_data directly instead of going
>> via the MAX548x enumeration, see below. Or is there some reason
>> not doing so?
>
> You make a good point. Anyhow we thought of a generic approach. In the future
> this chip family could support more wipers with different positions.
Make it generic when you need too. Easy enough to add later!
J
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-04-03 9:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 11:21 [PATCH] iio: max5487: Add support for Maxim digital potentiometers Cristina Moraru
2016-03-24 11:42 ` Daniel Baluta
2016-03-24 21:46 ` Peter Rosin
2016-04-01 8:28 ` Daniel Baluta
2016-04-03 9:25 ` Jonathan Cameron [this message]
2016-03-25 10:20 ` Peter Rosin
2016-04-01 8:33 ` Daniel Baluta
2016-04-09 8:24 ` [PATCH v2] " Cristina Moraru
2016-04-10 11:24 ` Jonathan Cameron
2016-04-10 12:47 ` Joachim Eastwood
2016-04-10 13:10 ` Joachim Eastwood
2016-05-17 13:11 ` [PATCH v3] " Cristina Moraru
2016-05-17 13:33 ` Peter Meerwald-Stadler
2016-05-19 2:21 ` Matt Ranostay
2016-05-18 9:15 ` [PATCH v4] " Cristina Moraru
2016-05-19 5:55 ` [PATCH v5] " Cristina Moraru
2016-05-21 19:14 ` 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=5700E1A3.6020204@kernel.org \
--to=jic23@kernel.org \
--cc=cristina.moraru09@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=peda@axentia.se \
--cc=pmeerw@pmeerw.net \
/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).