From: Yakir Yang
When transmitting IEC60985 linear PCM audio, we configure the
Audio Sample Channel Status information of all the channel
status bits in the IEC60958 frame.
Refer to 60958-3 page 10 for frequency, original frequency, and
wordlength setting.
This fix the issue that audio does not
When BT.2020 Colorimetry output is used for DP, we should program BT.2020
Colorimetry to MSA and VSC SDP. It adds output_colorspace to
intel_crtc_state struct as a place holder of pipe's output colorspace.
In order to distinguish needed colorimetry for VSC SDP, it adds
intel_dp_needs_vsc_sdp
Function intel_dp_setup_hdr_metadata_infoframe_sdp handles Infoframe SDP
header and data block setup for HDR Static Metadata. It enables writing of
HDR metadata infoframe SDP to panel. Support for HDR video was introduced
in DisplayPort 1.4. It implements the CTA-861-G standard for transport of
According to Bspec, GEN11 and prior GEN11 have different register size for
HDR Metadata Infoframe SDP packet. It adds new VIDEO_DIP_GMP_DATA_SIZE for
GEN11. And it makes handle different register size for
HDMI_PACKET_TYPE_GAMUT_METADATA on hsw_dip_data_size() for each GEN
platforms. It addresses
It attaches HDR metadata property to DP connector on GLK+.
It enables HDR metadata infoframe sdp on GLK+ to be used to send
HDR metadata to DP sink.
v2: Minor style fix
Signed-off-by: Gwan-gyeong Mun
Reviewed-by: Uma Shankar
---
drivers/gpu/drm/i915/display/intel_dp.c | 5 +
1 file
It attaches the colorspace connector property to a DisplayPort connector.
Based on colorspace change, modeset will be triggered to switch to a new
colorspace.
Based on colorspace property value create a VSC SDP packet with appropriate
colorspace. This would help to enable wider color gamut like
In order to use colorspace property to Display Port connectors, it extends
DRM_MODE_CONNECTOR_DisplayPort connector_type on
drm_mode_create_colorspace_property function.
v3: Addressed review comments from Ville
- Add new colorimetry options for DP 1.4a spec.
- Separate set of colorimetry
It refactors and renames a function which handled vsc sdp header and data
block setup for supporting colorimetry format.
Function intel_dp_setup_vsc_sdp handles vsc sdp header and data block
setup for pixel encoding / colorimetry format.
In order to use colorspace information of a connector, it
Support for HDR10 video was introduced in DisplayPort 1.4.
On GLK+ platform, in order to use DisplayPort HDR10, we need to support
BT.2020 colorimetry and HDR Static metadata.
It implements the CTA-861-G standard for transport of static HDR metadata.
It enables writing of HDR metadata infoframe
On Tue, 2019-08-27 at 01:14 +0530, Shankar, Uma wrote:
> > -Original Message-
> > From: Mun, Gwan-gyeong
> > Sent: Friday, August 23, 2019 3:23 PM
> > To: intel-...@lists.freedesktop.org
> > Cc: dri-devel@lists.freedesktop.org; Shankar, Uma <
> > uma.shan...@intel.com>;
> > Sharma,
On Mon, 2019-09-02 at 17:44 +0300, Ville Syrjälä wrote:
> On Fri, Aug 23, 2019 at 12:52:29PM +0300, Gwan-gyeong Mun wrote:
> > In order to use colorspace property to Display Port connectors, it
> > extends
> > DRM_MODE_CONNECTOR_DisplayPort connector_type on
> > drm_mode_create_colorspace_property
On Mon, 2019-09-02 at 17:43 +0300, Ville Syrjälä wrote:
> On Fri, Aug 23, 2019 at 12:52:28PM +0300, Gwan-gyeong Mun wrote:
> > When BT.2020 Colorimetry output is used for DP, we should program
> > BT.2020
> > Colorimetry to MSA and VSC SDP. It adds output_colorspace to
> > intel_crtc_state struct
In order to use GCE function, we need add some informations
into display node (mboxes, mediatek,gce-client-reg, mediatek,gce-events).
Signed-off-by: Bibby Hsieh
Signed-off-by: Yongqiang Niu
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 15 +++
1 file changed, 15 insertions(+)
https://bugs.freedesktop.org/show_bug.cgi?id=111241
Timothy Arceri changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 25/08/2019 23:23, Ilia Mirkin wrote:
> You'll probably get a more detailed reply during the week, but for now
> have a look at the "link-status" property, which was made for
> precisely this situation. I think basically the idea is to ignore link
> training as part of the modeset, and just
https://bugzilla.kernel.org/show_bug.cgi?id=204725
Mike Lothian (m...@fireburn.co.uk) changed:
What|Removed |Added
CC||m...@fireburn.co.uk
From: Bartosz Golaszewski
This field is unused outside of probe(). There's no need to store it.
We can make it into a local variable.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Andy Shevchenko
Reviewed-by: Linus Walleij
Reviewed-by: Daniel Thompson
---
Laptops with AMD APU doesn't restore display backlight brightness after
system resume.
This issue started when DC was introduced.
Let's use BL_CORE_SUSPENDRESUME so the backlight core calls
update_status callback after system resume to restore the backlight
level.
Tested on Dell Inspiron 3180
This is dead code since 3.15. If their is no plan to
use it further, these can be removed forever.
Signed-off-by: Souptick Joarder
---
drivers/video/fbdev/68328fb.c | 12
1 file changed, 12 deletions(-)
diff --git a/drivers/video/fbdev/68328fb.c b/drivers/video/fbdev/68328fb.c
On Mon, Aug 12, 2019 at 09:04:44AM +0100, Lee Jones wrote:
> On Tue, 23 Jul 2019, Andy Shevchenko wrote:
>
> > Use use fwnode_property_count_uXX() directly, that makes code neater.
> >
> > Signed-off-by: Andy Shevchenko
> > ---
> > drivers/video/backlight/lm3630a_bl.c | 3 +--
> > 1 file
On Mon, 2 Sep 2019 14:46:51 +0300, Ville Syrjälä wrote:
> On Fri, Aug 30, 2019 at 06:16:52PM +0200, Jean Delvare wrote:
> > It is fine for displays without audio functionality to not implement
> > CEA extension in their EDID. Do not return an error in that case,
> > instead return 0 as if there
https://bugs.freedesktop.org/show_bug.cgi?id=111524
--- Comment #5 from Samuel Sieb ---
Created attachment 145236
--> https://bugs.freedesktop.org/attachment.cgi?id=145236=edit
dmesg with drm.debug=4
I've seen mention elsewhere about setting the drm.debug value. If you need a
different
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #46 from Dmitri Seletski (drj...@gmail.com) ---
(In reply to Mike Lothian from comment #37)
> I think you need CONFIG_FB_SIMPLE & CONFIG_FB_BOOT_VESA_SUPPORT=y configured
>
> This is what I have in my .config for a Ryzen card
>
>
Hi Robin,
On Mon, Sep 2, 2019 at 11:45 AM Robin Murphy wrote:
> Try 0036bc73ccbe - that looks like something that CONFIG_DMA_API_DEBUG
> should have been screaming about anyway.
Thanks for your suggestion.
I can successfully boot after reverting the following commits:
commit
https://bugzilla.kernel.org/show_bug.cgi?id=201497
--- Comment #10 from Daniel Andersson (engyw...@gmail.com) ---
Is this going to get fixed?
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.2.11, v4.19.69, v4.14.141, v4.9.190,
v4.4.190.
v5.2.11: Build OK!
v4.19.69:
https://bugs.freedesktop.org/show_bug.cgi?id=111077
--- Comment #22 from rol...@rptd.ch ---
Hi Marek,
This is going to be complicated. The application is not yet free to use by
others (working on getting it to release shape). I would have to figure out
first how to break this down into a
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #45 from Dmitri Seletski (drj...@gmail.com) ---
(In reply to Michel Dänzer from comment #44)
> (In reply to Dmitri Seletski from comment #39)
> > /usr/lib64/dri/swrast_dri.so failed (libLLVMAMDGPUCodeGen.so.8: cannot open
> > shared
On Mon, Sep 2, 2019 at 4:40 PM Thierry Reding wrote:
> Hm... my recollection is that command mode is only supported on "smart"
> panels that have an internal framebuffer. So the commands actually
> instruct the panel to update their internal framebuffer, which means you
> can technically switch
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #24 from Marko Popovic ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #22)
> Yes, it's possible that there are different bugs.
>
> For the citra bug: I suspect an issue with Geometry Shaders + NGG but this
> will require
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #23 from Marko Popovic ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #22)
> > Okay I just got another random hang on the desktop. even with the
> > environment variable turned on the whole time. Unfortunately it seems to
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #22 from Pierre-Eric Pelloux-Prayer
---
> Okay I just got another random hang on the desktop. even with the
> environment variable turned on the whole time. Unfortunately it seems to be
> very hardly tracable seems to be very
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #21 from Marko Popovic ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #19)
> (In reply to Marko Popovic from comment #17)
> > (In reply to Pierre-Eric Pelloux-Prayer from comment #15)
> > > (In reply to Marko Popovic from
On Mon, Sep 02, 2019 at 09:17:14AM +0200, Linus Walleij wrote:
> The video DSI mode had not really been tested. These fixes makes
> it more likely to work on real hardware:
> - Set the HS clock to something the video mode reported by the
> panel can handle rather than the max HS rate.
> - Put
On Mon, Sep 02, 2019 at 04:40:06PM +0200, Thierry Reding wrote:
> On Mon, Sep 02, 2019 at 01:44:38PM +0200, Linus Walleij wrote:
> > On Mon, Sep 2, 2019 at 11:35 AM Thierry Reding
> > wrote:
> >
> > > > + dsi-command-mode:
> > > > + type: boolean
> > > > + description:
> > > > +
On Sat, Aug 31, 2019 at 09:50:13AM +0200, Linus Walleij wrote:
> There were bugs in the DSI transfer (read and write) function
> as it was only tested with displays ever needing a single byte
> to be written. Fixed it up and tested so we can now write
> messages of up to 16 bytes and read up to 4
On Mon, 02 Sep 2019, Andy Shevchenko wrote:
> On Mon, Aug 12, 2019 at 09:04:44AM +0100, Lee Jones wrote:
> > On Tue, 23 Jul 2019, Andy Shevchenko wrote:
> >
> > > Use use fwnode_property_count_uXX() directly, that makes code neater.
> > >
> > > Signed-off-by: Andy Shevchenko
> > > ---
> > >
On 02/09/2019 14:51, Fabio Estevam wrote:
Hi,
I am getting the following crash when booting the adreno driver on
i.MX53 running a 5.3-rc6 kernel.
Such error does not happen with 5.2 though.
Before I start running a bisect, I am wondering if anyone has any
ideas about this issue.
Try
On Fri, Aug 23, 2019 at 12:52:29PM +0300, Gwan-gyeong Mun wrote:
> In order to use colorspace property to Display Port connectors, it extends
> DRM_MODE_CONNECTOR_DisplayPort connector_type on
> drm_mode_create_colorspace_property function.
>
> Signed-off-by: Gwan-gyeong Mun
> ---
>
On Fri, Aug 23, 2019 at 12:52:28PM +0300, Gwan-gyeong Mun wrote:
> When BT.2020 Colorimetry output is used for DP, we should program BT.2020
> Colorimetry to MSA and VSC SDP. It adds output_colorspace to
> intel_crtc_state struct as a place holder of pipe's output colorspace.
> In order to
Acked-by: Thomas Zimmermann
Am 02.09.19 um 14:41 schrieb Gerd Hoffmann:
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/qxl/qxl_drv.h| 1 +
> drivers/gpu/drm/qxl/qxl_object.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/qxl/qxl_drv.h
On Mon, Sep 02, 2019 at 01:44:38PM +0200, Linus Walleij wrote:
> On Mon, Sep 2, 2019 at 11:35 AM Thierry Reding
> wrote:
>
> > > + dsi-command-mode:
> > > + type: boolean
> > > + description:
> > > + If this is specified, the panel will be used in command
> > > + mode
This patch seems unrelated.
Am 02.09.19 um 14:41 schrieb Gerd Hoffmann:
> Switch qxl to use drm_gem_object_funcs callbacks
> instead of drm_driver callbacks.
>
> Signed-off-by: Gerd Hoffmann
> ---
> drivers/gpu/drm/qxl/qxl_drv.c| 8
> drivers/gpu/drm/qxl/qxl_object.c | 12
Hi
Am 02.09.19 um 14:41 schrieb Gerd Hoffmann:
> Wire up drm_mm_print() for vram helpers, using a new
> debugfs file, so one can see how vram is used:
>
># cat /sys/kernel/debug/dri/0/vram-mm
>0x-0x0300: 768: used
>0x0300-0x0600:
On Mon, Sep 02, 2019 at 02:57:25PM +0200, Linus Walleij wrote:
> On Mon, Sep 2, 2019 at 12:32 PM Thierry Reding
> wrote:
> > On Mon, Sep 02, 2019 at 11:06:33AM +0200, Linus Walleij wrote:
>
> > > + /*
> > > + * This depends on the clocking HS vs LP rate, this value
> > > + * is
Store the timestamp of the current vblank in the new field 'time' of the
vblank trace event. If the timestamp is calculated by a driver that
supports high-precision vblank timing, set the field 'high-prec' to
'true'.
User space can now access actual hardware vblank times via the tracing
Thanks for the review, Daniel. I noticed that my last name was missing
in the initial revision (my git config was messed up). I am sending v2
of this patch to fix this, including your r/b tag.
Cheers, Heinrich
___
dri-devel mailing list
Hi
Am 02.09.19 um 14:41 schrieb Gerd Hoffmann:
> Signed-off-by: Gerd Hoffmann
> ---
> include/drm/drm_gem_vram_helper.h | 1 +
> drivers/gpu/drm/drm_gem_vram_helper.c | 3 ++-
> drivers/gpu/drm/Kconfig | 1 +
> 3 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git
Hi
Acked-by: Thomas Zimmermann
But please see below.
Am 02.09.19 um 14:41 schrieb Gerd Hoffmann:
> Now with ttm_buffer_object being a subclass of drm_gem_object we can
> easily lookup ttm_buffer_object for a given drm_gem_object, which in
> turm allows to create common helper functions.
Hi,
I am getting the following crash when booting the adreno driver on
i.MX53 running a 5.3-rc6 kernel.
Such error does not happen with 5.2 though.
Before I start running a bisect, I am wondering if anyone has any
ideas about this issue.
Thanks,
Fabio Estevam
[2.083249] 8<--- cut here
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #62 from tempel.jul...@gmail.com ---
I could reproduce the issue on a system with a Radeon RX 5700 XT Navi 10 GPU +
drm-next kernel in Hitman 2. Really devastating.
--
You are receiving this mail because:
You are the assignee for
On Fri, 30 Aug 2019 14:58:21 +0200, =?UTF-8?q?Guido=20G=C3=BCnther?= wrote:
> The Northwest Logic MIPI DSI IP core can be found in NXPs i.MX8 SoCs.
>
> Signed-off-by: Guido Günther
> Tested-by: Robert Chiras
> ---
> .../bindings/display/bridge/nwl-dsi.yaml | 176 ++
> 1
On Thu, 29 Aug 2019 22:50:27 +0800, wrote:
> From: Yongqiang Niu
>
> This patch add mutex description for mt8183 display
>
> Signed-off-by: Yongqiang Niu
> ---
> Documentation/devicetree/bindings/display/mediatek/mediatek,disp.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob
On 30.08.2019 19:00, Rob Clark wrote:
> On Thu, Aug 29, 2019 at 11:52 PM Andrzej Hajda wrote:
>> On 29.08.2019 19:39, Rob Clark wrote:
>>> On Wed, Aug 28, 2019 at 11:06 PM John Stultz wrote:
Since commit 83f35bc3a852 ("drm/bridge: adv7511: Attach to DSI
host at probe time") landed in
On Mon, Sep 02, 2019 at 01:55:21PM +0200, Jean Delvare wrote:
> On Mon, 2 Sep 2019 14:46:51 +0300, Ville Syrjälä wrote:
> > On Fri, Aug 30, 2019 at 06:16:52PM +0200, Jean Delvare wrote:
> > > It is fine for displays without audio functionality to not implement
> > > CEA extension in their EDID. Do
From: Ville Syrjälä
CEA ext block revisions 1 and 2 do not contain the data block
collection. Instead that section of the extension block is
marked as reserved for 8 byte timing descriptors. Revision 3
changed it to contain the CEA data block collection instead.
Most places that iterate the
From: Ville Syrjälä
Let's make cea_db_offsets() a bit more convenient to use by
setting the start/end offsets to zero whenever the data block
collection isn't present. This makes it safe for the caller
to blindly iterate the data blocks even if there are none.
Cc: Jean Delvare
Signed-off-by:
Le ven. 23 août 2019 à 09:14, Linus Walleij a écrit :
>
> The sti_hdmi.c file include despite not even
> using any GPIOs.
>
> What it does use is devm_ioremap_nocache() which comes from
> implicitly by including that header.
>
> Fix this up by including the right header instead.
Applied on
Le jeu. 22 août 2019 à 10:11, Hans Verkuil a écrit :
>
> Adding Benjamin Gaignard.
>
> Benjamin, can you take a look at this and Ack it (or merge it if you prefer)
> and
> ideally test it as well. This is the only patch in this series that I could
> not
> test since I don't have any hardware.
On Sun, Sep 1, 2019 at 6:28 PM Rob Clark wrote:
> I'm picking up the earlier patches in this series..
Thanks a lot :)
> although I won't
> have a good way to test on devices which use the hdmi block for a few
> weeks (when I complete my move, and get back a bunch of boards that
> are in boxes
On Mon, Sep 2, 2019 at 12:32 PM Thierry Reding wrote:
> On Mon, Sep 02, 2019 at 11:06:33AM +0200, Linus Walleij wrote:
> > + /*
> > + * This depends on the clocking HS vs LP rate, this value
> > + * is calculated as:
> > + * vrefresh = (clock * 1000) / (htotal*vtotal)
> > +
Currently the HDMI driver uses always limited range RGB output. This
patch improves the behavior by using limited range only if the output is
identified as a HDMI display, and VIC > 1.
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/hdmi5_core.c | 121 ---
1
From: Jyri Sarha
Implement CTM color management property for OMAP CRTC using DSS
overlay manager's Color Phase Rotation matrix. The CPR matrix does not
exactly match the CTM property documentation. On DSS the CPR matrix is
applied after gamma table look up. However, it seems stupid to add a
Commit d49cd15550d9d4495f6187425318c245d58cb63f ("OMAPDSS: DISPC: lock
access to DISPC_CONTROL & DISPC_CONFIG") added locking to
mgr_fld_write(). This was needed in omapfb times due to lack of good
locking, especially in the case of both V4L2 and fbdev layers using the
DSS driver.
This is not
From: Jyri Sarha
Adds support for COLOR_ENCODING and COLOR_RANGE properties to
omap_plane.c and dispc.c. The supported encodings and ranges are:
For COLOR_ENCODING:
- YCbCt BT.601 (default)
- YCbCt BT.709
For COLOR_RANGE:
- YCbCt limited range
- YCbCt full range (default)
Signed-off-by: Jyri
OMAP2 and OMAP3/AM4 have limitations with the scaler:
- OMAP2 can only scale XRGB
- OMAP3/AM4 can only scale XRGB, RGB565, YUYV and UYVY
The driver doesn't check these limitations, which leads to sync-lost
floods.
This patch adds a check for the pixel formats when scaling.
From: Jyri Sarha
The core.c just for registering the drivers is kind of useless. Let's
get rid of it and register the dss drivers in dss.c.
Signed-off-by: Jyri Sarha
Signed-off-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/Makefile | 2 +-
drivers/gpu/drm/omapdrm/dss/core.c | 55
From: Alejandro Hernandez
A "HDMI I2C Master Error" is sometimes reported with the current DDC SCL
timings. The current settings for a 10us SCL period (100 KHz) causes the
error with some displays. This patch increases the SCL signal period
from 10us to 10.2us, with the new settings the error
Hi,
Misc improvements to omapdrm which have been lying around for a long
time, and I've missed upstreaming them.
And one new one, which makes the DSS5 HDMI pick up the color range
automatically.
Tomi
Alejandro Hernandez (1):
drm/omap: tweak HDMI DDC timings
Jyri Sarha (3):
drm/omap:
Now with ttm_buffer_object being a subclass of drm_gem_object we can
easily lookup ttm_buffer_object for a given drm_gem_object, which in
turm allows to create common helper functions.
This patch starts off with a drm_gem_ttm_print_info() helper function
which prints adds some ttm specific lines
Signed-off-by: Gerd Hoffmann
---
include/drm/drm_gem_vram_helper.h | 1 +
drivers/gpu/drm/drm_gem_vram_helper.c | 3 ++-
drivers/gpu/drm/Kconfig | 1 +
3 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/drm/drm_gem_vram_helper.h
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_drv.h| 1 +
drivers/gpu/drm/qxl/qxl_object.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/qxl/qxl_drv.h b/drivers/gpu/drm/qxl/qxl_drv.h
index 9e034c5fa87d..d4051409ce64 100644
---
Switch qxl to use drm_gem_object_funcs callbacks
instead of drm_driver callbacks.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/qxl/qxl_drv.c| 8
drivers/gpu/drm/qxl/qxl_object.c | 12
2 files changed, 12 insertions(+), 8 deletions(-)
diff --git
Gerd Hoffmann (5):
drm/ttm: add drm_gem_ttm_print_info()
drm/vram: use drm_gem_ttm_print_info
drm/vram: add vram-mm debugfs file
drm/qxl: use drm_gem_object_funcs callbacks
drm/qxl: use drm_gem_ttm_print_info
drivers/gpu/drm/qxl/qxl_drv.h | 1 +
Wire up drm_mm_print() for vram helpers, using a new
debugfs file, so one can see how vram is used:
# cat /sys/kernel/debug/dri/0/vram-mm
0x-0x0300: 768: used
0x0300-0x0600: 768: used
0x0600-0x0900: 768: used
pon., 2 wrz 2019 o 11:31 Lee Jones napisał(a):
>
> On Wed, 24 Jul 2019, Bartosz Golaszewski wrote:
>
> > From: Bartosz Golaszewski
> >
> > While working on my other series related to gpio-backlight[1] I noticed
> > that we could simplify the driver if we made the only user of platform
> > data
From: Bartosz Golaszewski
Add a GPIO lookup entry and a device property for GPIO backlight to the
board file. Tie them to the platform device which is now registered using
platform_device_register_full() because of the properties. These changes
are inactive now but will be used once the gpio
From: Bartosz Golaszewski
Remove the platform data fields that nobody uses.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Andy Shevchenko
Reviewed-by: Linus Walleij
Reviewed-by: Daniel Thompson
---
include/linux/platform_data/gpio_backlight.h | 3 ---
1 file changed, 3 deletions(-)
diff
From: Bartosz Golaszewski
While working on my other series related to gpio-backlight[1] I noticed
that we could simplify the driver if we made the only user of platform
data use GPIO lookups and device properties. This series tries to do
that.
The first patch adds all necessary data structures
From: Bartosz Golaszewski
Platform data fields other than fbdev are no longer used by the
backlight driver. Remove them.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Andy Shevchenko
Reviewed-by: Linus Walleij
---
arch/sh/boards/mach-ecovec24/setup.c | 3 ---
1 file changed, 3
From: Bartosz Golaszewski
Instead of dereferencing pdev each time, use a helper variable for
the associated device pointer.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Linus Walleij
Reviewed-by: Daniel Thompson
Reviewed-by: Andy Shevchenko
---
drivers/video/backlight/gpio_backlight.c |
From: Bartosz Golaszewski
Now that the last user of platform data (sh ecovec24) defines a proper
GPIO lookup and sets the 'default-on' device property, we can drop the
platform_data-specific GPIO handling and unify a big chunk of code.
The only field used from the platform data is now the fbdev
From: Bartosz Golaszewski
This field is unused. Remove it.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Andy Shevchenko
Reviewed-by: Linus Walleij
Reviewed-by: Daniel Thompson
---
drivers/video/backlight/gpio_backlight.c | 4
1 file changed, 4 deletions(-)
diff --git
On Sat, Aug 31, 2019 at 06:25:46PM +0100, Sidong Yang wrote:
> Use alpha value to blend source value and destination value Instead of
> just overwrite with source value.
>
> Signed-off-by: Sidong Yang
> ---
> drivers/gpu/drm/vkms/vkms_composer.c | 13 +++--
> 1 file changed, 11
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #20 from Marko Popovic ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #19)
> Thanks for the trace!
>
> Replaying the trace a few times is enough to reliably to reproduce the hang.
>
> Using AMD_DEBUG=nongg seems to
On 02/09/2019 12:32, Jonas Karlman wrote:
> On 2019-09-02 11:42, Neil Armstrong wrote:
>> Hi,
>>
>> On 02/09/2019 05:54, Cheng-Yi Chiang wrote:
>>> In the designware databook, the sequence of enabling audio clock and
>>> setting format is not clearly specified.
>>> Currently, audio clock is
From: kbuild test robot
drivers/misc/habanalabs/device.c:552:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Fixes: 127d20c1da61 ("habanalabs: add uapi to retrieve device utilization")
Signed-off-by: kbuild test robot
---
tree:
tree: git://people.freedesktop.org/~gabbayo/linux habanalabs-next
head: f3d40ffeb89564d31295fb01bc04929661e2bbcf
commit: 127d20c1da61045a7903c5d76afe14b3a3a097c2 [25/29] habanalabs: add uapi
to retrieve device utilization
If you fix the issue, kindly add following tag
Reported-by: kbuild
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #19 from Pierre-Eric Pelloux-Prayer
---
(In reply to Marko Popovic from comment #17)
> (In reply to Pierre-Eric Pelloux-Prayer from comment #15)
> > (In reply to Marko Popovic from comment #14)
> > >
> > > Yes, always happens at
On Fri, Aug 30, 2019 at 06:16:52PM +0200, Jean Delvare wrote:
> It is fine for displays without audio functionality to not implement
> CEA extension in their EDID. Do not return an error in that case,
> instead return 0 as if there was a CEA extension with no audio or
> speaker block.
>
> This
On Mon, Sep 2, 2019 at 11:35 AM Thierry Reding wrote:
> > + dsi-command-mode:
> > + type: boolean
> > + description:
> > + If this is specified, the panel will be used in command
> > + mode instead of video mode.
>
> I'm not sure there's concensus on this one yet. I think so
From: Thierry Reding
If the transmitter supports pre-emphasis post cursor2 the sink will
request adjustments in a similar way to how it requests adjustments to
the voltage swing and pre-emphasis settings.
Add a helper to extract these adjustments on a per-lane basis from the
DPCD link status.
From: Thierry Reding
Keeping the list sorted alphabetically makes it much easier to determine
where to add new includes.
Signed-off-by: Thierry Reding
---
include/drm/drm_dp_helper.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/drm/drm_dp_helper.h
From: Thierry Reding
Store the AUX read interval from DPCD, so that it can be used to wait
for the durations given in the specification during link training.
v2: use USEC_PER_MSEC instead of MSEC_PER_SEC for clarity
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_dp_helper.c | 3 +++
From: Thierry Reding
Make use of ANSI 8B/10B channel coding if the DisplayPort sink supports
it.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_dp_helper.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_dp_helper.c
From: Thierry Reding
The drm_dp_link structure tracks capabilities on the DP link. Add some
kerneldoc to explain what each of its fields means.
Signed-off-by: Thierry Reding
---
include/drm/drm_dp_helper.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/include/drm/drm_dp_helper.h
From: Thierry Reding
Store capabilities in max_* fields and add separate fields for the
currently selected settings.
Cc: Rob Clark
Reviewed-by: Andrzej Hajda
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/bridge/tc358767.c | 14 ++---
drivers/gpu/drm/drm_dp_helper.c|
From: Thierry Reding
Use existing parsing helpers to probe a DisplayPort link.
Reviewed-by: Philipp Zabel
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_dp_helper.c | 29 ++---
include/drm/drm_dp_helper.h | 2 ++
2 files changed, 24 insertions(+), 7
From: Thierry Reding
If the sink is eDP and supports the alternate scrambler reset, enable
it.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_dp_helper.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
index
From: Thierry Reding
Parse from the sink capabilities whether or not it supports ANSI 8B/10B
channel coding as specified in ANSI X3.230-1994, clause 11.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_dp_helper.c | 3 +++
include/drm/drm_dp_helper.h | 9 +
2 files changed,
1 - 100 of 165 matches
Mail list logo
