From: "Ivan T. Ivanov" <iivanov@mm-sol.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Jonathan Cameron <jic23@kernel.org>,
Sachin Kamat <sachin.kamat@linaro.org>,
John Stultz <john.stultz@linaro.org>,
linux-iio@vger.kernel.org, svarbanov@mm-sol.com,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] iio: inkern: Add of_xlate function to struct iio_dev
Date: Fri, 03 Oct 2014 18:08:22 +0300 [thread overview]
Message-ID: <1412348902.1027.48.camel@iivanov-dev> (raw)
In-Reply-To: <1412346717.2987.5.camel@spandruv-hsb-test>
On Fri, 2014-10-03 at 07:31 -0700, Srinivas Pandruvada wrote:
> On Thu, 2014-10-02 at 16:49 +0300, Ivan T. Ivanov wrote:
> > On Thu, 2014-10-02 at 15:30 +0200, Lars-Peter Clausen wrote:
> > > On 10/02/2014 02:32 PM, Ivan T. Ivanov wrote:
> > > > When #iio-cells is greater than '0', the driver could provide
> > > > a custom of_xlate function that reads the *args* and returns
> > > > the appropriate index in registered IIO channels array.
> > >
> > > Do you have an example of a device that doesn't want to use the default
> > > mapping? If yes please include it in the commit message, otherwise it is
> > > fairly hard to say whether this makes sense or not.
> >
> > Still not mainlined. You can find more detailed description of the
> > issue here[1] and driver here[2].
> I see your need. I wonder this mapping be done in individual client
> driver instead of creating another callback.
I am not sure I got you question. The idea is to provide default
1:1 mapping in core, which can be overwritten by client callback.
Regards,
Ivan
next prev parent reply other threads:[~2014-10-03 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 12:32 [PATCH] iio: inkern: Add of_xlate function to struct iio_dev Ivan T. Ivanov
2014-10-02 13:30 ` Lars-Peter Clausen
2014-10-02 13:49 ` Ivan T. Ivanov
2014-10-03 14:31 ` Srinivas Pandruvada
2014-10-03 15:08 ` Ivan T. Ivanov [this message]
2014-10-18 11:42 ` Jonathan Cameron
2014-10-18 11:50 ` Lars-Peter Clausen
2014-10-18 12:14 ` Jonathan Cameron
2014-10-20 11:22 ` Ivan T. Ivanov
2014-10-18 17:13 ` Srinivas Pandruvada
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=1412348902.1027.48.camel@iivanov-dev \
--to=iivanov@mm-sol.com \
--cc=jic23@kernel.org \
--cc=john.stultz@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=svarbanov@mm-sol.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