All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: I2C class bitmask
Date: Thu, 21 May 2015 14:07:31 -0700	[thread overview]
Message-ID: <555E4913.9070805@freescale.com> (raw)

Lee,

Is there any convention regarding I2C class bitmask? I see only three are
defined for 3.12.19 and four for 4.0

I2C_CLASS_HWMON, I2C_CLASS_DDC, I2C_CLASS_SPD, I2C_CLASS_DEPRECATED

I am working on a clock chip driver (SI5338) and trying to detect them (multiple
chips in i2c mux). It would be a lot easier to have its own class, like
I2C_CLASS_CLOCK. It is trivial to add a line to i2c.h file. Just checking if
this is a bad idea.

York

WARNING: multiple messages have this Message-ID (diff)
From: York Sun <yorksun@freescale.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-i2c@vger.kernel.org>
Subject: I2C class bitmask
Date: Thu, 21 May 2015 14:07:31 -0700	[thread overview]
Message-ID: <555E4913.9070805@freescale.com> (raw)

Lee,

Is there any convention regarding I2C class bitmask? I see only three are
defined for 3.12.19 and four for 4.0

I2C_CLASS_HWMON, I2C_CLASS_DDC, I2C_CLASS_SPD, I2C_CLASS_DEPRECATED

I am working on a clock chip driver (SI5338) and trying to detect them (multiple
chips in i2c mux). It would be a lot easier to have its own class, like
I2C_CLASS_CLOCK. It is trivial to add a line to i2c.h file. Just checking if
this is a bad idea.

York

             reply	other threads:[~2015-05-21 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 21:07 York Sun [this message]
2015-05-21 21:07 ` I2C class bitmask York Sun
2015-05-23 16:27 ` Guenter Roeck
     [not found]   ` <20150523162737.GA4981-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2015-05-23 16:50     ` York Sun
2015-05-23 16:50       ` York Sun

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=555E4913.9070805@freescale.com \
    --to=yorksun@freescale.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.