[PATCH v12 0/11] dw-hdmi: convert imx hdmi to bridge/dw_hdmi

Hi Andy, On Mon, Nov 17, 2014 at 8:53 AM, Andy Yan wrote: > Andy Yan (11): > staging: imx-drm: imx-hdmi: make checkpatch happy > staging: imx-drm: imx-hdmi: return defer if can't get ddc i2c adapter > staging: imx-drm: imx-hdmi: convert imx-hdmi to drm_bridge mode > staging: imx-drm:

[PATCH] drm/dsi: Do the 'msg' check prior to dereferencing it.

From: Fabio Estevam <fabio.este...@freescale.com> Commit a52879e8d7cb ("drm/dsi: Add message to packet translator") caused the following Smatch complaint: drivers/gpu/drm/drm_mipi_dsi.c:328 mipi_dsi_create_packet() warn: variable dereferenced before check 'msg' (s

[PATCH 1/6] gpu: ipu-di: Add ipu_di_adjust_videomode()

Steve, On Mon, Dec 15, 2014 at 10:29 PM, wrote: > From: Jiada Wang > > On some monitors, high resolution modes are not working, exhibiting > pixel column truncation problems (for example, 1280x1024 displays as > 1280x1022). > > The function ipu_di_adjust_videomode() aims to fix these issues by

[PATCH] drm: armada: Use devm_ioremap_resource()

From: Fabio Estevam <fabio.este...@freescale.com> devm_request_and_ioremap() is deprecated, so use devm_ioremap_resource() instead. Signed-off-by: Fabio Estevam --- drivers/gpu/drm/armada/armada_crtc.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/drivers/g

[PATCH RFC v2 00/35] Second preview of imx-drm cleanup series

ge window sooner > rather than later, preferably getting most of this ready for that > window too. Series looks good: Reviewed-by: Fabio Estevam Patch 04/35 will not be needed in the final submission, as there is already a fix for the build issue in Greg's tree. Regards, Fabio Estevam

[PATCH] drm: armada: Use devm_ioremap_resource()

David, On Mon, Feb 10, 2014 at 7:57 PM, Fabio Estevam wrote: > From: Fabio Estevam > > devm_request_and_ioremap() is deprecated, so use devm_ioremap_resource() > instead. > > Signed-off-by: Fabio Estevam > --- Any comments about this one? > drivers/gpu/drm/

[PATCH] drm: armada: Use devm_ioremap_resource()

On Mon, Feb 24, 2014 at 11:05 AM, Russell King - ARM Linux wrote: > Given the amount of patches I'm presently dealing with, I really don't > want to bother with such trivial patches at the moment. What I do want > to do is to get stuff like imx-drm and the conversion of armada to the >

[RFC PATCH v4 4/8] staging: imx-drm: Document imx-hdmi device tree bindings

On Tue, Feb 25, 2014 at 11:23 AM, Philipp Zabel wrote: > This patch adds device tree binding documentation for the HDMI transmitter > on i.MX6. > > Signed-off-by: Philipp Zabel > --- > .../devicetree/bindings/staging/imx-drm/hdmi.txt | 53 > ++ > 1 file changed, 53

[RFC PATCH v4 4/8] staging: imx-drm: Document imx-hdmi device tree bindings

On Tue, Feb 25, 2014 at 11:23 AM, Philipp Zabel wrote: > +Required properties: > + - #address-cells : should be <1> > + - #size-cells : should be <0> > + - compatible : should be "fsl,imx6q-hdmi" or "fsl,imx6dl-hdmi". > + - gpr : should be <>. > + The phandle points to the iomuxc-gpr region

ipu-v3 build fix

On Thu, Aug 7, 2014 at 7:32 AM, Dave Airlie wrote: > does ipu-v3 need to > > select GENERIC_IRQ_CHIP > > otherwise on my arm test builds I get a failure to link due to missing > irq symbols. Which defconfig you use in order to trigger the failure?

[PATCH] Documentation: DocBook: Rename drm_stub.c to drm_drv.c cause 'make xmldocs' failed

On Tue, Aug 12, 2014 at 2:30 PM, Randy Dunlap wrote: > This patch fixed 'make xmldocs' failed on linus's tree and > linux-next as of 8th/Aug,2014. > > When drm merge for 3.17-rc1 happen, a file was renamed from > drm_stub.c to drm_drv.c. > But Documentation/DocBook/drm.tmpl still have an old

[PATCH] gpu: ipu-v3: Kconfig: Remove SOC_IMX6SL from IMX_IPUV3_CORE Kconfig

On Fri, Jun 20, 2014 at 12:06 AM, Fabio Estevam wrote: > From: Fabio Estevam > > SOC_IMX6SL does not have the IPU block, so remove it from the Kconfig entry. > > Signed-off-by: Fabio Estevam > --- > drivers/gpu/ipu-v3/Kconfig | 2 +- > 1 file changed, 1 insertion(+)

[PATCH] drm/bridge: Fix the dw_hdmi object name

From: Fabio Estevam <fabio.este...@freescale.com> Commit 66d5e6d329aed4 ("drm/bridge: Add vendor prefixes") changed the object name to dw-hdmi.o, which breaks the build: make[4]: *** No rule to make target `drivers/gpu/drm/bridge/dw-hdmi.o', needed by `drivers/gpu/drm/bridge/bu

[PATCH 00/72] staging imx-drm new features and fixes

Hi Steve, On Fri, Oct 31, 2014 at 8:53 PM, Steve Longerbeam wrote: > Hi, this affects only Freescale imx IPU and imx-drm staging drivers, > except for two patches that affect drm core (patch 53 and 63, see below). > > New features for imx-drm staging driver: > > - Support for multi-display

[PATCH] ipu-v3: ipu-smfc: Do not leave DEBUG defined

From: Fabio Estevam <fabio.este...@freescale.com> Let's only define DEBUG for debugging purpose and not by default to avoid printing debugging message unnecessarily. Signed-off-by: Fabio Estevam --- Russell, Are you still collecting ipu-v3 patches? ./scripts/get_maintainer.pl does not p

[PATCH] ipu-v3: ipu-smfc: Do not leave DEBUG defined

Hi Philipp, On Tue, Sep 2, 2014 at 6:29 AM, Philipp Zabel wrote: > Hi Fabio, > > Am Dienstag, den 02.09.2014, 00:37 -0300 schrieb Fabio Estevam: >> From: Fabio Estevam >> >> Let's only define DEBUG for debugging purpose and not by default to avoid >> printin

[PATCH] gpu: ipu-v3: Kconfig: Remove SOC_IMX6SL from IMX_IPUV3_CORE Kconfig

SOC_IMX6SL does not have the IPU block, so remove it from the Kconfig entry. Signed-off-by: Fabio Estevam --- drivers/gpu/ipu-v3/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/ipu-v3/Kconfig b/drivers/gpu/ipu-v3/Kconfig index 2f228a2..8696d20 100644

[PATCH] gpu: ipu-v3: ipu-di: Print the generated pixelclock error

: Clocks: IPU 26400Hz DI 6499Hz Needed 6500Hz imx-ipuv3 240.ipu: Want 6500Hz IPU 26400Hz DI 6499Hz using DI, 6499Hz, error 0.9% Signed-off-by: Fabio Estevam --- drivers/gpu/ipu-v3/ipu-di.c | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git

[PATCH, RFC] i.MX DRM support

ile still being able to change bigger amounts of the driver without breaking > officially supported features. What do you think about this? +1 on this. Thanks for your hard work on this, Sascha. Regards, Fabio Estevam

[PATCH] drm/crtc-helper: gc usless connectro loop in disable_unused_functions

On Sun, Apr 13, 2014 at 4:39 PM, Daniel Vetter wrote: > I've forgotten to clean this all up correctly in > > commit e3d6ddb35f6221859b6054879d186e13a3af351e > Author: Daniel Vetter > Date: Tue Apr 1 22:15:00 2014 +0200 > > drm/crtc-helper: don't disable disconnected outputs > >

[PATCH 1/2] drm: radeon: ni_dpm: Fix unused variable warning when CONFIG_ACPI=n

From: Fabio Estevam <fabio.este...@freescale.com> With CONFIG_ACPI=n the following build warning is seen: drivers/gpu/drm/radeon/ni_dpm.c:3448:31: warning: unused variable 'eg_pi' [-Wunused-variable] Move the definition of eg_pi inside the CONFIG_ACPI 'if' block. Signed-off-by: Fabio E

[PATCH 2/2] drm: radeon: cypress_dpm: Fix unused variable warning when CONFIG_ACPI=n

From: Fabio Estevam <fabio.este...@freescale.com> With CONFIG_ACPI=n the following build warning is seen: drivers/gpu/drm/radeon/cypress_dpm.c:302:31: warning: unused variable 'eg_pi' [-Wunused-variable] Move the definition of eg_pi inside the CONFIG_ACPI 'if' block. Signed-off-by:

[PATCHv3 3/8] staging: imx-drm: ipuv3-crtc: don't harcode some mode flags.

Hi Denis, On Tue, Nov 12, 2013 at 2:49 PM, Denis Carikli wrote: > This change is needed for making the eukrea-cpuimx51 > QVGA display work. > > Greg Kroah-Hartman > Cc: driverdev-devel at linuxdriverproject.org > Cc: Philipp Zabel > Cc: Sascha Hauer > Cc: Shawn Guo > Cc: linux-arm-kernel

[PATCH] drm: drm_drv: Only call drm_agp_clear() in __OS_HAS_AGP case

From: Fabio Estevam <fabio.este...@freescale.com> Commit 28ec711 (drm/agp: move AGP cleanup paths to drm_agpsupport.c) causes the following link error on ARM (imx_v6_v7_defconfig): drivers/built-in.o: In function `drm_lastclose': :(.text+0x588a0): undefined reference to `drm_agp_clear

[PATCH 1/3] ARM: imx6q: refactor some ldb related clocks

On Tue, Aug 20, 2013 at 5:38 AM, Liu Ying wrote: > diff --git a/Documentation/devicetree/bindings/clock/imx6q-clock.txt > b/Documentation/devicetree/bindings/clock/imx6q-clock.txt > index 5a90a72..90e923e 100644 > --- a/Documentation/devicetree/bindings/clock/imx6q-clock.txt > +++

Building DRM for i.MX fails with linux-next 20130212

, Fabio Estevam

Building DRM for i.MX fails with linux-next 20130212

Dave/Bjorn, On Tue, Feb 12, 2013 at 3:50 PM, Fabio Estevam wrote: > Hi, > > Building imx_v6_v7_defconfig on linux-next 20130212 gives me the > following build error: > > CC drivers/gpu/drm/drm_pci.o > drivers/gpu/drm/drm_pci.c: In function ?drm_pcie_get_speed_cap_mas

[PATCH] CHROMIUM: drm: bridge/dw_hdmi: Eliminate unused cable_plugin

On Mon, Oct 5, 2015 at 4:17 PM, Russell King - ARM Linux wrote: > On Sat, Sep 26, 2015 at 05:32:12PM -0300, Fabio Estevam wrote: >> On Mon, Sep 21, 2015 at 11:15 AM, Russell King - ARM Linux >> wrote: >> >> > My current patch stack for imx-drm related stuff l

[PATCH 03/12] gpu: imx: simplify sync polarity setting

sell King <rmk+kernel at arm.linux.org.uk> Reviewed-by: Fabio Estevam

[PATCH 04/12] gpu: imx: fix support for interlaced modes

he IPU. > > Signed-off-by: Russell King <rmk+kernel at arm.linux.org.uk> Reviewed-by: Fabio Estevam

[PATCH 05/12] drm: bridge/dw_hdmi: add support for interlaced video modes

gt; > Signed-off-by: Russell King <rmk+kernel at arm.linux.org.uk> Reviewed-by: Fabio Estevam

[PATCH 11/12] drm: bridge/dw_hdmi: add connector mode forcing

nd this problem. Although this requires > manual configuration, it is better than nothing at all. > > When a forced connection state has been set, there is no point handling > our RXSENSE interrupts, so disable them in this circumstance. > > Signed-off-by: Russell King <rmk+kernel at arm.linux.org.uk> Reviewed-by: Fabio Estevam at freescale.com

[PATCH 12/12] drm: bridge/dw_hdmi: improve HDMI enable/disable handling

signal to cause a re-read of the EDID data will not cause the bridge > to immediately disable the video signal. > > Signed-off-by: Russell King <rmk+kernel at arm.linux.org.uk> Reviewed-by: Fabio Estevam

[PATCH 1/9] drm: bridge/dw_hdmi-ahb-audio: add audio driver

On Sat, Aug 8, 2015 at 1:10 PM, Russell King wrote: > Add ALSA based HDMI AHB audio driver for dw_hdmi. The only buffer > format supported by the hardware is its own special IEC958 based format, > which is not compatible with any ALSA format. To avoid doing too

[PATCH 1/9] drm: bridge/dw_hdmi-ahb-audio: add audio driver

On Tue, Oct 6, 2015 at 3:18 PM, Russell King - ARM Linux wrote: > Sorry, I've been out for most of the day. There's no DT patches required. > > The dw_hdmi bridge driver creates its own platform device for the audio, > which should then bind to the dw_hdmi-ahb-audio driver using normal Linux >

[PATCH 1/9] drm: bridge/dw_hdmi-ahb-audio: add audio driver

nks, Russell! Got audio to play on my HDMI TV :-) For the entire series: Tested-by: Fabio Estevam

