On Thu, Sep 19, 2013 at 10:48:01PM +0100, Russell King wrote:
The DMA API requires drivers to call the appropriate dma_set_mask()
functions before doing any DMA mapping. Add this required call to
the AMBA PL08x driver.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
Acked-by: Vinod
-off-by: Russell King rmk+ker...@arm.linux.org.uk
Acked-by: Vinod Koul vinod.k...@intel.com
This also brings me question that should we force the driver to use the
dma_set_mask_and_coherent() API or they have below flexiblity too?
~Vinod
---
drivers/dma/edma.c |6 ++
1 files changed
doing any DMA mapping. Add this required call to
the AMBA PL08x driver.
^--- copy and paste error - should of course be PL330
Fixed, thanks.
with fixed changelog...
Acked-by: Vinod Koul vinod.k...@intel.com
~Vinod
--
___
dri
On Tue, Sep 13, 2016 at 11:06:16AM -0700, Bjorn Andersson wrote:
> > I hate to send a ping,
>
> Sorry about that.
>
> > but do you think we can merge this fdma series? It has gone
> > through quite a few review rounds now.
> >
>
> I think the remoteproc part looks good.
yeah I was waiting for
On Wed, Sep 14, 2016 at 06:37:40PM +0530, Vinod Koul wrote:
> On Tue, Sep 13, 2016 at 11:06:16AM -0700, Bjorn Andersson wrote:
> > > I hate to send a ping,
> >
> > Sorry about that.
> >
> > > but do you think we can merge this fdma series? It has gone
>
On Fri, Aug 26, 2016 at 03:56:40PM +0100, Peter Griffin wrote:
> config STM32_DMA
> bool "STMicroelectronics STM32 DMA support"
> depends on ARCH_STM32
> @@ -567,7 +580,6 @@ config ZX_DMA
> help
> Support the DMA engine for ZTE ZX296702 platform devices.
>
> -
replacements.
If all are okay, this should be merged thru PM tree as it depends on macro
addition.
Subhransu S. Prusty (1):
PM: Add helper pm_runtime_last_busy_and_autosuspend()
Vinod Koul (26):
dmaengine: ste_dma: use pm_runtime_last_busy_and_autosuspend helper
extcon: arizona: use
Use the new pm_runtime_last_busy_and_autosuspend helper instead of open
coding the same code
Signed-off-by: Vinod Koul
---
drivers/gpu/drm/i915/intel_pm.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
Use the new pm_runtime_last_busy_and_autosuspend helper instead of open
coding the same code
Signed-off-by: Vinod Koul
---
drivers/gpu/drm/nouveau/nouveau_connector.c |3 +--
drivers/gpu/drm/nouveau/nouveau_drm.c |9 +++--
2 files changed, 4 insertions(+), 8 deletions(-)
diff
Use the new pm_runtime_last_busy_and_autosuspend helper instead of open
coding the same code
Signed-off-by: Vinod Koul
---
drivers/gpu/vga/vga_switcheroo.c |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/vga/vga_switcheroo.c b/drivers/gpu/vga
Use the new pm_runtime_last_busy_and_autosuspend helper instead of open
coding the same code
Signed-off-by: Vinod Koul
---
drivers/gpu/drm/radeon/radeon_connectors.c | 15 +--
drivers/gpu/drm/radeon/radeon_drv.c|5 ++---
drivers/gpu/drm/radeon/radeon_kms.c
On Wed, Sep 24, 2014 at 10:28:07PM +0200, Rafael J. Wysocki wrote:
>
> OK, I guess this is as good as it gets.
>
> What tree would you like it go through?
Since rest of the patches are dependent upon 1st patch which should go thru
your tree, we should merge this thru your tree
Thanks
--
On Wed, Sep 24, 2014 at 03:32:19PM -0500, Felipe Balbi wrote:
> > > > OK, I guess this is as good as it gets.
> > > >
> > > > What tree would you like it go through?
> > >
> > > Do we really need this new helper ? I mean, the very moment when we
> > > decide to implement ->runtime_idle() we will
ansfer-Encoding: quoted-printable
> >
> > On Thu, Sep 25, 2014 at 09:22:01AM -0500, Felipe Balbi wrote:
> > > On Thu, Sep 25, 2014 at 01:27:18PM +0530, Vinod Koul wrote:
> > > > On Wed, Sep 24, 2014 at 03:32:19PM -0500, Felipe Balbi wrote:
> > > > > > >
On Fri, Oct 16, 2015 at 02:31:43PM +0200, Lars-Peter Clausen wrote:
> On 10/16/2015 01:50 PM, Jyri Sarha wrote:
> > After reading the ELCE Audio mini conf minutes [1] I gather that HDMI
> > audio was not discussed after all.
>
> It was discussed, but rather shortly and only in the context of the
On Fri, Oct 16, 2015 at 03:15:25PM +0100, Mark Brown wrote:
> On Fri, Oct 16, 2015 at 03:51:40PM +0200, Arnaud Pouliquen wrote:
>
> > - Does trigger is needed when CPU-DAI is master on bus?
> > Otherwise how to inform HDMI that I2S bus is no more clocked? I'm not
> > sure that mute is sufficient
On Fri, Oct 16, 2015 at 02:37:17PM +0100, Russell King - ARM Linux wrote:
> I've sent one proposal which uses a notifier to inform audio and CEC
> drivers about state changes in the HDMI video side, and had precisely
> zero replies to it - people seemed to prefer discussing stuff rather
> than
On Sun, Oct 18, 2015 at 04:20:48PM +0100, Russell King - ARM Linux wrote:
> On Sun, Oct 18, 2015 at 08:38:34PM +0530, Vinod Koul wrote:
> > On Fri, Oct 16, 2015 at 02:37:17PM +0100, Russell King - ARM Linux wrote:
> > > I've sent one proposal which uses a notifier to in
On Mon, Oct 19, 2015 at 03:20:30PM +0200, Takashi Iwai wrote:
> On Sun, 18 Oct 2015 19:16:42 +0200,
> Russell King - ARM Linux wrote:
> >
> > On Sun, Oct 18, 2015 at 09:43:29PM +0530, Vinod Koul wrote:
> > > Right but can I ask why you didn't try making video as c
On Tue, Oct 20, 2015 at 09:08:00AM +0100, Russell King - ARM Linux wrote:
> > > Currently i915/audio component works as you described. The audio is
> > > optional and HDMI graphics works without audio, while HDMI HD-audio
> > > mandates i915 graphics.
> >
> > Right, but we also add additional
On Wed, Oct 21, 2015 at 12:11:08PM +0300, Jani Nikula wrote:
> On Tue, 20 Oct 2015, Vinod Koul wrote:
> > On Tue, Oct 20, 2015 at 09:08:00AM +0100, Russell King - ARM Linux wrote:
> >> > > Currently i915/audio component works as you described. The audio is
> >&g
On Wed, Oct 21, 2015 at 03:37:47PM +0100, Russell King - ARM Linux wrote:
> On Wed, Oct 21, 2015 at 04:10:31PM +0200, Takashi Iwai wrote:
> > On Wed, 21 Oct 2015 16:03:07 +0200,
> > Russell King - ARM Linux wrote:
> > > It's only the point if you can code it up properly, which from what I
> > >
On Thu, Jun 08, 2017 at 03:25:28PM +0200, Christoph Hellwig wrote:
> DMA_ERROR_CODE is not a public API and will go away. Instead properly
> unwind based on the loop counter.
Acked-By: Vinod Koul <vinod.k...@intel.com>
--
~Vinod
___
dri-d
se/platform.c | 3 +--
> drivers/bcma/main.c | 2 +-
> drivers/dma/qcom/hidma_mgmt.c | 2 +-
This one:
Acked-by: Vinod Koul <vk...@kernel.org>
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 23-11-18, 15:24, Anshuman Khandual wrote:
> --- a/drivers/dma/dmaengine.c
> +++ b/drivers/dma/dmaengine.c
> @@ -386,7 +386,8 @@ EXPORT_SYMBOL(dma_issue_pending_all);
> static bool dma_chan_is_local(struct dma_chan *chan, int cpu)
> {
> int node = dev_to_node(chan->device->dev);
> -
global macro NUMA_NO_NODE. This helps remove NUMA related assumptions like
> 'invalid node' from various places redirecting them to a common definition.
>
> drivers/dma/dmaengine.c | 4 +++-
Acked-by: Vinod Koul
--
~Vinod
On 25-07-19, 18:02, Paul Cercueil wrote:
> The newer and better JZ4780 driver is now used to provide DMA
> functionality on the JZ4740.
Please change subjetc to dmaengine: xxx
After that
Acked-by: Vinod Koul
--
~Vinod
___
dri-devel mailing li
a dedicated DMA.
>
> This patch enables them, following the existing style for the
> scatter/gather type transfers.
I presume you want this to go with drm tree (if not let me know) so:
Acked-by: Vinod Koul
--
~Vinod
___
dri-devel m
On 15-01-20, 18:07, Maxime Ripard wrote:
> On Wed, Jan 15, 2020 at 06:01:37PM +0530, Vinod Koul wrote:
> > On 10-01-20, 16:11, Stefan Mavrodiev wrote:
> > > Currently the cyclic transfers can be used only with normal DMAs. They
> > > can be used by pcm_dmaengin
On 21-01-20, 13:37, Stefan Mavrodiev wrote:
>
> On 1/21/20 10:35 AM, Vinod Koul wrote:
> > On 15-01-20, 18:07, Maxime Ripard wrote:
> > > On Wed, Jan 15, 2020 at 06:01:37PM +0530, Vinod Koul wrote:
> > > > On 10-01-20, 16:11, Stefan Mavrodiev wrote:
> > &
ne.yaml | 7 +-
> .../display/allwinner,sun4i-a10-tcon.yaml | 5 +-
> .../bindings/display/panel/panel-common.yaml | 5 +-
> .../devicetree/bindings/dma/dma-common.yaml | 3 +-
> .../devicetree/bindings/dma/ti/k3-udma.yaml | 18 +-
Acked-By: Vinod Koul
--
~Vinod
+-
> .../bindings/display/renesas,cmm.yaml | 16 ++---
> .../devicetree/bindings/dma/ti/k3-udma.yaml | 8 +--
Acked-By: Vinod Koul
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 16-04-20, 12:30, Geert Uytterhoeven wrote:
> According to https://www.analog.com/, the company name is spelled
> "Analog Devices".
Applied after updating the subsystem name, thanks
--
~Vinod
___
dri-devel mailing list
Lontium Lt9611 is a DSI to HDMI bridge which supports two DSI ports and
I2S port as an input and HDMI port as output
Co-developed-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
Signed-off-by: Vinod Koul
---
drivers/gpu/drm/bridge/Kconfig | 13 +
drivers/gpu/drm/bridge/Makefile |1
Lontium LT9611 is a DSI to HDMI bridge which supports 2 DSI ports
and I2S port as input and one HDMI port as output
Signed-off-by: Vinod Koul
---
.../display/bridge/lontium,lt9611.yaml| 178 ++
1 file changed, 178 insertions(+)
create mode 100644
Documentation
Add prefix for Lontium Semiconductor Corporation
Signed-off-by: Vinod Koul
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b/Documentation/devicetree/bindings/vendor
Hi,
This series adds driver and bindings for Lontium LT9611 bridge chip which
takes MIPI DSI as input and HDMI as output.
This chip can be found in 96boards RB3 platform [1] commonly called DB845c.
[1]: https://www.96boards.org/product/rb3-platform/
Vinod Koul (3):
dt-bindings: vendor
of using symbolic names, instead of
> hex+comment. Considering how partial the comments are, current
> approach is perfectly fine.
>
> On Wed, 13 May 2020 at 11:06, Vinod Koul wrote:
> >
> > Lontium Lt9611 is a DSI to HDMI bridge which supports two DSI ports and
> > I2
ma (via
> '$ref') and all possible properties and/or child nodes are not
> explicitly listed in the schema with the '$ref'.
>
> This is in preparation to add a meta-schema to check for missing
> 'unevaluatedProperties' or 'additionalProperties'. This has been a
> constant source of rev
On 05-10-20, 13:38, Rob Herring wrote:
> In order to add meta-schema checks for additional/unevaluatedProperties
> being present, all schema need to make this explicit. As common/shared
> schema are included by other schemas, they should always allow for
> additionalProperties.
Ack
gs/phy/qcom-usb-ipq4019-phy.yaml| 2 ++
For phy changes:
Acked-By: Vinod Koul
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 28-09-20, 10:59, Rob Herring wrote:
> The default sizes in examples for 'reg' are 1 cell each. Fix the
> incorrect sizes in zynqmp examples:
>
> Documentation/devicetree/bindings/dma/xilinx/xlnx,zynqmp-dpdma.example.dt.yaml:
> example-0: dma-controller@fd4c:reg:0: [0, 4249616384, 0, 4096]
DSI end-points are supposed to be at node 0 and node 1 as per binding.
So fix this and use node 0 and node 1 for dsi.
Reported-by: Dmitry Baryshkov
Fixes: 23278bf54afe ("drm/bridge: Introduce LT9611 DSI to HDMI bridge")
Signed-off-by: Vinod Koul
---
drivers/gpu/drm/bridge/lontium-lt
ip, so let's reuse the lt9611.yaml schema.
Acked-By: Vinod Koul
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 28-08-20, 15:04, Dmitry Baryshkov wrote:
> +#define EDID_BLOCK_SIZE 128
> +#define EDID_NUM_BLOCKS 2
tab or space either one, not both ;)
> +static struct mipi_dsi_device *lt9611uxc_attach_dsi(struct lt9611uxc
> *lt9611uxc,
> + struct
On 28-08-20, 18:01, Dmitry Baryshkov wrote:
> On 28/08/2020 17:18, Vinod Koul wrote:
> > On 28-08-20, 15:04, Dmitry Baryshkov wrote:
> > > +static int lt9611uxc_bridge_attach(struct drm_bridge *bridge,
> > > + enum drm_bridge_attach_flags fla
Hello,
On 08-07-20, 16:05, Vinod Koul wrote:
> Hi,
>
> This series adds driver and bindings for Lontium LT9611 bridge chip which
> takes MIPI DSI as input and HDMI as output.
>
> This chip can be found in 96boards RB3 platform [1] commonly called DB845c.
Any feedback on thi
On 26-07-20, 13:12, Konrad Dybcio wrote:
> These SoCs make use of the 14nm phy, but at different
> addresses than other 14nm units.
>
> Signed-off-by: Konrad Dybcio
> ---
> .../devicetree/bindings/display/msm/dsi.txt| 1 +
> drivers/gpu/drm/msm/dsi/phy/dsi_phy.c | 2 ++
>
HI Laurent,
On 12-08-20, 01:52, Laurent Pinchart wrote:
> Hi Vinod,
>
> On Sun, Aug 02, 2020 at 12:14:09PM +0530, Vinod Koul wrote:
> > On 31-07-20, 23:42, Laurent Pinchart wrote:
> > > On Fri, Jul 31, 2020 at 10:17:44PM +0530, Vinod Koul wrote:
> > > > On 31-
On 31-07-20, 23:42, Laurent Pinchart wrote:
> Hi Vinod,
>
> On Fri, Jul 31, 2020 at 10:17:44PM +0530, Vinod Koul wrote:
> > On 31-07-20, 18:24, Laurent Pinchart wrote:
> > > Hello,
> > >
> > > This small series fixes a Kconfig dependency issue with the
ater on top ? I
> don't expect conflicts (especially in 2/3 and 3/3), so merging the whole
> series in one go would be simpler in my opinion.
Acked-By: Vinod Koul
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 03-08-20, 09:06, Rob Clark wrote:
> On Mon, Aug 3, 2020 at 4:00 AM Vinod Koul wrote:
> >
> > On 26-07-20, 13:12, Konrad Dybcio wrote:
> > > These SoCs make use of the 14nm phy, but at different
> > > addresses than other 14nm units.
> &g
on binding and driver
- Add HDMI audio support
Vinod Koul (4):
dt-bindings: vendor-prefixes: Add Lontium vendor prefix
dt-bindings: display: bridge: Add documentation for LT9611
drm/bridge: Introduce LT9611 DSI to HDMI bridge
drm/msm/dsi: attach external bridge
-by: Vinod Koul
---
drivers/gpu/drm/bridge/Kconfig | 13 +
drivers/gpu/drm/bridge/Makefile |1 +
drivers/gpu/drm/bridge/lontium-lt9611.c | 1174 +++
3 files changed, 1188 insertions(+)
create mode 100644 drivers/gpu/drm/bridge/lontium-lt9611.c
diff --git
Lontium LT9611 is a DSI to HDMI bridge which supports 2 DSI ports
and I2S port as input and one HDMI port as output
Reviewed-by: Rob Herring
Tested-by: John Stultz
Signed-off-by: Vinod Koul
---
.../display/bridge/lontium,lt9611.yaml| 176 ++
1 file changed, 176
Modern bridges do not create the connector and expect the display driver
to do so. Hence, create the drm connector in msm display driver and add
use flag DRM_BRIDGE_ATTACH_NO_CONNECTOR to attach bridges
Tested-by: John Stultz
Signed-off-by: Vinod Koul
---
drivers/gpu/drm/msm/dsi/dsi.c
Add prefix for Lontium Semiconductor Corporation
Acked-by: Rob Herring
Tested-by: John Stultz
Signed-off-by: Vinod Koul
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b
Lontium LT9611 is a DSI to HDMI bridge which supports 2 DSI ports
and I2S port as input and one HDMI port as output
Reviewed-by: Rob Herring
Tested-by: John Stultz
Signed-off-by: Vinod Koul
---
.../display/bridge/lontium,lt9611.yaml| 176 ++
1 file changed, 176
Add prefix for Lontium Semiconductor Corporation
Acked-by: Rob Herring
Tested-by: John Stultz
Signed-off-by: Vinod Koul
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b
-by: Vinod Koul
---
drivers/gpu/drm/bridge/Kconfig | 13 +
drivers/gpu/drm/bridge/Makefile |1 +
drivers/gpu/drm/bridge/lontium-lt9611.c | 1142 +++
3 files changed, 1156 insertions(+)
create mode 100644 drivers/gpu/drm/bridge/lontium-lt9611.c
diff --git
Modern bridges do not create the connector and expect the display driver
to do so. Hence, create the drm connector in msm display driver and add
use flag DRM_BRIDGE_ATTACH_NO_CONNECTOR to attach bridges
Tested-by: John Stultz
Signed-off-by: Vinod Koul
---
drivers/gpu/drm/msm/dsi/dsi.c
the file to lontium-lt9611.c
- Fix comments reported by Laurent on binding and driver
- Add HDMI audio support
Vinod Koul (4):
dt-bindings: vendor-prefixes: Add Lontium vendor prefix
dt-bindings: display: bridge: Add documentation for LT9611
drm/bridge: Introduce LT9611 DSI to HDMI bridge
drm
Lontium Lt9611 is a DSI to HDMI bridge which supports two DSI ports and
I2S port as an input and HDMI port as output
Co-developed-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
Co-developed-by: Srinivas Kandagatla
Signed-off-by: Srinivas Kandagatla
Signed-off-by: Vinod Koul
---
drivers
Lontium LT9611 is a DSI to HDMI bridge which supports 2 DSI ports
and I2S port as input and one HDMI port as output
Reviewed-by: Rob Herring
Signed-off-by: Vinod Koul
---
.../display/bridge/lontium,lt9611.yaml| 176 ++
1 file changed, 176 insertions(+)
create mode
- rebase on v5.8-rc1
Changes in v2:
- Add acks by Rob
- Fix comments reported by Emil and rename the file to lontium-lt9611.c
- Fix comments reported by Laurent on binding and driver
- Add HDMI audio support
Vinod Koul (3):
dt-bindings: vendor-prefixes: Add Lontium vendor prefix
dt
Add prefix for Lontium Semiconductor Corporation
Acked-by: Rob Herring
Signed-off-by: Vinod Koul
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b/Documentation/devicetree
Hello Sam,
On 20-06-20, 20:05, Sam Ravnborg wrote:
> Hi Vinod.
>
> Looks good but some some of small nits.
Great :)
> And a few larger things in the following.
> The larger things is releated to prepare the bridge driver to live in a
> world with chained bridges.
Sure, so that entails adding
Lontium Lt9611 is a DSI to HDMI bridge which supports two DSI ports and
I2S port as an input and HDMI port as output
Co-developed-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
Co-developed-by: Srinivas Kandagatla
Signed-off-by: Srinivas Kandagatla
Signed-off-by: Vinod Koul
---
drivers
comments reported by Emil and rename the file to lontium-lt9611.c
- Fix comments reported by Laurent on binding and driver
- Add HDMI audio support
Vinod Koul (3):
dt-bindings: vendor-prefixes: Add Lontium vendor prefix
dt-bindings: display: bridge: Add documentation for LT9611
drm/bridge
Add prefix for Lontium Semiconductor Corporation
Acked-by: Rob Herring
Signed-off-by: Vinod Koul
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b/Documentation/devicetree
Lontium LT9611 is a DSI to HDMI bridge which supports 2 DSI ports
and I2S port as input and one HDMI port as output
Reviewed-by: Rob Herring
Signed-off-by: Vinod Koul
---
.../display/bridge/lontium,lt9611.yaml| 176 ++
1 file changed, 176 insertions(+)
create mode
Hi Laurent,
Sorry for late reply, I was out last week.
On 28-05-20, 04:48, Laurent Pinchart wrote:
> > +
> > + interrupts:
> > +maxItems: 1
> > +description: interrupt line for the chip
>
> I think you could drop the descriptions for the reg and interrupt
> properties, they don't add
Hi Laurent,
On 28-05-20, 04:52, Laurent Pinchart wrote:
> > +static int lt9611_bridge_attach(struct drm_bridge *bridge,
> > + enum drm_bridge_attach_flags flags)
> > +{
> > + struct lt9611 *lt9611 = bridge_to_lt9611(bridge);
> > + int ret;
> > +
> > +
Hi Sam, Laurent,
On 22-07-20, 16:14, Laurent Pinchart wrote:
> > > +static int lt9611_bridge_attach(struct drm_bridge *bridge,
> > > + enum drm_bridge_attach_flags flags)
> > > +{
> > > + struct lt9611 *lt9611 = bridge_to_lt9611(bridge);
> > > + int ret;
> > > +
> > > + if
Add bridge type as DRM_MODE_CONNECTOR_HDMIA
Signed-off-by: Vinod Koul
---
I found this when testing Dragon-board 410c which uses this bridge
[6.671913] msm 1a0.mdss: [drm:msm_dsi_manager_ext_bridge_init [msm]]
*ERROR* drm_bridge_connector_init failed: -22
[6.678879] msm 1a0
On 23-07-20, 13:39, Sam Ravnborg wrote:
> On Thu, Jul 23, 2020 at 04:11:51PM +0530, Vinod Koul wrote:
> > Hi Sam, Laurent,
> >
> > On 22-07-20, 16:14, Laurent Pinchart wrote:
> > > > > +static int lt9611_bridge_attach(struct drm_bridge *bridge,
> >
Hi Sam,
On 19-07-20, 19:18, Sam Ravnborg wrote:
> Hi Vinod.
>
> Three trivial points below.
> The rest looks good.
>
> With these fixed you can add:
> Reviewed-by: Sam Ravnborg
Thanks, I will send an update with nits fixed
--
~Vinod
___
dri-devel
Lontium LT9611 is a DSI to HDMI bridge which supports 2 DSI ports
and I2S port as input and one HDMI port as output
Reviewed-by: Rob Herring
Tested-by: John Stultz
Signed-off-by: Vinod Koul
---
.../display/bridge/lontium,lt9611.yaml| 176 ++
1 file changed, 176
-by: Vinod Koul
---
drivers/gpu/drm/bridge/Kconfig | 13 +
drivers/gpu/drm/bridge/Makefile |1 +
drivers/gpu/drm/bridge/lontium-lt9611.c | 1229 +++
3 files changed, 1243 insertions(+)
create mode 100644 drivers/gpu/drm/bridge/lontium-lt9611.c
diff --git
- Add HDMI audio support
Vinod Koul (3):
dt-bindings: vendor-prefixes: Add Lontium vendor prefix
dt-bindings: display: bridge: Add documentation for LT9611
drm/bridge: Introduce LT9611 DSI to HDMI bridge
.../display/bridge/lontium,lt9611.yaml| 176 +++
.../devicetree/bindings
Add prefix for Lontium Semiconductor Corporation
Acked-by: Rob Herring
Tested-by: John Stultz
Signed-off-by: Vinod Koul
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b
On 24-07-20, 04:30, Laurent Pinchart wrote:
> Hi Vinod,
>
> Thank you for the patch.
>
> On Thu, Jul 23, 2020 at 04:15:23PM +0530, Vinod Koul wrote:
> > Add bridge type as DRM_MODE_CONNECTOR_HDMIA
> >
> > Signed-off-by: Vinod Koul
>
> Th
the
> > ADV
> > driver has been changed accordingly. However, the 'type' field of the bridge
> > structure was left unset, which makes the helper function always return
> > -EINVAL.
> >
> > Signed-off-by: Laurentiu Palcu
>
> Reviewed-by: Laurent Pinc
On 17-11-20, 07:14, Chun-Kuang Hu wrote:
> mtk_mipi_dsi_phy is currently placed inside mediatek drm driver, but it's
> more suitable to place a phy driver into phy driver folder, so move
> mtk_mipi_dsi_phy driver into phy driver folder.
Acked-By: Vinod Koul
I am thinking this would go
mtk_hdmi_phy_driver is not declared as static, so statify it.
drivers/phy/mediatek/phy-mtk-hdmi.c:204:24: warning: symbol
'mtk_hdmi_phy_driver' was not declared. Should it be static?
Signed-off-by: Vinod Koul
---
drivers/phy/mediatek/phy-mtk-hdmi.c | 2 +-
1 file changed, 1 insertion(+), 1
On 08-12-20, 09:50, Chunfeng Yun wrote:
> On Mon, 2020-12-07 at 15:09 +, Colin King wrote:
> > From: Colin Ian King
> >
> > Currently there is a null pointer check for hdmi_phy that implies it
> > may be null, however a dev_err messages dereferences this potential null
> > pointer. Avoid a
On 23-11-20, 11:46, Robert Foss wrote:
> 4k requires two dsi pipes, so don't report MODE_OK when only a
> single pipe is configured. But rather report MODE_PANEL to
> signal that requirements of the panel are not being met.
Acked-By: Vinod Koul
> Reported-by: Peter Collingbourne
ses are
> fixed.
> ---
> .../devicetree/bindings/display/xlnx/xlnx,zynqmp-dpsub.yaml| 1 -
> Documentation/devicetree/bindings/dma/renesas,rcar-dmac.yaml | 1 -
Acked-By: Vinod Koul
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
ht
On 02-11-20, 07:08, Chun-Kuang Hu wrote:
> + Vinod:
>
> Hi, Chunfeng:
>
> Chunfeng Yun 於 2020年10月30日 週五 下午2:24寫道：
> >
> > On Thu, 2020-10-29 at 23:27 +0800, Chun-Kuang Hu wrote:
> > > mtk_mipi_dsi_phy is currently placed inside mediatek drm driver, but it's
> > > more suitable to place a phy
On 17-11-20, 00:17, Chun-Kuang Hu wrote:
> Hi, Vinod:
>
> Vinod Koul 於 2020年11月16日 週一 下午3:25寫道：
> >
> > On 02-11-20, 07:08, Chun-Kuang Hu wrote:
> > > + Vinod:
> > >
> > > Hi, Chunfeng:
> > >
> > > Chunfeng Yun 於 2020年10月30日 週五
Hi,
Thanks Doug for adding me
On 02-11-20, 08:37, Doug Anderson wrote:
> > On Thu, Oct 29, 2020 at 06:17:34PM -0700, Stephen Boyd wrote:
> > Any chance we can convince you to prepare this bridge driver for use in
> > a chained bridge setup where the connector is created by the display
> >
On 25-12-20, 15:52, Chunfeng Yun wrote:
> Convert phy-mtk-ufs.txt to YAML schema mediatek,ufs-phy.yaml
Applied, thanks
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 25-12-20, 15:52, Chunfeng Yun wrote:
> Convert MIPI DSI PHY binding to YAML schema mediatek,dsi-phy.yaml
Applied, thanks
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 25-12-20, 15:52, Chunfeng Yun wrote:
> Convert HDMI PHY binding to YAML schema mediatek,hdmi-phy.yaml
Applied, thanks
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 25-12-20, 15:52, Chunfeng Yun wrote:
> Convert phy-mtk-tphy.txt to YAML schema mediatek,tphy.yaml
Applied, thanks
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 25-12-20, 15:52, Chunfeng Yun wrote:
> Convert phy-mtk-xsphy.txt to YAML schema mediatek,xsphy.yaml
Applied, thanks
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 12-01-21, 09:38, Zou Wei wrote:
> Fix the following sparse warning:
>
> drivers/phy/mediatek/phy-mtk-mipi-dsi.c:237:24: warning: symbol
> 'mtk_mipi_tx_driver' was not declared. Should it be static?
Applied, thanks
--
~Vinod
___
dri-devel mailing
On 03-02-21, 12:06, Enric Balletbo i Serra wrote:
> From: Boris Brezillon
>
> This patch adds the missing MODULE_DEVICE_TABLE definitions on different
> Mediatek phy drivers which generates correct modalias for automatic loading
> when these drivers are compiled as an external module.
Applied,
--
> drivers/dma/pl330.c | 3 +--
For dmaengine:
Acked-By: Vinod Koul
--
~Vinod
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
; Cc: Scott Branden
> Cc: Pavel Machek
> Cc: Ulf Hansson
> Cc: Kishon Vijay Abraham I
> Cc: Vinod Koul
> Cc: Geert Uytterhoeven
> Cc: Linus Walleij
> Cc: Daniel Lezcano
> Cc: linux-cry...@vger.kernel.org
> Cc: dri-devel@lists.freedesktop.org
> Cc: linux-l...@vger.
1 - 100 of 379 matches
Mail list logo
