Add bindings for visionox rm69299 panel.
Signed-off-by: Harigovindan P
---
Changes in v2:
- Removed unwanted properties from description.
- Creating source files without execute permissions(Rob Herring).
Changes in v3:
- Changing txt file into yaml
Changes in v4:
- Updating licen
Adding support for visionox rm69299 panel driver and adding bindings for the
same panel.
Harigovindan P (2):
dt-bindings: display: add visionox rm69299 panel variant
drm/panel: add support for rm69299 visionox panel driver
.../display/panel/visionox,rm69299.yaml | 73 +
drivers/g
rob,
issue got resolved. the problem was end node of the panel had the label.
- panel2: eppendorf {
+ lvds-out {
https://github.com/vinaysimhabn/kernel-msm/commit/a7bf9ccd0b61cb355fe7fa768e65b6f04cfa686f
thanks.
On Thu, Mar 19, 2020 at 10:46 PM Vinay Simha B N wrote:
>
> On Thu, Mar 19, 2020
The GMU has very few memory allocations and uses a flat memory space so
there is no good reason to go out of our way to bypass the DMA APIs which
were basically designed for this exact scenario.
v7: Check return value of dma_set_mask_and_coherent
v4: Use dma_alloc_wc()
v3: Set the dma mask correct
Convert display/msm/gmu.txt to display/msm/gmu.yaml and remove the old
text bindings. The 'sram' text from the old binding never applied to
the GMU so it was not converted but all the other properties were correct.
Acked-by: Sam Ravnborg
Reviewed-by: Rob Herring
Signed-off-by: Jordan Crouse
--
When CONFIG_INIT_ON_ALLOC_DEFAULT_ON the GMU memory allocator runs afoul of
cache coherency issues because it is mapped as write-combine without clearing
the cache after it was zeroed.
Rather than duplicate the hacky workaround we use in the GEM allocator for the
same reason it turns out that we
On Mon, Mar 16, 2020 at 09:46:46AM +0530, Harigovindan P wrote:
> Add bindings for visionox rm69299 panel.
>
> Signed-off-by: Harigovindan P
> ---
>
> Changes in v2:
> - Removed unwanted properties from description.
> - Creating source files without execute permissions(Rob Herring).
Quoting Vara Reddy (2020-03-04 16:10:27)
> From: Chandan Uddaraju
>
> Add the needed DP PLL specific files to support
> display port interface on msm targets.
>
> The DP driver calls the DP PLL driver registration.
> The DP driver sets the link and pixel clock sources.
>
> Changes in v2:
> -- U
On Thu 19 Mar 11:19 PDT 2020, Rob Clark wrote:
> On Wed, Mar 18, 2020 at 9:39 PM Bjorn Andersson
> wrote:
> >
> > With the introduction of '3ef2f119bd3e ("drm/msm: Use
> > drm_attach_bridge() to attach a bridge to an encoder")' the HDMI bridge
> > is attached both in msm_hdmi_bridge_init() and la
On Wed 11 Mar 20:51 PDT 2020, Ilia Mirkin wrote:
> Each of hdmi and edp are already attached in msm_*_bridge_init. A second
> attachment returns -EBUSY, failing the driver load.
>
> Tested with HDMI on IFC6410 (APQ8064 / MDP4), but eDP case should be
> analogous.
>
> Fixes: 3ef2f119bd3ed (drm/ms
On Wed, Mar 18, 2020 at 9:39 PM Bjorn Andersson
wrote:
>
> With the introduction of '3ef2f119bd3e ("drm/msm: Use
> drm_attach_bridge() to attach a bridge to an encoder")' the HDMI bridge
> is attached both in msm_hdmi_bridge_init() and later in
> msm_hdmi_modeset_init().
>
> The second attempt fai
Subject could be "sc7180: update DPU assigned clocks"
Quoting Krishna Manikandan (2020-03-16 04:02:42)
> Add DISP_CC_MDSS_ROT_CLK and DISP_CC_MDSS_AHB_CLK
> in the assigned clocks list for sc7180 target.
Why?
>
> Signed-off-by: Krishna Manikandan
Does this need a Fixes: tag?
> ---
> arch/ar
On Thu, Mar 19, 2020 at 10:36 PM Rob Herring wrote:
>
> On Thu, Mar 19, 2020 at 9:56 AM Vinay Simha B N wrote:
> >
> > On Thu, Mar 19, 2020 at 9:16 PM Rob Herring wrote:
> > >
> > > On Thu, Mar 19, 2020 at 1:31 AM Vinay Simha B N
> > > wrote:
> > > >
> > > > hi,
> > > >
> > > > I am getting th
On Thu, Mar 19, 2020 at 9:56 AM Vinay Simha B N wrote:
>
> On Thu, Mar 19, 2020 at 9:16 PM Rob Herring wrote:
> >
> > On Thu, Mar 19, 2020 at 1:31 AM Vinay Simha B N wrote:
> > >
> > > hi,
> > >
> > > I am getting the endpoint' is not bidirectional(d2l_in, dsi0_out)
> > > warning in compilation,
On Thu, Mar 19, 2020 at 9:16 PM Rob Herring wrote:
>
> On Thu, Mar 19, 2020 at 1:31 AM Vinay Simha B N wrote:
> >
> > hi,
> >
> > I am getting the endpoint' is not bidirectional(d2l_in, dsi0_out)
> > warning in compilation, built boot image works on qcom apq8016-ifc6309
> > board with the dsi->br
On Thu, Mar 19, 2020 at 1:31 AM Vinay Simha B N wrote:
>
> hi,
>
> I am getting the endpoint' is not bidirectional(d2l_in, dsi0_out)
> warning in compilation, built boot image works on qcom apq8016-ifc6309
> board with the dsi->bridge->lvds panel.
> Because of this warning i cannot create a .yaml
hi,
I am getting the endpoint' is not bidirectional(d2l_in, dsi0_out)
warning in compilation, built boot image works on qcom apq8016-ifc6309
board with the dsi->bridge->lvds panel.
Because of this warning i cannot create a .yaml documentation examples.
Please suggest.
tc_bridge: bridge@f {
status
17 matches
Mail list logo