i.mx6 video out in mainline

On Tue, Oct 6, 2015 at 6:52 PM, Pushpal Sidhu wrote: > Hi All, > > I'm attempting to use a standard fb console (using the > imx6qdl-gw54xx.dtsi), but I find that it only draws to the 1024x768p > portion of the screen. This is also true when running the userspace > tool fb-test. Looking at

i.mx6 video out in mainline

On Tue, Oct 6, 2015 at 8:02 PM, Pushpal Sidhu wrote: > When I took your patch and adapted it for imx6qdl-gw54xx.dtsi, I found > that HDMI video out was slightly shifted to the left and resolution > remained at 1024x768p. > > I also found that when I disabled DRM_IMX_LDB, HDMI out stopped >

[PATCH 1/9] drm: bridge/dw_hdmi-ahb-audio: add audio driver

On Fri, Oct 9, 2015 at 1:00 PM, Russell King - ARM Linux wrote: >> Thanks, Russell! >> >> Got audio to play on my HDMI TV :-) >> >> For the entire series: >> >> Tested-by: Fabio Estevam > > Just to confirm - that's for _all_ of these 8

[PATCH 00/48] Etnaviv changes RFCv1->RFCv2

Hi Jon, On Tue, Oct 20, 2015 at 7:09 AM, Jon Nettleton wrote: > I agree, although we can also point them to the device-tree option to > workaround the problem temporarily. > > Christian, fyi I have fixed this in u-boot for all the SolidRun platforms. This is fixed in mainline U-boot for mx6:

