[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181219154040.k424xkzz3xap6462@flea>
Date: Wed, 19 Dec 2018 16:40:40 +0100
From: Maxime Ripard <maxime.ripard@...tlin.com>
To: sakari.ailus@....fi
Cc: Kishon Vijay Abraham I <kishon@...com>,
Boris Brezillon <boris.brezillon@...tlin.com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-media@...r.kernel.org,
Archit Taneja <architt@...eaurora.org>,
Andrzej Hajda <a.hajda@...sung.com>,
Chen-Yu Tsai <wens@...e.org>, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org,
linux-arm-kernel@...ts.infradead.org,
Krzysztof Witos <kwitos@...ence.com>,
Rafal Ciepiela <rafalc@...ence.com>
Subject: Re: [PATCH v3 03/10] phy: Add MIPI D-PHY configuration options
On Mon, Dec 17, 2018 at 10:20:39PM +0200, sakari.ailus@....fi wrote:
> Hi Maxime,
>
> On Mon, Dec 17, 2018 at 04:49:21PM +0100, Maxime Ripard wrote:
> > Hi Sakari,
> >
> > Thanks for your feedback.
> >
> > On Thu, Dec 13, 2018 at 10:49:28PM +0200, sakari.ailus@....fi wrote:
> > > > + /**
> > > > + * @lanes:
> > > > + *
> > > > + * Number of active data lanes used for the transmissions.
> > >
> > > Could you add that these are the first "lanes" number of lanes from what
> > > are available?
> >
> > I'm not quite sure I understood this part though, what did you mean?
>
> A number of lanes are routed between the two devices on hardware, and this
> field is specifying how many of them are in use. In order for the bus to
> function, both ends need to be in agreement on which of these lanes are
> actually being used. The current practice I've seen without exceptions is
> that these are the first n lanes.
Ah, right, I get it now, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists