linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kenneth Heitke <kheitke@codeaurora.org>
To: "Daniel Glöckner" <dg@emlix.com>
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: Fri, 23 Jul 2010 14:50:14 -0600	[thread overview]
Message-ID: <4C4A0086.3040009@codeaurora.org> (raw)
In-Reply-To: <4C496C58.1080806@emlix.com>

Daniel Glöckner wrote:
> On 07/21/2010 07:52 PM, Kenneth Heitke wrote:
>> 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
>> instead.  This restricts the client drivers from using the SMBus
>> communication APIs unless they update the address field (addr) of the
>> i2c_client structure prior to every SMBus function call.
> 
> Is it just me who is uncomfortable with this?
> 
> If I am not mistaken, you still have to update the i2c_client structure
> when using the SMBus API.

Yes, you are correct if the SMBus API is being used.

Each SSBI transaction consists of an address and a data word.  I need to 
get the address information somehow and I didn't want to have to fetch 
this information from the data buffer passed in for the clients.

> 
> And how do you intend to bind a driver to an SSBI device if there is not a
> single address to bind to?

There is only one device per controller therefore the binding is done 
using the bus number.  If I have 3 devices, then I have 3 independent buses.

> 
> The Qualcomm SSBI patent mentiones the possibility of adding logic to chips
> to be accessible over both SSBI and the three wire SBI interface. The SBI
> interface on the other hand is even closer to I2C and requires the use of
> a slave ID byte. If you didn't abuse the address field, you could write
> drivers that work on both interfaces.

The driver doesn't support the three wire SBI interface.  That interface 
   has been replaced with the single wire interface and won't be support 
under Linux.

> 
> Why not use one of the special addresses mentioned in the I2C specification
> for SSBI? 0x02 might be appropriate.
> 

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  parent reply	other threads:[~2010-07-23 20:50 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
     [not found]   ` <4C496C58.1080806-QdrG9jWwCLEAvxtiuMwx3w@public.gmane.org>
2010-07-23 18:32     ` Kenneth Heitke
2010-07-23 20:48     ` Kenneth Heitke
2010-07-23 20:50   ` Kenneth Heitke [this message]
     [not found] ` <1279734768-8436-1-git-send-email-kheitke-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2010-07-28 13:26   ` Pavel Machek
     [not found]     ` <20100728132607.GA16737-+ZI9xUNit7I@public.gmane.org>
2010-08-10  2:26       ` Kenneth Heitke
     [not found]         ` <4C60B8BB.2050209-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
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=4C4A0086.3040009@codeaurora.org \
    --to=kheitke@codeaurora.org \
    --cc=ben-linux@fluff.org \
    --cc=crane.cai@amd.com \
    --cc=dg@emlix.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=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).