imx IPU2 video out

re trying to use the same clock source. Take a look at how we solved this for mx6dl-sabresd: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/imx6qdl-sabresd.dtsi?id=d28be499c45e6e16d7a042ce280eb872dc06952b Regards, Fabio Estevam

i.mx6 video out in mainline

On Thu, Oct 8, 2015 at 5:54 PM, Pushpal Sidhu wrote: > Comparing the imx6qdl-gw54xx.dtsi and imx6qdl-sabersd.dtsi, I couldn't > see too many differences between HDMI and LVDS, so I'm a little > surprised you don't see this exact same behavior there. Note that I've On a imx6q-sabresd I get HDMI

mx6 hdmi resolution behaviour

] imx-ipuv3 240.ipu: videomode adapted for IPU restrictions Shouldn't we get 1920x1080 in this case as well? Regards, Fabio Estevam

mx6 hdmi resolution behaviour

On Tue, Jun 23, 2015 at 1:44 PM, Russell King - ARM Linux wrote: > If you have no connected connectors, then you get 1024x768: > > imx-drm display-subsystem: No connectors reported connected with modes > [drm] Cannot find any crtc or sizes - going 1024x768 > > as that's what DRM defaults to when

drm: imx: multi-display support questions

a mx6q-sabresd. Regards, Fabio Estevam

