case, continued to work as before.
Tested against 3.16-rc6 with this patchset and the earlier patchset from
Guido applied.
Also tested on BeagleBone Black even though it doesn't have a panel,
just to make sure nothing changed there.
For the series:
Tested-by: Darren Etheridge
> Ezeq
tda998x)
Tested against 3.16-rc6, using unmodified tilcdc driver, unmodified dts.
Version details:
Linux am335x-evm 3.16.0-rc6-2-gf8a096f-dirty #40 SMP Thu Jul 24
13:49:42 CDT 2014 armv7l GNU/Linux
Tried modetest with a variety of modes, all looked correct.
Tested as both built-in and modules.
Tested-by: Darren Etheridge
42 CDT 2014 armv7l GNU/Linux
Tried modetest with a variety of modes, all looked correct.
Tested as both built-in and modules.
Tested-by: Darren Etheridge
On 07/01/2014 06:39 PM, Guido Mart?nez wrote:
> On Fri, Jun 27, 2014 at 05:08:51PM -0500, Darren Etheridge wrote:
>> [snip]
>>
>> Otherwise I think this is a good and useful patch series.
> It that a Tested-by tag? :)
Sure - I would prefer that the WARN_ON was silenced wh
Guido,
On 06/17/2014 09:17 AM, Guido Mart?nez wrote:
> The tilcdc driver could be compiled as a module, but was severely broken
> and could not be used as such. This patchset attempts to fix the issues
> preventing a proper load/unload of the module.
>
> Issues included dangling sysfs nodes, dangl
Guido,
On 06/17/2014 09:17 AM, Guido Mart?nez wrote:
> The TI tilcdc driver is designed with a notion of submodules. Currently,
> at unload time, these submodules are iterated and destroyed.
>
> Now that the tilcdc remove order is fixed, this can be handled perfectly
I am not sure I understand th
On 06/17/2014 09:17 AM, Guido Mart?nez wrote:
> Use module_init instead of late_initcall, as is the norm for modular
> drivers.
>
> module_init was used until 6e8de0bd6a51fdeebd5d975c4fcc426f730b339b
> ("drm/tilcdc: add encoder slave (v2)") changed it to a late_initcall,
> but it does not explain w
Guido,
Thanks and sorry I missed this the first time around. I'll give it a
try on a few of my AM335x based boards when I have access to them again
on Monday.
Darren
On 06/17/2014 09:17 AM, Guido Mart?nez wrote:
> The tilcdc driver could be compiled as a module, but was severely broken
> and
Rob Clark wrote on Thu [2014-Apr-24 16:51:04 -0400]:
> On Mon, Mar 3, 2014 at 2:08 PM, Felipe Balbi wrote:
> > From: Darren Etheridge
> >
> > 1680x1050 appears to also be within the bandwidth capabilities
> > of the device and memory infrastructure.
>
> For t
Jean-Francois Moine wrote on Tue [2014-Jan-28 18:12:18
+0100]:
> On Thu, 23 Jan 2014 17:29:07 -0600
> Darren Etheridge wrote:
>
> > > @@ -896,9 +897,9 @@ tda998x_encoder_mode_set(struct drm_encoder *encoder,
> > >* TDA19988 requires high-active sync at input stag
Jean-Francois Moine wrote on Sun [2014-Jan-19 19:58:40
+0100]:
> This patch uses always the adjusted video mode instead of a mix of
> original and adjusted mode.
>
> Signed-off-by: Jean-Francois Moine
> ---
> drivers/gpu/drm/i2c/tda998x_drv.c | 66
> +++
>
original mainline NXP/tilcdc drm drivers anyway.
So for the series:
Tested-by: Darren Etheridge
Darren
original mainline NXP/tilcdc drm drivers anyway.
So for the series:
Tested-by: Darren Etheridge
Darren
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
ices
> drm/i2c: nxp-tda998x: ensure VIP output mux is properly set
> drm/i2c: nxp-tda998x: fix npix/nline programming
> drm/i2c: nxp-tda998x: prepare for video input configuration
> drm/i2c: nxp-tda998x: add video and audio input configuration
>
> Sebastian Hesselbarth:
> drm/i2c:
ices
> drm/i2c: nxp-tda998x: ensure VIP output mux is properly set
> drm/i2c: nxp-tda998x: fix npix/nline programming
> drm/i2c: nxp-tda998x: prepare for video input configuration
> drm/i2c: nxp-tda998x: add video and audio input configuration
>
> Sebastian Hesselbarth:
> drm/i2c:
Add a fixup function that will flip the hsync priority and
add a hskew value that is used to shift the tda998x to the
right by a variable number of pixels depending on the mode.
This works around an issue with the sync timings that tilcdc
is outputing.
Signed-off-by: Darren Etheridge
Add necessary support for flipping the hsync signal and shifting
the display to the right by a certain number of pixels. Changes
only take effect if adjusted_mode is changed in fixup function.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/i2c/tda998x_drv.c | 10 ++
1 files
erified using a
HDMI analyzer and are reporting correct timings at the output stage.
Hopefully this will allow the dove/tda driver changes to progress now that
were blocked as per this discussion:
http://lists.freedesktop.org/archives/dri-devel/2013-July/040900.html
Darren Etheridge (2):
drm/i2c
Add a fixup function that will flip the hsync priority and
add a hskew value that is used to shift the tda998x to the
right by a variable number of pixels depending on the mode.
This works around an issue with the sync timings that tilcdc
is outputing.
Signed-off-by: Darren Etheridge
Add necessary support for flipping the hsync signal and shifting
the display to the right by a certain number of pixels. Changes
only take effect if adjusted_mode is changed in fixup function.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/i2c/tda998x_drv.c | 10 ++
1 files
erified using a
HDMI analyzer and are reporting correct timings at the output stage.
Hopefully this will allow the dove/tda driver changes to progress now that
were blocked as per this discussion:
http://lists.freedesktop.org/archives/dri-devel/2013-July/040900.html
Darren Etheridge (2):
drm/i2c
Rob Clark wrote on Wed [2013-Jun-26 11:42:44 -0400]:
> On Fri, Jun 21, 2013 at 2:52 PM, Darren Etheridge
> wrote:
> > The series of patches that follow are intended to address issues that
> > have been found in the tilcdc drm driver. The patchset enables support
> > for
Rob Clark wrote on Wed [2013-Jun-26 11:42:44 -0400]:
> On Fri, Jun 21, 2013 at 2:52 PM, Darren Etheridge wrote:
> > The series of patches that follow are intended to address issues that
> > have been found in the tilcdc drm driver. The patchset enables support
> > for sc
From: Pantelis Antoniou
Bits weren't cleared so resolution changes didn't work.
Signed-off-by: Pantelis Antoniou
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/
In certain senarios drm will initialize before i2c this means that i2c
slave devices like the nxp tda998x will fail to be probed. This patch
detects this condition then defers the probe of the slave device and
the tilcdc main driver.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc
keeping checkpatch happy.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 16 ++--
1 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
index 283e0a6..6118651 100644
The tilcdc has a number of limitations for the allowed sizes of
the various adjustable timing parameter. Some modes are outside
of these timings. This commit will prune modes that report timings
that will overflow the allowed sizes in the tilcdc.
Signed-off-by: Darren Etheridge
---
drivers
When hooking up to an HDMI analyzer noticed some timings were
off by one. Referring to the hardware technical reference manual
for the lcd controller some of the timing registers use 0 to
represent 1. This patch addresses that issue.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc
Adding support for max-pixelclock and max-width device tree
entries. As some devices that use the tilcdc hardware module
have restrictions on the allowed/tested values. Also update DT
bindings document to reflect new parameters.
Signed-off-by: Darren Etheridge
---
.../devicetree/bindings/drm
TI LCD controller version 2 has an extended eleventh
bit that enables horizontal resolutions greater than
1024 pixels to be specified (upto 2048). This patch
adds support for setting this bit on LCDC V2.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 15
modesetting to work correctly
Fix an issue where the slave encoder can initialize before the i2c
subsystem, resulting in no displays being configured.
Applies cleanly on drm-next.
Darren Etheridge (6):
drm/tilcdc: support pixel widths greater than 1024
drm/tilcdc: adding
From: Pantelis Antoniou
Bits weren't cleared so resolution changes didn't work.
Signed-off-by: Pantelis Antoniou
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/
In certain senarios drm will initialize before i2c this means that i2c
slave devices like the nxp tda998x will fail to be probed. This patch
detects this condition then defers the probe of the slave device and
the tilcdc main driver.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc
keeping checkpatch happy.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 16 ++--
1 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
index 283e0a6..6118651 100644
When hooking up to an HDMI analyzer noticed some timings were
off by one. Referring to the hardware technical reference manual
for the lcd controller some of the timing registers use 0 to
represent 1. This patch addresses that issue.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc
The tilcdc has a number of limitations for the allowed sizes of
the various adjustable timing parameter. Some modes are outside
of these timings. This commit will prune modes that report timings
that will overflow the allowed sizes in the tilcdc.
Signed-off-by: Darren Etheridge
---
drivers
Adding support for max-pixelclock and max-width device tree
entries. As some devices that use the tilcdc hardware module
have restrictions on the allowed/tested values. Also update DT
bindings document to reflect new parameters.
Signed-off-by: Darren Etheridge
---
.../devicetree/bindings/drm
TI LCD controller version 2 has an extended eleventh
bit that enables horizontal resolutions greater than
1024 pixels to be specified (upto 2048). This patch
adds support for setting this bit on LCDC V2.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 15
modesetting to work correctly
Fix an issue where the slave encoder can initialize before the i2c
subsystem, resulting in no displays being configured.
Applies cleanly on drm-next.
Darren Etheridge (6):
drm/tilcdc: support pixel widths greater than 1024
drm/tilcdc: adding
TI LCD controller version 2 has an extended eleventh
bit that enables horizontal resolutions greater than
1024 pixels to be specified (upto 2048). This patch
adds support for setting this bit on LCDC V2.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 15
keeping checkpatch happy.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 16 ++--
1 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
index 283e0a6..6118651 100644
The tilcdc has a number of limitations for the allowed sizes of
the various adjustable timing parameter. Some modes are outside
of these timings. This commit will prune modes that report timings
that will overflow the allowed sizes in the tilcdc.
Signed-off-by: Darren Etheridge
---
drivers
When hooking up to an HDMI analyzer noticed some timings were
off by one. Referring to the hardware technical reference manual
for the lcd controller some of the timing registers use 0 to
represent 1. This patch addresses that issue.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc
overflow LCD controller timing registers causing
either no monitor signal or a very corrupted display. This patchset
will stop monitor modes from being reported as valid if the lcd
controller cannot support them.
Applies cleanly on 3.10rc4.
Darren Etheridge (5):
drm/tilcdc: support pixel widths
Adding support for max-pixelclock and max-width device tree
entries. As some devices that use the tilcdc hardware module
have restrictions on the allowed/tested values. Also update DT
bindings document to reflect new parameters.
Signed-off-by: Darren Etheridge
---
.../devicetree/bindings/drm
keeping checkpatch happy.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 16 ++--
1 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
b/drivers/gpu/drm/tilcdc/tilcdc_crtc.c
index 283e0a6..6118651 100644
The tilcdc has a number of limitations for the allowed sizes of
the various adjustable timing parameter. Some modes are outside
of these timings. This commit will prune modes that report timings
that will overflow the allowed sizes in the tilcdc.
Signed-off-by: Darren Etheridge
---
drivers
When hooking up to an HDMI analyzer noticed some timings were
off by one. Referring to the hardware technical reference manual
for the lcd controller some of the timing registers use 0 to
represent 1. This patch addresses that issue.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc
Adding support for max-pixelclock and max-width device tree
entries. As some devices that use the tilcdc hardware module
have restrictions on the allowed/tested values. Also update DT
bindings document to reflect new parameters.
Signed-off-by: Darren Etheridge
---
.../devicetree/bindings/drm
TI LCD controller version 2 has an extended eleventh
bit that enables horizontal resolutions greater than
1024 pixels to be specified (upto 2048). This patch
adds support for setting this bit on LCDC V2.
Signed-off-by: Darren Etheridge
---
drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 15
overflow LCD controller timing registers causing
either no monitor signal or a very corrupted display. This patchset
will stop monitor modes from being reported as valid if the lcd
controller cannot support them.
Applies cleanly on 3.10rc4.
Darren Etheridge (5):
drm/tilcdc: support pixel widths
51 matches
Mail list logo
