From: Kenneth Heitke <kheitke@codeaurora.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: khali@linux-fr.org, ben-linux@fluff.org,
linux-arm-msm@vger.kernel.org, sdharia@codeaurora.org,
Crane Cai <crane.cai@amd.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Linus Walleij <linus.walleij@stericsson.com>,
Ralf Baechle <ralf@linux-mips.org>,
srinidhi kasagar <srinidhi.kasagar@stericsson.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: Single-wire Serial Bus Interface for Qualcomm MSM chipsets
Date: Mon, 09 Aug 2010 20:26:03 -0600 [thread overview]
Message-ID: <4C60B8BB.2050209@codeaurora.org> (raw)
In-Reply-To: <20100728132607.GA16737@ucw.cz>
Pavel Machek wrote:
> Hi!
>
>> This bus driver supports the Single-wire Serial Bus Interface (SSBI)
>> controller in the Qualcomm MSM SOCs. SSBI is not an I2C but is
>> functionally related enough such that it is able to leaverage the I2C
>> framework.
>>
>> Unlike I2C, SSBI is a point-to-point connection, and therefore there is no
>> need to specify a slave device address. The SSBI implementation
>> overrides the slave device address to be a device register address
>
> Then perhaps it should not go to drivers/i2c?
>
I'd like to make use of the i2c framework rather than implement
something else. Are you suggesting that the driver reside elsewhere
(i.e. mach-msm) or that the driver not use the i2c framework?
thanks.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-08-10 2:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 17:52 [PATCH] i2c: Single-wire Serial Bus Interface for Qualcomm MSM chipsets Kenneth Heitke
2010-07-23 10:18 ` Daniel Glöckner
2010-07-23 18:32 ` Kenneth Heitke
2010-07-23 20:48 ` Kenneth Heitke
2010-07-23 20:50 ` Kenneth Heitke
2010-07-28 13:26 ` Pavel Machek
2010-08-10 2:26 ` Kenneth Heitke [this message]
2010-08-10 21:41 ` Pavel Machek
2010-09-24 22:48 ` Kenneth Heitke
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=4C60B8BB.2050209@codeaurora.org \
--to=kheitke@codeaurora.org \
--cc=ben-linux@fluff.org \
--cc=crane.cai@amd.com \
--cc=khali@linux-fr.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=ralf@linux-mips.org \
--cc=sameo@linux.intel.com \
--cc=sdharia@codeaurora.org \
--cc=srinidhi.kasagar@stericsson.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).