drm: imx: multi-display support questions

On Tue, Jun 23, 2015 at 2:49 PM, Fabio Estevam wrote: > Hi Gary, > > On Wed, May 27, 2015 at 10:31 AM, Gary Bisson > wrote: > >> Ok, thanks, I'll check and see what I need to get all the displays to >> work together. > > With this patch: > http://lists.infr

mx6 hdmi resolution behaviour

On Tue, Jun 23, 2015 at 5:41 PM, Russell King - ARM Linux wrote: > I've just tried this (the HBi1 was booted previously with the HDMI socket > disconnected). Just now, I turned the TV on, and then connected it to > the HDMI. Thanks for testing it. > The TV reported a resolution of 1024x768,

mx6 hdmi resolution behaviour

On Tue, Jun 23, 2015 at 5:58 PM, Russell King - ARM Linux wrote: >> That's the point that makes me confused: shouldn't it report a higher >> resolution like 1080p? > > No - it won't go higher than the initial mode that was set. See > drm_fb_helper_hotplug_event(): > > max_width =

drm: imx: multi-display support questions

ly use the same > configuration for our platforms. What do you mean by "use the same configuration for our platforms"? I was planning to send the two attached patches. Are you and Eric OK with them? Regards, Fabio Estevam -- next part -- A non-text attachmen

drm: imx: multi-display support questions

On Mon, Jun 29, 2015 at 1:12 PM, Gary Bisson wrote: > I am ok with it but I'd like Eric to ack it too as he might have some remarks. Ok, I will submit it to the linux-arm mailing list with you and Eric on Cc. Regards, Fabio Estevam

[PATCH] CHROMIUM: drm: bridge/dw_hdmi: Eliminate unused cable_plugin

On Mon, Sep 21, 2015 at 11:15 AM, Russell King - ARM Linux wrote: > My current patch stack for imx-drm related stuff looks like this at > present: > > drm: bridge/dw_hdmi: place PHY into low power mode when disabled > drm: bridge/dw_hdmi: start of support for pixel doubled modes > drm:

drm: imx: multi-display support questions

