From: Andreas Kemnade <andreas@kemnade.info>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Discussions about the Letux Kernel <letux-kernel@openphoenux.org>,
devicetree@vger.kernel.org, lars@metafoo.de,
linux-pm@vger.kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, sre@kernel.org, robh+dt@kernel.org,
leonard.crestez@nxp.com, lee.jones@linaro.org
Subject: Re: [Letux-kernel] [PATCH 0/4] mfd: rn5t618: Extend ADC support
Date: Sat, 3 Jul 2021 18:55:40 +0200 [thread overview]
Message-ID: <20210703185540.5b6bec20@aktux> (raw)
In-Reply-To: <20210703183932.75c7012a@aktux>
On Sat, 3 Jul 2021 18:39:40 +0200
Andreas Kemnade <andreas@kemnade.info> wrote:
> Hi,
>
> On Sat, 3 Jul 2021 16:59:50 +0100
> Jonathan Cameron <jic23@kernel.org> wrote:
>
> > On Sat, 3 Jul 2021 10:42:20 +0200
> > Andreas Kemnade <andreas@kemnade.info> wrote:
> >
> > > Add devicetree support so that consumers can reference the channels
> > > via devicetree, especially the power subdevice can make use of that
> > > to provide voltage_now properties.
> >
> > Does the mapping vary from board to board? Often these mappings are
> > internal to the chip so might as well be provided hard coded in the
> > relevant drivers rather than via DT. See drivers that have iio_map
> > structure arrays.
> >
> Most things are internal to the chip, but
> AIN1/AIN0 are external and could be connected to anything.
>
hmm, iio_map stuff looks nice, so before messing with devicetree,
I could solve 90% of the problem by just using iio_map? For my use
cases it is enough to have the internal stuff at the moment. That would
simplify stuff a lot.
So I could go forward with the iio_map stuff now, and if there is a use
case for AIN1/0, the devicetree stuff can be added later?
Regards,
Andreas
next prev parent reply other threads:[~2021-07-03 16:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 8:42 [PATCH 0/4] mfd: rn5t618: Extend ADC support Andreas Kemnade
2021-07-03 8:42 ` [PATCH 1/4] dt-bindings: mfd: ricoh,rn5t618: ADC related nodes and properties Andreas Kemnade
2021-07-03 16:02 ` Jonathan Cameron
2021-07-03 16:43 ` Andreas Kemnade
2021-07-12 14:41 ` Rob Herring
2021-07-03 8:42 ` [PATCH 2/4] mfd: rn5t618: Add of compatibles for ADC and power Andreas Kemnade
2021-07-03 16:04 ` Jonathan Cameron
2021-07-03 16:31 ` Andreas Kemnade
2021-07-04 16:17 ` Jonathan Cameron
2021-07-05 7:36 ` Lee Jones
2021-07-05 8:31 ` Jonathan Cameron
2021-07-05 10:03 ` Andreas Kemnade
2021-07-05 7:37 ` Lee Jones
2021-07-03 8:42 ` [PATCH 3/4] iio: rn5t618: Add devicetree support Andreas Kemnade
2021-07-03 16:12 ` Jonathan Cameron
2021-07-03 8:42 ` [PATCH 4/4] power: supply: rn5t618: Add voltage_now property Andreas Kemnade
2021-07-03 11:41 ` kernel test robot
2021-07-03 14:35 ` kernel test robot
2021-07-03 15:29 ` Andreas Kemnade
2021-07-03 16:12 ` Jonathan Cameron
2021-07-03 15:59 ` [PATCH 0/4] mfd: rn5t618: Extend ADC support Jonathan Cameron
2021-07-03 16:39 ` Andreas Kemnade
2021-07-03 16:55 ` Andreas Kemnade [this message]
2021-07-04 16:10 ` [Letux-kernel] " Jonathan Cameron
2021-07-05 11:18 ` Andreas Kemnade
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=20210703185540.5b6bec20@aktux \
--to=andreas@kemnade.info \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=leonard.crestez@nxp.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sre@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).