From: lars@metafoo.de (Lars-Peter Clausen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] mfd: add support for Allwinner SoCs ADC
Date: Sun, 3 Jul 2016 18:49:49 +0200 [thread overview]
Message-ID: <5779422D.9060207@metafoo.de> (raw)
In-Reply-To: <87ab8638-926b-89ce-26a5-705a321d3066@kernel.org>
On 07/03/2016 01:17 PM, Jonathan Cameron wrote:
> On 28/06/16 09:18, Quentin Schulz wrote:
>> The Allwinner SoCs all have an ADC that can also act as a touchscreen
>> controller and a thermal sensor. For now, only the ADC and the thermal
>> sensor drivers are probed by the MFD, the touchscreen controller support
>> will be added later.
>>
>> Signed-off-by: Quentin Schulz <quentin.schulz@free-electrons.com>
> The code looks fine to me. The 'controversial' bit of this is listing
> iio-hwmon as an mfd child to get it to probe as a result of this being
> present. My immediately thought is that it should be separately
> described in the devicetree and hence instantiated outside of this driver.
The devicetree is a generic description of the hardware. The iio-hwmon
bridge is a software component that translates between two Linux specific
ABIs. In my opinion putting the later in the former is makes no sense, it is
simply not part of the hardware description.
Its quite terrible that we have the bindings in the first place, but I guess
we have to keep them considering they are ABI and there are existing users.
But we should definitely strongly discourage the introduction of new users.
It is policy whether an application wants to access a device using the IIO
or hwmon API. As such it must be managed by userspace, this is not something
that can be done using devicetree nor should it be something that is done on
a driver by driver basis.
- Lars
next prev parent reply other threads:[~2016-07-03 16:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 8:45 [PATCH 0/3] add support for Allwinner SoCs ADC Quentin Schulz
2016-06-28 8:18 ` [PATCH 1/3] mfd: " Quentin Schulz
2016-06-28 8:30 ` Antoine Tenart
2016-06-28 8:51 ` Antoine Tenart
2016-07-03 11:17 ` Jonathan Cameron
2016-07-03 16:49 ` Lars-Peter Clausen [this message]
2016-07-03 17:38 ` Guenter Roeck
2016-06-28 8:18 ` [PATCH 2/3] iio: adc: " Quentin Schulz
2016-06-28 8:32 ` Antoine Tenart
2016-07-03 11:54 ` Jonathan Cameron
2016-07-03 12:48 ` Jonathan Cameron
2016-07-03 15:43 ` Guenter Roeck
2016-07-04 7:26 ` Quentin Schulz
2016-07-04 16:29 ` Guenter Roeck
2016-07-05 7:40 ` Quentin Schulz
2016-06-28 8:18 ` [PATCH 3/3] hwmon: iio_hwmon: defer probe when no channel is found Quentin Schulz
2016-06-30 3:47 ` [3/3] " Guenter Roeck
2016-06-30 13:59 ` Jonathan Cameron
2016-06-30 14:49 ` Lars-Peter Clausen
2016-06-30 14:51 ` Guenter Roeck
2016-07-03 10:47 ` Jonathan Cameron
2016-07-03 15:48 ` Guenter Roeck
2016-06-29 3:28 ` [PATCH 0/3] add support for Allwinner SoCs ADC Chen-Yu Tsai
2016-07-01 9:45 ` Quentin Schulz
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=5779422D.9060207@metafoo.de \
--to=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.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).