have seen this error sometime ago. Do you get HDMI image if you unplug/plug the HDMI cable? This was also fixed by Steve Longerbeam series and we still need to fix it in mainline. Regards, Fabio Estevam

[PATCH 0/5] i.MX5/6 mem2mem scaler

s patchset is good, are there any comments to > the gpu part of this patchset? > > I talked with Mauro on the IRC and he acked that this patchset could be > merged via the gpu subsystem. Do you plan to resend this series? It is still not applied. Regards, Fabio Estevam

[PATCH] drm: imx: imx-tve: Check and propagate the errors

From: Fabio Estevam <fabio.este...@freesale.com> In the case of errors we should propagate them. Signed-off-by: Fabio Estevam --- drivers/gpu/drm/imx/imx-tve.c | 14 +++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/imx/imx-tve.c b/drivers/g

[PATCH 00/72] staging imx-drm new features and fixes

if we just wait until imx-drm is moved > and then I will resubmit the imx-drm patches, and in the meantime > I will go ahead and resubmit only the IPU patches. imx-drm has moved out of staging. Do you plan to re-submit this series? Thanks, Fabio Estevam

[PATCH v2] drm: imx: imx-tve: Check and propagate the errors

From: Fabio Estevam <fabio.este...@freescale.com> In the case of errors we should propagate them. Signed-off-by: Fabio Estevam --- Changes since v1: - Fixed a typo on my FSL address drivers/gpu/drm/imx/imx-tve.c | 14 +++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff

[PATCH v3] drm: imx: imx-tve: Check and propagate the errors

From: Fabio Estevam <fabio.este...@freescale.com> In the case of errors we should propagate them. Signed-off-by: Fabio Estevam --- Changes since v2: - Propage the error in more places like suggested by Philipp drivers/gpu/drm/imx/imx-tve.c | 24 1 file chang

[PATCH v4 9/9] drm/exynos: add support for 'hdmi' clock

