Am Mittwoch, den 18.05.2016, 11:12 +0200 schrieb Lothar WaÃmann:
> Hi,
>
> On Fri, 13 May 2016 13:04:12 +0200 Philipp Zabel wrote:
> > Hi Lothar,
> >
> > Am Freitag, den 13.05.2016, 12:33 +0200 schrieb Lothar WaÃmann:
> > > Hi,
> > >
> > > the commit 503fe87bd0a8 ("gpu: ipu-v3: Fix
Hi,
On Fri, 13 May 2016 13:04:12 +0200 Philipp Zabel wrote:
> Hi Lothar,
>
> Am Freitag, den 13.05.2016, 12:33 +0200 schrieb Lothar WaÃmann:
> > Hi,
> >
> > the commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module
> > autoloading")
> > indeed fixes the autoloading issue, but
Hi there
On Fri, 2016-05-13 at 12:33 +0200, Lothar WaÃmann wrote:
> Hi,
>
> the commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module
> autoloading")
> indeed fixes the autoloading issue, but completely breaks the driver
> in
> non-modular mode (at least with the parallel-display driver
Hi Lothar,
Am Freitag, den 13.05.2016, 12:33 +0200 schrieb Lothar WaÃmann:
> Hi,
>
> the commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading")
> indeed fixes the autoloading issue, but completely breaks the driver in
> non-modular mode (at least with the parallel-display
Hi,
the commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading")
indeed fixes the autoloading issue, but completely breaks the driver in
non-modular mode (at least with the parallel-display driver I didn't
yet check with the imx-ldb driver.
Can anyone confirm that the imx-drm
On Fri, May 13, 2016 at 12:33:36PM +0200, Lothar WaÃmann wrote:
> I'm always very suspicious when seeing code moving of_node's from
> one device to another or assigning of_node's to platform devices that
> weren't instantiated via DT.
It's completely wrong to add an of_node to a device on the
