Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755748Ab2K3CNF (ORCPT ); Thu, 29 Nov 2012 21:13:05 -0500 Received: from mail-ob0-f174.google.com ([209.85.214.174]:62737 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755042Ab2K3CNC (ORCPT ); Thu, 29 Nov 2012 21:13:02 -0500 MIME-Version: 1.0 In-Reply-To: <20121129163448.GA3761@sirena.org.uk> References: <1354165536-18529-1-git-send-email-ch.naveen@samsung.com> <1354165536-18529-3-git-send-email-ch.naveen@samsung.com> <20121129163448.GA3761@sirena.org.uk> Date: Thu, 29 Nov 2012 18:13:01 -0800 X-Google-Sender-Auth: VprkVF4JFB4AgtZnXBnSQO1KTLY Message-ID: Subject: Re: [PATCH 2/2] i2c-s3c2410: Add bus arbitration implementation From: Simon Glass To: Mark Brown Cc: Naveen Krishna Chatradhi , linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-i2c@vger.kernel.org, grundler@chromium.org, naveen@chromium.org, w.sang@pengutronix.de, linux-kernel@vger.kernel.org, Olof Johansson Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 908 Lines: 23 +Olof On Thu, Nov 29, 2012 at 8:34 AM, Mark Brown wrote: > On Thu, Nov 29, 2012 at 10:35:35AM +0530, Naveen Krishna Chatradhi wrote: > >> The arbitrator is a general purpose function which uses two GPIOs to >> communicate with another device to claim/release a bus. We use it to >> arbitrate an i2c port between the AP and the EC. > > Should this not be layerd on top of the I2C controller rather than part > of the controller driver? It doesn't seem terribly controller specific. It was originally done separately but I think it was felt that this was overly complex. Olof can you please comment on this? Regards, Simon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/