On Tue, Jan 20, 2015 at 10:16 AM, Marek Szyprowski wrote: > + mixer_res->hdmi = devm_clk_get(dev, "hdmi"); > + if (IS_ERR(mixer_res->hdmi)) { > + dev_err(dev, "failed to get clock 'hdmi'\n"); > + return -ENODEV; 'return PTR_ERR(mixer_res->hdmi);' would be

[PATCH v2 0/7] imx-drm: ipuv3-crtc: Implement mode_fixup

Hi Philipp, On Fri, Jan 23, 2015 at 8:50 AM, Philipp Zabel wrote: > What are this panel timings? The adjustment should increase the vertical > back porch by up to two lines (so it is at least two lines), reducing > the front porch or vsync length by the same amount. Does this panel use > the

[PATCH v2 0/7] imx-drm: ipuv3-crtc: Implement mode_fixup

On Fri, Jan 23, 2015 at 12:56 AM, Liu Ying wrote: > Hi, > > It looks that the below commit makes my Hannstar XGA LVDS panel stop working > on the i.MX6DL SabreSD board. Any idea? Yes, with eb10d6355532def3a ("mx-drm: encoder prepare/mode_set must use adjusted mode") applied the DI clock is 0:

[PATCH v2 0/7] imx-drm: ipuv3-crtc: Implement mode_fixup

Hi Philipp, On Fri, Jan 23, 2015 at 2:18 PM, Philipp Zabel wrote: > @@ -281,6 +267,9 @@ static void imx_ldb_encoder_mode_set(struct drm_encoder > *encoder, > struct imx_ldb_channel *imx_ldb_ch = enc_to_imx_ldb_ch(encoder); > struct imx_ldb *ldb = imx_ldb_ch->ldb; > int

[PATCH v2 0/7] imx-drm: ipuv3-crtc: Implement mode_fixup

On Fri, Jan 23, 2015 at 2:39 PM, Philipp Zabel wrote: > Am Freitag, den 23.01.2015, 14:27 -0200 schrieb Fabio Estevam: >> Hi Philipp, >> >> On Fri, Jan 23, 2015 at 2:18 PM, Philipp Zabel >> wrote: >> > @@ -281,6 +267,9 @@ static void imx_ldb_encoder_mode_s

[PATCH] drm/cma: Use the %zu specifier for printing size_t

From: Fabio Estevam <fabio.este...@freescale.com> Building for arm64 causes the following warnings: drivers/gpu/drm/drm_gem_cma_helper.c: In function 'drm_gem_cma_create': drivers/gpu/drm/drm_gem_cma_helper.c:114:4: warning: format '%d' expects argument of type 'int', but argument 3 ha

[PATCH 2/2] drm: bridge/sti_dvo: Adapt to bridge API change

n function 'sti_dvo_bind': drivers/gpu/drm/sti/sti_dvo.c:419:2: error: implicit declaration of function 'drm_bridge_init' [-Werror=implicit-function-declaration] Signed-off-by: Fabio Estevam --- drivers/gpu/drm/sti/sti_dvo.c | 11 ++- 1 file changed, 2 insertions(+), 9 deletions(-)

[PATCH 1/2] drm: bridge/dw_hdmi: Adapt to bridge API change

/dw_hdmi.c: In function 'dw_hdmi_register': drivers/gpu/drm/bridge/dw_hdmi.c:1535:2: error: implicit declaration of function 'drm_bridge_init' [-Werror=implicit-function-declaration] Signed-off-by: Fabio Estevam --- drivers/gpu/drm/bridge/dw_hdmi.c | 11 ++- 1 file changed, 2 insert

[PATCH] drm: bridge/dw_hdmi: Fix return error path

If devm_request_threaded_irq() fails we should jump to 'err_iahb' label that will disable the clocks that were previously enabled. Signed-off-by: Fabio Estevam --- drivers/gpu/drm/bridge/dw_hdmi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/bridge

[PATCH] drm/bridge: dw_hdmi: Return the real error on drm_bridge_attach() failure

From: Fabio Estevam <fabio.este...@freescale.com> drm_bridge_attach() may return different errors on failure, not just -EINVAL, so it is better to propagate the real error instead. Signed-off-by: Fabio Estevam --- drivers/gpu/drm/bridge/dw_hdmi.c | 2 +- 1 file changed, 1 insertion

[PATCH] drm/i2c: tda998x: Use '%zd' for printing 'ssize_t' format

' [-Wformat=] Reported-by: Olof's autobuilder Signed-off-by: Fabio Estevam --- drivers/gpu/drm/i2c/tda998x_drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i2c/tda998x_drv.c b/drivers/gpu/drm/i2c/tda998x_drv.c index 011e1ca..d5dc8aa 100644 --- a/drivers/gpu/drm

[PATCH 1/5] DRM: add i.MX IPUv3 base driver

Hi Sascha, On Tue, Jun 7, 2011 at 7:45 AM, Sascha Hauer wrote: ... > +static int __init imx_ipu_init(void) > +{ > + ? ? ? int32_t ret; > + > + ? ? ? ret = platform_driver_register(_ipu_driver); > + ? ? ? return 0; Did you intend to return ret here instead? Regards, Fabio Estevam

[PATCH] README: Fix grammar

Fix two grammar issues: - "standard autotools packages ---> "standard autotools package" - "If you are install" ---> "If you are installing" Signed-off-by: Fabio Estevam <feste...@gmail.com> --- README | 6 +++--- 1 file changed, 3 insertions(+

Re: DVI output on i.MX51 EVP board not working?

> bisect, unfortunately. It was a long time I worked on this commit and it worked well for me on an old DVI monitor. I will try to locate such monitor in the office next week and try it again. Regards, Fabio Estevam ___ dri-devel mailing list dri

Re: DVI output on i.MX51 EVP board not working?

On Wed, Apr 5, 2017 at 10:05 AM, Wladimir J. van der Laan wrote: > Ok, thanks for testing. > > To be clear: was this result with v3.x, or with mainline? I tested with 4.11-rc5 and the kernel is driving the DVI monitor correctly. ___

Re: [PATCH] drm/panel: simple: Add support for Seiko 43WVF1G

Thierry/Rob, On Tue, Feb 7, 2017 at 10:48 PM, Fabio Estevam <feste...@gmail.com> wrote: > On Tue, Feb 7, 2017 at 9:36 PM, Rob Herring <r...@kernel.org> wrote: > >> Except I have no way of knowing whether: a) you omitted a supply >> because you don't (yet) care, b)

Re: [PATCH 1/2] drm/bridge: ti-tfp410: support hpd via gpio

Hi Christopher, On Mon, Mar 6, 2017 at 6:40 PM, wrote: > From: Christopher Spinrath > > On some boards the hpd pin of a hdmi connector is wired up to a gpio > pin. Since in the DRM world the tfp410 driver is responsible

Re: DVI output on i.MX51 EVP board not working?

On Sat, Apr 1, 2017 at 6:40 PM, Fabio Estevam <feste...@gmail.com> wrote: > Hi Wladimir, > > On Fri, Mar 31, 2017 at 2:36 AM, Wladimir J. van der Laan > <laa...@gmail.com> wrote: > >> - Went as far back as kernel v4.0, even to v3.12 or so (commit 493a863, "

[PATCH] drm/panel: simple: Remove unneeded gpiod NULL check

From: Fabio Estevam <fabio.este...@nxp.com> The gpiod API checks for NULL descriptors, so there is no need to duplicate the check in the driver. Signed-off-by: Fabio Estevam <fabio.este...@nxp.com> --- drivers/gpu/drm/panel/panel-simple.c | 6 ++ 1 file changed, 2 insertions(+),

Re: [PATCH] drm/panel: Add driver for Seiko 43WVF1G panel

Rob, On Wed, Jun 14, 2017 at 2:49 PM, Thierry Reding wrote: >> +Required properties: >> +- compatible: should be "sii,43wvf1g". >> +- "DVDD-supply": 3v3 digital regulator. >> +- "AVDD-supply": 5v analog regulator. > > I don't think we should be using all-uppercase for

[PATCH] drm/panel: simple: Skip error message on deferred probe

From: Fabio Estevam <fabio.este...@nxp.com> When enable_gpio is provided via an I2C or SPI expander, it may not be available when panel-simple probes leading to the following error: panel-simple panel: failed to request GPIO: -517 As this error message is not very useful to the end user

Re: Etnaviv crashes on glmark2

On Tue, Aug 22, 2017 at 9:47 AM, Fabio Estevam <feste...@gmail.com> wrote: > Hi, > > I am running kernel 4.12.8 and mesa 17.1.6 on a imx6q, but glmark2 > never runs successfully until the end. It always crashes like this: > > ** Failed to set swap interval. Results may be

Re: Etnaviv crashes on glmark2

Hi Lucas, On Wed, Aug 23, 2017 at 9:06 AM, Lucas Stach wrote: >> I don't recognize this either, I haven't seen a kernel memory managment >> error while >> running glmark2 (or anything w/ etnaviv) for a long time. Strange. > > This might also be related to the used

Re: [PATCH] drm/panel: Add driver for Seiko 43WVF1G panel

Hi Rob, On Wed, Jun 14, 2017 at 2:49 PM, Thierry Reding wrote: > On Tue, Apr 25, 2017 at 01:18:35PM -0300, Marco Franchi wrote: >> Add driver for Seiko Instruments Inc. 4.3" WVGA (800 x RGB x 480) >> TFT with Touch-Panel. >> >> Datasheet available at: >>

Re: [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller

Hi Marek, On Mon, May 22, 2017 at 11:20 AM, Marek Vasut wrote: > IMO it's OK. > > Reviewed-by: Marek Vasut Thanks for the feedback. Do you plan to send Dave a pull request so that this one can reach 4.12-rc? Thanks

[PATCH RESEND] drm: mxsfb_crtc: Reset the eLCDIF controller

From: Fabio Estevam <fabio.este...@nxp.com> According to the eLCDIF initialization steps listed in the MX6SX Reference Manual the eLCDIF block reset is mandatory. Without performing the eLCDIF reset the display shows garbage content when the kernel boots. In earlier tests this iss

Re: [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller

Hi Marek, On Fri, May 5, 2017 at 3:01 PM, Fabio Estevam <fabio.este...@nxp.com> wrote: > According to the eLCDIF initialization steps listed in the MX6SX > Reference Manual the eLCDIF block reset is mandatory. > > Without performing the eLCDIF reset the display shows garb

Re: [PATCH RESEND] drm: mxsfb_crtc: Reset the eLCDIF controller

On Mon, May 22, 2017 at 5:53 PM, Fabio Estevam <feste...@gmail.com> wrote: > From: Fabio Estevam <fabio.este...@nxp.com> > > According to the eLCDIF initialization steps listed in the MX6SX > Reference Manual the eLCDIF block reset is mandatory. > > Without performin

[PATCH RESEND] drm: mxsfb_crtc: Reset the eLCDIF controller

From: Fabio Estevam <fabio.este...@nxp.com> According to the eLCDIF initialization steps listed in the MX6SX Reference Manual the eLCDIF block reset is mandatory. Without performing the eLCDIF reset the display shows garbage content when the kernel boots. In earlier tests this iss

Re: [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller

Hi Marek, On Mon, May 22, 2017 at 5:33 PM, Marek Vasut wrote: >> Do you plan to send Dave a pull request so that this one can reach 4.12-rc? > > You could probably get it in via drm-misc ? I tried it, but no response so far. Care to send Dave a pull request so that this one can

Re: [PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller

Hi Marek, On Mon, Jun 5, 2017 at 9:08 AM, Marek Vasut wrote: > I'm currently on vacation, try one more time and if it doesn't work out > (which means this trivial list is not really working?), I'll send a PR > sometime mid-month. Tried your suggestion, but it did not work.

Re: [PATCH] drm/panel: Add driver for Seiko 43WVF1G panel

Thierry/Rob, On Mon, May 8, 2017 at 10:54 AM, Fabio Estevam <feste...@gmail.com> wrote: > On Tue, Apr 25, 2017 at 1:18 PM, Marco Franchi <marco.fran...@nxp.com> wrote: >> Add driver for Seiko Instruments Inc. 4.3" WVGA (800 x RGB x 480) >> TFT with Touch-

[PATCH v3] drm: mxsfb_crtc: Reset the eLCDIF controller

was previously showing a splash screen and the bootloader display driver does properly implement the eLCDIF reset. Add the eLCDIF reset to the driver, so that it can operate correctly independently of the bootloader. Tested on a imx6sx-sdb board. Cc: <sta...@vger.kernel.org> Signed-off-by: Fabio E

[PATCH] drm: mxsfb_crtc: Reset the eLCDIF controller

was previously showing a splash screen and the bootloader display driver does properly implement the eLCDIF reset. Add the eLCDIF reset to the driver, so that it can operate correctly independently of the bootloader. Tested on a imx6sx-sdb board. Cc: <sta...@vger.kernel.org> Signed-off-by: Fabio E

[PATCH v2] drm: mxsfb_crtc: Reset the eLCDIF controller

was previously showing a splash screen and the bootloader display driver does properly implement the eLCDIF reset. Add the eLCDIF reset to the driver, so that it can operate correctly independently of the bootloader. Tested on a imx6sx-sdb board. Cc: <sta...@vger.kernel.org> Signed-off-by: Fabio E

[PATCH] drm: mxsfb_crtc: Print bus_format in hexadecimal

From: Fabio Estevam <fabio.este...@nxp.com> Media bus formats are represented in hexadecimal format in include/uapi/linux/media-bus-format.h, so it is better to print the error message using the bus_format variable in hexadecimal. Signed-off-by: Fabio Estevam <fabio.este...@nxp.com>

Re: [PATCH] drm/panel: Add driver for Seiko 43WVF1G panel

om Breno Lima. > > Signed-off-by: Marco Franchi <marco.fran...@nxp.com> Works fine on a imx6sx-sdb board: Tested-by: Fabio Estevam <fabio.este...@nxp.com> ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel

[PATCH v2] gpu: ipu-v3: ipu-dc: Remove unused 'di' variable

From: Fabio Estevam <fabio.este...@nxp.com> The 'di' variable is never used inside ipu_dc_enable_channel(), so just remove it. This fixes the following build warning with W=1: drivers/gpu/ipu-v3/ipu-dc.c: In function 'ipu_dc_enable_channel': drivers/gpu/ipu-v3/ipu-dc.c:252:6: warning: va

Re: [PATCH v2 resend] drm/panel: Add driver for Seiko 43WVF1G panel

Hi Thierry, On Wed, Aug 30, 2017 at 11:12 AM, Thierry Reding <thierry.red...@gmail.com> wrote: > On Tue, Aug 29, 2017 at 02:29:08PM -0300, Fabio Estevam wrote: >> Hi Thierry, >> >> On Fri, Aug 18, 2017 at 12:08 PM, Thierry Reding >> <thierry.red...@gmail.com&

[PATCH] gpu: ipu-v3: ipu-dc: Remove unused 'di' variable

From: Fabio Estevam <fabio.este...@nxp.com> The 'di' variable is never used inside lipu_dc_enable_channel(), so just remove it. This fixes the following build warning with W=1: drivers/gpu/ipu-v3/ipu-dc.c: In function 'ipu_dc_enable_channel': drivers/gpu/ipu-v3/ipu-dc.c:252:6: warning: va

Re: [PATCH v2 resend] drm/panel: Add driver for Seiko 43WVF1G panel

Hi Thierry, On Fri, Aug 18, 2017 at 12:08 PM, Thierry Reding wrote: > I've applied, though somewhat reluctantly, this to drm-misc-next without > Rob's Acked-by, but the device tree bindings look trivial enough. Was it really applied? I am not able to find this patch

Etnaviv crashes on glmark2

Hi, I am running kernel 4.12.8 and mesa 17.1.6 on a imx6q, but glmark2 never runs successfully until the end. It always crashes like this: ** Failed to set swap interval. Results may be bounded above by refresh rate. [conditionals] fragment-steps=0:vertex-steps=0: FPS: 63 FrameTime: 15.873 ms [

Re: Etnaviv crashes on glmark2

On Wed, Aug 23, 2017 at 10:13 AM, Fabio Estevam <feste...@gmail.com> wrote: > In order to reproduce the failure, just run 'glmark2-es2-drm' and wait > until it completes. The crash always happen after the last test runs. I have been running glmark2 tests with linux-next-20170824 over

<    1   2   3   4   5   6   >