From: Jonathan Cameron <jic23@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>, Jean Delvare <jdelvare@suse.de>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/3] iio: imu: inv_mpu6050: Added adapter class
Date: Thu, 01 Jan 2015 12:27:14 +0000 [thread overview]
Message-ID: <54A53D22.4060903@kernel.org> (raw)
In-Reply-To: <20141231102554.GC1461@katana>
On 31/12/14 10:25, Wolfram Sang wrote:
> On Fri, Dec 26, 2014 at 12:37:36PM +0000, Jonathan Cameron wrote:
>> On 15/12/14 21:19, Srinivas Pandruvada wrote:
>>> To use i2c auto detect to work we need to have a non zero class.
>>> The closest class is I2C_CLASS_HWMON, as it defined to be used
>>> with all hw monitoring drivers.
>>>
>>> Also this class is already used by some iio driver, hid drivers, led
>>> and misc drivers. So this is not new that this is used outside
>>> hwmon drivers.
>>>
>>> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
>> Been meaning to sort this out for a while. We really shouldn't be camping
>> on the HWMON class (nor should anyone else).
>>
>> Wolfram, do you mind new classes being added?
>
> In general, I wouldn't mind but I wonder if it makes sense here. DDC and
> SPD are very special I2C uses where access should be limited, so a
> seperate class makes sense IMO. HWMON has a specific name, but really
> became "everything what people could hook to their I2C bus" these days.
> So, if anything, we could think about renaming I2C_CLASS_HWMON to
> I2C_CLASS_STANDARD or something (or at least add a comment about that in
> i2c.h)? I'd think IIO devices fall into the default category. Please say
> if you think different. If we'd add the IIO class, most drivers will
> need patches to support IIO devices which would have worked otherwise,
> so this change should be justified.
The I2C_CLASS_STANDARD option sounds sensible - though perhaps the comment
would be quicker ;)
>
> @Jean: Do you have anything to add?
>
> --
> 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:[~2015-01-01 12:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 21:19 [PATCH 0/3] Enable AK8963 conneted via INV6500 Srinivas Pandruvada
2014-12-15 21:19 ` [PATCH 1/3] iio: imu: inv_mpu6050: ACPI enumeration Srinivas Pandruvada
2014-12-26 12:39 ` Jonathan Cameron
2014-12-15 21:19 ` [PATCH 2/3] iio: imu: inv_mpu6050: Added adapter class Srinivas Pandruvada
2014-12-26 12:37 ` Jonathan Cameron
2014-12-31 10:25 ` Wolfram Sang
2015-01-01 12:27 ` Jonathan Cameron [this message]
2015-01-04 19:20 ` Jean Delvare
2014-12-15 21:19 ` [PATCH 3/3] iio: ak8975: Added autodetect feature for ACPI Srinivas Pandruvada
2014-12-18 16:28 ` Lars-Peter Clausen
2014-12-18 16:52 ` Srinivas Pandruvada
2014-12-18 17:05 ` Lars-Peter Clausen
2014-12-18 17:30 ` Srinivas Pandruvada
2014-12-18 17:54 ` Lars-Peter Clausen
2014-12-18 18:00 ` Srinivas Pandruvada
2014-12-26 11:53 ` Jonathan Cameron
2015-01-08 16:40 ` Wolfram Sang
2015-01-08 16:54 ` 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=54A53D22.4060903@kernel.org \
--to=jic23@kernel.org \
--cc=jdelvare@suse.de \
--cc=linux-iio@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=wsa@the-dreams.de \
/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).