[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190713202207.v7t2t3r24amctxvf@mara.localdomain>
Date: Sat, 13 Jul 2019 23:22:08 +0300
From: Sakari Ailus <sakari.ailus@...ux.intel.com>
To: Maxime Ripard <maxime.ripard@...tlin.com>
Cc: Zeng Tao <prime.zeng@...ilicon.com>, kishon@...com,
Chen-Yu Tsai <wens@...e.org>,
Paul Kocialkowski <paul.kocialkowski@...tlin.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] phy: Change the configuration interface param to void*
to make it more general
On Fri, Jul 12, 2019 at 09:21:45AM +0200, Maxime Ripard wrote:
> On Fri, Jul 12, 2019 at 05:26:04PM +0800, Zeng Tao wrote:
> > The phy framework now allows runtime configurations, but only limited
> > to mipi now, and it's not reasonable to introduce user specified
> > configurations into the union phy_configure_opts structure. An simple
> > way is to replace with a void *.
> >
> > We have already got some phy drivers which introduce private phy API
> > for runtime configurations, and with this patch, they can switch to
> > the phy_configure as a replace.
> >
> > Signed-off-by: Zeng Tao <prime.zeng@...ilicon.com>
>
> I still don't believe this is the right approach, for the reasons
> exposed in my first review of that patch.
I agree.
The very reason for having PHY type specific structs is to allow configuring
the PHY independently of the PHY device. This patch breaks that.
--
Regards,
Sakari Ailus
sakari.ailus@...ux.intel.com
Powered by blists - more mailing lists