[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190809144525.GE864@valkosipuli.retiisi.org.uk>
Date: Fri, 9 Aug 2019 17:45:25 +0300
From: Sakari Ailus <sakari.ailus@....fi>
To: Luis Oliveira <Luis.Oliveira@...opsys.com>
Cc: mchehab@...nel.org, davem@...emloft.net,
gregkh@...uxfoundation.org, Jonathan.Cameron@...wei.com,
robh@...nel.org, nicolas.ferre@...rochip.com,
paulmck@...ux.ibm.com, mark.rutland@....com, kishon@...com,
devicetree@...r.kernel.org, linux-media@...r.kernel.org,
linux-kernel@...r.kernel.org, Joao.Pinto@...opsys.com
Subject: Re: [v4 4/6] dt-bindings: phy: Document the Synopsys MIPI DPHY Rx
bindings
On Fri, Aug 09, 2019 at 05:42:52PM +0300, Sakari Ailus wrote:
> Hi Luis,
>
> On Tue, Jun 11, 2019 at 09:20:53PM +0200, Luis Oliveira wrote:
> > Add device-tree bindings documentation for SNPS DesignWare MIPI D-PHY in
> > RX mode.
> >
> > Signed-off-by: Luis Oliveira <luis.oliveira@...opsys.com>
> > ---
> > Changelog
> > v3-v4
> > - @Laurent I know I told you I could remove the snps,dphy-frequency on V3 but
> > it is really useful for me here. I removed all other the proprietary
> > properties except this one. Do you still think it must be removed?
>
> Yes. DT is the wrong place for runtime configuration. You get that
> information using the V4L2_CID_LINK_FREQ control on the upstream
> sub-device.
And the PHY driver itself gets that in its configuration (struct
phy_configure_opts_mipi_dphy through the configure op).
--
Sakari Ailus
Powered by blists - more mailing lists