Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752439AbbHSPjk (ORCPT ); Wed, 19 Aug 2015 11:39:40 -0400 Received: from mga14.intel.com ([192.55.52.115]:20081 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751467AbbHSPjh (ORCPT ); Wed, 19 Aug 2015 11:39:37 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,710,1432623600"; d="scan'208";a="786864203" From: Jani Nikula To: Thierry Reding , Lucas Stach Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, a.hajda@samsung.com Subject: Re: [RFC 0/2] drm/dsi: DSI for devices with different control bus In-Reply-To: <20150819150207.GJ15607@ulmo.nvidia.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <1435641851-27295-1-git-send-email-architt@codeaurora.org> <55D40F2A.6000208@codeaurora.org> <20150819131300.GC15607@ulmo.nvidia.com> <1439993828.31432.28.camel@pengutronix.de> <20150819143452.GH15607@ulmo.nvidia.com> <1439995944.31432.34.camel@pengutronix.de> <20150819150207.GJ15607@ulmo.nvidia.com> User-Agent: Notmuch/0.20.2+57~gff3a03d (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Wed, 19 Aug 2015 18:39:30 +0300 Message-ID: <87d1yj9tjh.fsf@intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1516 Lines: 34 On Wed, 19 Aug 2015, Thierry Reding wrote: > On Wed, Aug 19, 2015 at 04:52:24PM +0200, Lucas Stach wrote: >> Am Mittwoch, den 19.08.2015, 16:34 +0200 schrieb Thierry Reding: >> > I think that's a flawed interpretation of what's going on here. The >> > device in fact has two interfaces: one is I2C, the other is DSI. In my >> > opinion that's reason enough to represent it as two logical devices. >> > >> Does it really have 2 control interfaces that are used at the same time? >> Or is the DSI connection a passive data bus if the register control >> happens through i2c? > > The interfaces may not be used at the same time, and the DSI interface > may even be crippled, but the device is still addressable from the DSI > host controller, if for nothing else than for routing the video stream. As a drive-by comment, the Toshiba TC358764XBG/65XBG chip can be configured via both DSI and I2C. The I2C interface requires DSI clock on the DSI interface to operate. You may not use the interfaces simultaneously, but provided you protect against races in register access, both interfaces can be operational at the same time. Sorry I couldn't find a public spec of the chip to share. HTH, Jani. -- Jani Nikula, Intel Open Source Technology Center -- 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/