From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wolverine02.qualcomm.com ([199.106.114.251]:23538 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753592Ab0HJC0E (ORCPT ); Mon, 9 Aug 2010 22:26:04 -0400 Message-ID: <4C60B8BB.2050209@codeaurora.org> Date: Mon, 09 Aug 2010 20:26:03 -0600 From: Kenneth Heitke MIME-Version: 1.0 Subject: Re: [PATCH] i2c: Single-wire Serial Bus Interface for Qualcomm MSM chipsets References: <1279734768-8436-1-git-send-email-kheitke@codeaurora.org> <20100728132607.GA16737@ucw.cz> In-Reply-To: <20100728132607.GA16737@ucw.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: Pavel Machek Cc: khali@linux-fr.org, ben-linux@fluff.org, linux-arm-msm@vger.kernel.org, sdharia@codeaurora.org, Crane Cai , Samuel Ortiz , Linus Walleij , Ralf Baechle , srinidhi kasagar , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org 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.