From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Michal Simek <michal.simek@xilinx.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Manish Narani <manish.narani@xilinx.com>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
robh+dt@kernel.org, mark.rutland@arm.com, sudeep.holla@arm.com,
amit.kucheria@linaro.org, leoyang.li@nxp.com, broonie@kernel.org,
arnaud.pouliquen@st.com, eugen.hristev@microchip.com,
rdunlap@infradead.org, geert@linux-m68k.org, ak@it-klinger.de,
freeman.liu@spreadtrum.com, lukas@wunner.de,
vilhelm.gray@gmail.com, gregkh@linuxfoundation.org,
kstewart@linuxfoundation.org, sgoud@xilinx.com,
anirudh@xilinx.com, linux-iio@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/4] iio: Documentation: Add Xilinx AMS sysfs documentation
Date: Mon, 17 Sep 2018 11:06:12 +0100 [thread overview]
Message-ID: <20180917110215.00002846@huawei.com> (raw)
In-Reply-To: <cf2acc8a-ed2d-27f4-ca58-3e2132e17d2a@xilinx.com>
On Mon, 17 Sep 2018 11:56:08 +0200
Michal Simek <michal.simek@xilinx.com> wrote:
> On 16.9.2018 12:12, Jonathan Cameron wrote:
> > On Fri, 14 Sep 2018 12:48:28 +0530
> > Manish Narani <manish.narani@xilinx.com> wrote:
> >
> >> Add documentation for xilinx-ams driver. This contains information about
> >> various voltages and temperatures on PS (Processing System), PL
> >> (Programmable Logic) and AMS Control Block.
> >>
> >> Signed-off-by: Manish Narani <manish.narani@xilinx.com>
> > The more I look at this device the more I'm convinced it is very much a dedicated
> > hardware monitoring function, not a generic ADC sensing unit at all.
> >
> > Hmm. It is still fine to have it in IIO but you need to think in detail
> > about how you are going to interface this to hwmon via the iio-hwmon bridge.
> >
> > Some of the interface complexity should only really be apparent when we hit
> > hwmon perhaps rather than having so many different custom interfaces in IIO.
> >
> > Please also loop in the maintainers and lists for hwmon in the next
> > version so we can get their input.
>
> Isn't there iio-hwmon driver for this?
>
> Thanks,
> Michal
Absolutely. The interesting bit is that if we are planning to actually expose
the many monitoring channels via iio-hwmon IIRC it won't use the extended names
at all (I may have missremembered this thogh). As such we may want to reduced
the amount of custom ABI in IIO in favour of a level of opaqueness with the
'real' interface provided by the iio-hwmon bridge driver. A quick glance
suggested we may need to increase the information exposed by the iio-hwmon
driver to make this work.
When we have run into cases like this (a very much hardware monitoring oriented
device with a few general purpose channels) in the past we have always gotten
agreement from the hwmon maintainers that they are happy with using an IIO provider
and the iio-hwmon driver route. It is just nice to keep everyone in agreement
and have no surprises!
Jonathan
next prev parent reply other threads:[~2018-09-17 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 7:18 [PATCH v2 0/4] Add Xilinx AMS Driver Manish Narani
2018-09-14 7:18 ` [PATCH v2 1/4] dt-bindings: iio: adc: Add Xilinx AMS binding documentation Manish Narani
2018-09-14 8:31 ` Peter Meerwald-Stadler
2018-09-16 10:01 ` Jonathan Cameron
2018-09-14 7:18 ` [PATCH v2 2/4] iio: Documentation: Add Xilinx AMS sysfs documentation Manish Narani
2018-09-16 10:12 ` Jonathan Cameron
2018-09-17 9:56 ` Michal Simek
2018-09-17 10:06 ` Jonathan Cameron [this message]
2018-09-17 10:23 ` Michal Simek
2018-09-14 7:18 ` [PATCH v2 3/4] iio: adc: Add Xilinx AMS driver Manish Narani
2018-09-14 8:52 ` Peter Meerwald-Stadler
2018-09-14 11:59 ` Himanshu Jha
2018-09-14 21:30 ` Randy Dunlap
2018-09-16 10:34 ` Jonathan Cameron
2018-09-14 7:18 ` [PATCH v2 4/4] arm64: zynqmp: DT: Add Xilinx AMS node Manish Narani
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=20180917110215.00002846@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=ak@it-klinger.de \
--cc=amit.kucheria@linaro.org \
--cc=anirudh@xilinx.com \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@microchip.com \
--cc=freeman.liu@spreadtrum.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=kstewart@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=manish.narani@xilinx.com \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pmeerw@pmeerw.net \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sgoud@xilinx.com \
--cc=sudeep.holla@arm.com \
--cc=vilhelm.gray@gmail.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;
as well as URLs for NNTP newsgroup(s).