On Fri, Apr 19, 2024 at 10:22:19AM +0200, Linus Walleij wrote:
> On Thu, Apr 18, 2024 at 1:36 AM Dmitry Baryshkov
> wrote:
>
> > I have LVDS working on apq8064, but it requires fixes in the MMCC
> > driver, in the MDP4 driver and in DTS. I need to clean up them first
> > before even attempting to
On Thu, Apr 18, 2024 at 1:36 AM Dmitry Baryshkov
wrote:
> I have LVDS working on apq8064, but it requires fixes in the MMCC
> driver, in the MDP4 driver and in DTS. I need to clean up them first
> before even attempting to send them out. Also a PWM/LPG driver would
> help as otherwise the power s
On Wed, Apr 17, 2024 at 01:39:16PM +0200, Linus Walleij wrote:
> Hi Herman,
>
> thanks for your patch!
>
> Do you actually have this working on real hardware? I never
> submitted this patch because I could not get the hardware
> working.
>
> I was hoping for smarter people (Dmitry Baryshkov...)
Hi Herman,
thanks for your patch!
Do you actually have this working on real hardware? I never
submitted this patch because I could not get the hardware
working.
I was hoping for smarter people (Dmitry Baryshkov...) to step
in and help out to actually make it work before submitting
patches.
Your
On Wed, Apr 17, 2024 at 11:12:09AM +0200, Herman van Hazendonk wrote:
> This happens in the MSM DRM driver when it is used
> without any subcomponents, which is a special corner
> case.
>
> If the MDP4 is used with nothing but the LVDS display,
> we get this problem that no components are found si
On Wed, Apr 17, 2024 at 11:12:09AM +0200, Herman van Hazendonk wrote:
> This happens in the MSM DRM driver when it is used
> without any subcomponents, which is a special corner
> case.
>
> If the MDP4 is used with nothing but the LVDS display,
> we get this problem that no components are found si
