[RFC PATCH 06/17] drm/exynos: dsi: Handle exynos specifics via driver_data

[Jagan Teki]

On Sun, Jul 25, 2021 at 10:55 PM Sam Ravnborg <sam at ravnborg.org> wrote:
>
> On Sun, Jul 04, 2021 at 02:32:19PM +0530, Jagan Teki wrote:
> > Exynos DSI driver is actually a Samsung MIPI DSIM bridge
> > IP which is also used in i.MX8MM platforms.
> >
> > Right now the existing driver has some exynos drm specific
> > code bases like te_irq, crtc and component_ops.
> >
> > In order to switch this driver into a common bridge driver
> > We can see 2 options to handle the exynos specific code.
> >
> > A. Drop the component_ops, and rework other specifics.
> >    This may lead to more foundation work as it requires
> >    more changes in exynos drm drivers stack.
> >
> > B. Handle the exynos specifics via driver data, and make
> >    the common bridge work in different platforms and plan
> >    for option A in future.
> >
> > So, this patch is trying to add option B) changes to handle
> > exynos specifics via driver_data.
>
> We really should find someone that has the time, energy, knowledge and
> hardware that can include device_link support once anf for all for
> bridges.
> Then we would avoid hacks like this.
>
> I see no other options at the moment, but look forward for a better
> solution.

The real key problem here is hardware, unfortunately I'm unable to
find any proper exynos DSI hardware for myself to proceed atleast.

Thanks,
Jagan.