Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

* Tomi Valkeinen [170512 00:32]: > On 11/05/17 17:16, Tony Lindgren wrote: > > >> pinctrl-single doesn't allow to freely set the bits, but requires the > >> pins to have similar bit structure (function-mask). In CONTROL_DSIPHY, > >> DSI1 and DSI2 have different bit

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

On 11/05/17 17:16, Tony Lindgren wrote: >> pinctrl-single doesn't allow to freely set the bits, but requires the >> pins to have similar bit structure (function-mask). In CONTROL_DSIPHY, >> DSI1 and DSI2 have different bit structures. > > OK if the register mixes different types of controllers

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

* Tomi Valkeinen [170511 01:37]: > On 10/05/17 21:29, Tony Lindgren wrote: > > * Tomi Valkeinen [170510 10:44]: > >> > >> > >> On 10/05/17 19:46, Tony Lindgren wrote: > >>> * Tomi Valkeinen [170510 00:26]: > On 09/05/17

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

On 10/05/17 21:29, Tony Lindgren wrote: > * Tomi Valkeinen [170510 10:44]: >> >> >> On 10/05/17 19:46, Tony Lindgren wrote: >>> * Tomi Valkeinen [170510 00:26]: On 09/05/17 18:05, Sebastian Reichel wrote: > patch 10: > I think dsi

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

* Tomi Valkeinen [170510 10:44]: > > > On 10/05/17 19:46, Tony Lindgren wrote: > > * Tomi Valkeinen [170510 00:26]: > >> On 09/05/17 18:05, Sebastian Reichel wrote: > >> > >>> patch 10: > >>> I think dsi pin muxing should be done by providing

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

* Tomi Valkeinen [170510 00:26]: > On 09/05/17 18:05, Sebastian Reichel wrote: > > > patch 10: > > I think dsi pin muxing should be done by providing pinmux > > info via DT. > > Unfortunately there's no pinmux driver for the kind of register we have > for DSI. At least

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

On 10/05/17 19:46, Tony Lindgren wrote: > * Tomi Valkeinen [170510 00:26]: >> On 09/05/17 18:05, Sebastian Reichel wrote: >> >>> patch 10: >>> I think dsi pin muxing should be done by providing pinmux >>> info via DT. >> >> Unfortunately there's no pinmux driver for the

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

On 09/05/17 18:05, Sebastian Reichel wrote: > patch 10: > I think dsi pin muxing should be done by providing pinmux > info via DT. Unfortunately there's no pinmux driver for the kind of register we have for DSI. At least this was the case not that long ago. Tomi signature.asc Description:

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

On 10/05/17 01:18, Laurent Pinchart wrote: > Hi Tomi, > > On Tuesday 09 May 2017 15:10:40 Tomi Valkeinen wrote: >> On 08/05/17 14:32, Laurent Pinchart wrote: >>> Hello, >>> >>> This patch series is a second, extended version of the code previously >>> posted as "[PATCH/RFC 0/7] Remove the

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

* Tomi Valkeinen [170509 04:56]: > On 08/05/17 20:07, Tony Lindgren wrote: > > * Laurent Pinchart [170508 04:36]: > >> The next step is to remove the omapdss platform driver (for the virtual > >> omapdss platform device, also known as

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

Hi, On Tue, May 09, 2017 at 03:10:40PM +0300, Tomi Valkeinen wrote: > On 08/05/17 14:32, Laurent Pinchart wrote: > > Hello, > > > > This patch series is a second, extended version of the code previously > > posted > > as "[PATCH/RFC 0/7] Remove the omapdrm device from platform code". > > As

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

Hi Tomi, On Tuesday 09 May 2017 15:10:40 Tomi Valkeinen wrote: > On 08/05/17 14:32, Laurent Pinchart wrote: > > Hello, > > > > This patch series is a second, extended version of the code previously > > posted as "[PATCH/RFC 0/7] Remove the omapdrm device from platform code". > As this is a long

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

On 08/05/17 14:32, Laurent Pinchart wrote: > Hello, > > This patch series is a second, extended version of the code previously posted > as "[PATCH/RFC 0/7] Remove the omapdrm device from platform code". As this is a long series, I'd like to pick a bunch of patches from this series already: 1-5,

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

On 08/05/17 20:07, Tony Lindgren wrote: > * Laurent Pinchart [170508 04:36]: >> The next step is to remove the omapdss platform driver (for the virtual >> omapdss platform device, also known as core code, not to be confused with the >> omapdss_dss driver for the

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

* Laurent Pinchart [170508 04:36]: > The next step is to remove the omapdss platform driver (for the virtual > omapdss platform device, also known as core code, not to be confused with the > omapdss_dss driver for the DSS hardware device). Patches 21/28 to 23/28

[PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

Hello, This patch series is a second, extended version of the code previously posted as "[PATCH/RFC 0/7] Remove the omapdrm device from platform code". The omapdss/omapdrm initialization code is quite a mess. The physical devices are instantiated from DT, but two virtual devices named omapdrm