Hi Laurent,
21. 8. 13. 오후 9:16에 Laurent Pinchart 이(가) 쓴 글:
> Hi Inki,
>
> On Fri, Aug 13, 2021 at 03:50:56PM +0900, Inki Dae wrote:
>> 21. 7. 26. 오전 2:25에 Sam Ravnborg 이(가) 쓴 글:
>>> On Sun, Jul 04, 2021 at 02:32:19PM +0530, Jagan Teki wrote:
Exynos DSI driver is actually a Samsung MIPI DSIM
Hi Inki,
On Fri, Aug 13, 2021 at 03:50:56PM +0900, Inki Dae wrote:
> 21. 7. 26. 오전 2:25에 Sam Ravnborg 이(가) 쓴 글:
> > 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.
> >>
> >> R
Hi,
21. 7. 26. 오전 2:25에 Sam Ravnborg 이(가) 쓴 글:
> 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 lik
On Sun, Jul 25, 2021 at 10:55 PM Sam Ravnborg 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
> > c
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 swi
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