Hi,
On 4/7/22 20:58, Carsten Haitzler wrote:
> On Thu, 7 Apr 2022 17:38:59 +0200 Hans de Goede said:
>
> Below you covered our usual /sys/class/backlight device friends... what about
> DDC monitor controls? These function similarly but just remotely control a
> screen via I2C and also suffer fro
Hi,
On 4/8/22 17:11, Alex Deucher wrote:
> On Fri, Apr 8, 2022 at 10:56 AM Hans de Goede wrote:
>>
>> Hi,
>>
>> On 4/8/22 16:08, Alex Deucher wrote:
>>> On Fri, Apr 8, 2022 at 4:07 AM Daniel Vetter wrote:
On Thu, Apr 07, 2022 at 05:05:52PM -0400, Alex Deucher wrote:
> On Thu, Apr 7
On 11/04/2022 10:56, Thomas Hellström wrote:
Hi, Matthew
On 4/11/22 10:56, Matthew Auld wrote:
If we hit the sync case, like when skipping clearing for kernel internal
objects, or when falling back to cpu clearing, like in i915, we end up
trying to add a NULL fence, but with some recent changes
Hi, Matthew
On 4/11/22 10:56, Matthew Auld wrote:
If we hit the sync case, like when skipping clearing for kernel internal
objects, or when falling back to cpu clearing, like in i915, we end up
trying to add a NULL fence, but with some recent changes in this area
this now just results in NULL de
As drm_connector already have the display_info, instead of creating
"output_bpc" debugfs in vendor specific driver, move the logic to
the drm layer.
This patch will also move "Current" bpc to the crtc debugfs from
connector debugfs, since we are getting this info from crtc_state.
Cc: Harry Wentla
This new debugfs will expose the currently using bpc by crtc.
It is very useful for verifying whether we enter the correct
output color depth from IGT.
This patch will also add the connector's max supported bpc to
"i915_display_info" debugfs.
Example:
cat /sys/kernel/debug/dri/0/crtc-0/i915_curre
It's useful to know the connector's max supported bpc for IGT
testing. Expose it via a debugfs file on the connector "output_bpc".
Example: cat /sys/kernel/debug/dri/0/DP-1/output_bpc
V2:
* Fix typo in comments (Harry)
Cc: Jani Nikula
Cc: Ville Syrjälä
Cc: Harry Wentland
Signed-off-by: Bhanup
This series will expose the Connector's max supported bpc via connector
debugfs and Crtc's current bpc via crtc debugfs. Also move the existing
vendor specific "output_bpc" logic to drm.
Test-with: 20220411094147.1650859-2-bhanuprakash.mo...@intel.com
Bhanuprakash Modem (3):
drm/debug: Expose c
On Thu, 07 Apr 2022, Ville Syrjälä wrote:
> On Thu, Apr 07, 2022 at 12:14:26PM +0300, Jani Nikula wrote:
>> Ever so slowly moving towards cleaner EDID reading.
>>
>> Jani Nikula (12):
>> drm/edid: convert edid_is_zero() to edid_block_is_zero() for blocks
>> drm/edid: have edid_block_check() d
This series will expose the Connector's max supported bpc via connector
debugfs and Crtc's current bpc via crtc debugfs. Also move the existing
vendor specific "output_bpc" logic to drm.
Test-with: 20220411094147.1650859-2-bhanuprakash.mo...@intel.com
Bhanuprakash Modem (3):
drm/debug: Expose c
This series will expose the Connector's max supported bpc via connector
debugfs and Crtc's current bpc via crtc debugfs. Also move the existing
vendor specific "output_bpc" logic to drm.
Test-with: 20220411094147.1650859-2-bhanuprakash.mo...@intel.com
Bhanuprakash Modem (3):
drm/debug: Expose c
On Thu, 07 Apr 2022, Ville Syrjälä wrote:
> On Thu, Apr 07, 2022 at 12:14:29PM +0300, Jani Nikula wrote:
>> Split out a function to log EDID block status. The printouts get changed
>> slightly.
>>
>> Unfortunately, not all users will have struct drm_device available, so
>> we convert to pr_* debu
On Thu, 07 Apr 2022, Ville Syrjälä wrote:
> On Thu, Apr 07, 2022 at 12:14:32PM +0300, Jani Nikula wrote:
>> Make the callback a bit easier on the eye.
>>
>> Signed-off-by: Jani Nikula
>> ---
>> drivers/gpu/drm/drm_edid.c | 18 +-
>> 1 file changed, 9 insertions(+), 9 deletions(-
Add some helpers to figure out the EDID extension block count, block
count, size, pointers to blocks.
Unfortunately, we'll need to cast away the const in a few places where
we actually need to access the data.
v2: fix s/j/i/ introduced in a rebase
Signed-off-by: Jani Nikula
Reviewed-by: Ville S
This will be useful in the future. Use fail label for fail exit.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index
We don't need override as a variable for anything.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 8a050b65c06a..5a1906a
Use the EDID block read helper also for extension block reads, making
edid_block_read() the only place with the read retry logic.
Note: We observe that drm_do_get_edid() does not use invalid extension
blocks to flag the EDID as corrupt.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
Convert drm_do_get_edit() from the base block read helper to the generic
block read helper. There's quite a bit going on here, as the corrupt and
null EDID information is moved back to the caller. As we see, they were
not all that clear to begin with, and this change underlines that.
Signed-off-by
We have an abstraction for the EDID base block read, yet duplicating the
retries and error handling for extension block reads. Introduce a more
generic EDID block read helper.
Switch to the helper piecemeal, starting with drm_edid_get_panel_id(),
which doesn't need or have access to the connector
Make the callback a bit easier on the eye.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index e1afd6a55a8c..5b45
Avoid casting here and there, and make it const.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index 0b8098e34236..e
Unify debug log dumping. There's duplication in the error paths for EDID
block validity checks, but this should be neglible.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 33 +++--
1 file changed, 19 insertions(+), 14 deletion
On 11/04/2022 08:38, Arunpravin Paneer Selvam wrote:
Add a simple check to reject any size not aligned to the
min_page_size.
when size is not aligned to min_page_size, driver module
should handle in their own way either to round_up() the
size value to min_page_size or just to enable WARN_ON().
Split out a function to log EDID block status. The printouts get changed
slightly.
Unfortunately, not all users will have struct drm_device available, so
we convert to pr_* debug logging instead of drm device based logging.
v2: Complain more loudly about unknown status codes (Ville)
Signed-off-b
We have the check function, have it also detect blocks that are all zero
instead of leaving that to callers.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 19 ++-
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/
As edid_is_zero() is only ever used on EDID blocks, convert it to
edid_block_is_zero() with implicit block size.
Signed-off-by: Jani Nikula
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/drm_edid.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/dr
Submitting [1] again for CI. Just a slight change in patch 3 to address
review.
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/102329/
Jani Nikula (12):
drm/edid: convert edid_is_zero() to edid_block_is_zero() for blocks
drm/edid: have edid_block_check() detect blocks that are all z
Am Montag, dem 11.04.2022 um 00:17 +0200 schrieb Marek Vasut:
> On 4/7/22 11:47, Lucas Stach wrote:
> > Am Donnerstag, dem 07.04.2022 um 00:05 +0200 schrieb Marek Vasut:
> > > On 4/6/22 21:45, Lucas Stach wrote:
> > > > Am Freitag, dem 11.03.2022 um 18:05 +0100 schrieb Marek Vasut:
> > > > > Move m
On 11/04/2022 08:28, Arunpravin Paneer Selvam wrote:
Add a set of drm buddy test cases to validate the
drm/drm_buddy.c memory allocator.
Signed-off-by: Arunpravin Paneer Selvam
---
tests/drm_buddy.c | 14 ++
tests/meson.build | 1 +
2 files changed, 15 insertions(+)
create mo
On Sun, Apr 10, 2022 at 10:05 PM James Hilliard
wrote:
>
> On Sun, Apr 10, 2022 at 1:52 PM Patrik Jakobsson
> wrote:
> >
> > On Sun, Apr 10, 2022 at 9:40 PM James Hilliard
> > wrote:
> > >
> > > On Sun, Apr 10, 2022 at 1:36 PM Patrik Jakobsson
> > > wrote:
> > > >
> > > > On Sat, Apr 9, 2022 at
This is a note to let you know that I've just added the patch titled
drm/nouveau/pmu: Add missing callbacks for Tegra devices
to the 5.17-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
drm/amdkfd: Create file descriptor after client is added to smi_clients list
to the 5.17-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename
This is a note to let you know that I've just added the patch titled
drm/nouveau/pmu: Add missing callbacks for Tegra devices
to the 5.16-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
drm/amdkfd: Create file descriptor after client is added to smi_clients list
to the 5.16-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename
This is a note to let you know that I've just added the patch titled
drm/amdkfd: Create file descriptor after client is added to smi_clients list
to the 5.15-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename
This is a note to let you know that I've just added the patch titled
drm/nouveau/pmu: Add missing callbacks for Tegra devices
to the 5.15-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
drm/nouveau/pmu: Add missing callbacks for Tegra devices
to the 5.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
drm/amdkfd: Create file descriptor after client is added to smi_clients list
to the 5.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename
On Fri, Apr 08, 2022 at 05:54:24PM +0200, Piotr Oniszczuk wrote:
>
>
> > Wiadomość napisana przez Sascha Hauer w dniu
> > 08.04.2022, o godz. 14:00:
> >
> >> That turned out to be simpler than I thought it would be. The zpos
> >> values were never actually written to the hardware. Please try t
Il 11/04/22 04:31, xinlei@mediatek.com ha scritto:
From: Jitao Shi
To comply with the panel sequence, hold the mipi signal to LP00 before the dcs
cmds transmission,
and pull the mipi signal high from LP00 to LP11 until the start of the dcs cmds
transmission.
The normal panel timing is :
(
Il 11/04/22 04:31, xinlei@mediatek.com ha scritto:
From: Jitao Shi
In order to match the changes of "Use the drm_panel_bridge API",
the poweron/poweroff of dsi is extracted from enable/disable and
defined as new funcs (pre_enable/post_disable).
Fixes: 2dd8075d2185 ("drm/mediatek: mtk_dsi:
Il 11/04/22 04:31, xinlei@mediatek.com ha scritto:
From: Jitao Shi
Old sequence:
1. Pull the MIPI signal high
2. Delay & Dsi_reset
3. Set the dsi timing register
4. dsi clk & lanes leave ulp mode and enter hs mode
The sequence after patching is:
1. Set the dsi timing register
2. Pull the M
If we hit the sync case, like when skipping clearing for kernel internal
objects, or when falling back to cpu clearing, like in i915, we end up
trying to add a NULL fence, but with some recent changes in this area
this now just results in NULL deref in dma_resv_add_fence:
<1>[5.466383] BUG: ke
Hi All,
Fedora has received a bug report here:
https://bugzilla.redhat.com/show_bug.cgi?id=2072556
That Fedora rawhide VMs no longer boot under the VirtualBox hypervisor
after the VM has been updated to a 5.18-rc# kernel.
Switching the emulated GPU from vmwaregfx to VirtualBoxSVGA fixes
this, s
Hi Marek,
url:
https://github.com/intel-lab-lkp/linux/commits/Marek-Vasut/drm-mxsfb-Implement-LCDIF-scanout-CRC32-support/20220410-071222
base: git://anongit.freedesktop.org/drm/drm drm-next
config: i386-randconfig-m021-20220411
(https://download.01.org/0day-ci/archive/20220411
On Fri, 08 Apr 2022, Douglas Anderson wrote:
> As talked about in the kerneldoc for "struct dp_aux_ep_client" in this
> patch and also in the past in commit a1e3667a9835 ("drm/bridge:
> ti-sn65dsi86: Promote the AUX channel to its own sub-dev"), to use the
> DP AUX bus properly we really need two
This is a note to let you know that I've just added the patch titled
fbdev: Fix unregistering of framebuffers without device
to the 5.17-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
fbdev: Fix unregistering of framebuffers without device
to the 5.16-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
fbdev: Fix unregistering of framebuffers without device
to the 5.15-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
On Mon, Apr 11, 2022 at 06:40:38AM +, Dexuan Cui wrote:
> > Subject: [PATCH v3] drm/hyperv: Added error message for fb size greater than
> > allocated
> >
> > Added error message when the size of requested framebuffer is more than
> > the allocated size by vmbus mmio region for framebuffer
>
On Sun, Apr 10, 2022 at 01:31:23PM +0200, Alex Bee wrote:
> Am 08.04.22 um 13:22 schrieb Sascha Hauer:
> > The driver checks if the pixel clock of the given mode matches an entry
> > in the mpll config table. The frequencies in the mpll table are meant as
> > a frequency range up to which the entry
On 10/04/2022 12:13, Jernej Škrabec wrote:
Dne petek, 08. april 2022 ob 15:41:36 CEST je Neil Armstrong napisal(a):
On 08/04/2022 12:32, Sandor Yu wrote:
CEC interrupt status/mask and logical address registers
will be reset when device enter suspend.
It will cause cec fail to work after device
[Cc: +]
Dear Richard,
Am 11.04.22 um 02:27 schrieb Gong, Richard:
On 4/8/2022 7:19 PM, Paul Menzel wrote:
Am 08.04.22 um 21:05 schrieb Richard Gong:
Active State Power Management (ASPM) feature is enabled since kernel 5.14.
There are some AMD GFX cards (such as WX3200 and RX640) that cann
Add a simple check to reject any size not aligned to the
min_page_size.
when size is not aligned to min_page_size, driver module
should handle in their own way either to round_up() the
size value to min_page_size or just to enable WARN_ON().
If we dont handle the alignment properly, we may hit th
Dear Richard,
Thank you for your response, but please reply to your own reply next time.
Am 11.04.22 um 02:37 schrieb Gong, Richard:
On 4/8/2022 7:19 PM, Paul Menzel wrote:
Thank you for your patch.
Am 08.04.22 um 21:05 schrieb Richard Gong:
Active State Power Management (ASPM) feature is
Hi Stefan,
On Sun, Apr 10, 2022 at 02:32:02AM +0200, Stefan Wahren wrote:
> Am 09.04.22 um 21:25 schrieb Stefan Wahren:
> > Hi,
> >
> > today i tested Linux 5.18-rc1 on my Raspberry Pi 400 connected to my
> > HDMI display (multi_v7_defconfig + CONFIG_ARM_LPAE, firmware:
> > 2021-01-08T14:31:16) a
Add a set of drm buddy test cases to validate the
drm/drm_buddy.c memory allocator.
Signed-off-by: Arunpravin Paneer Selvam
---
tests/drm_buddy.c | 14 ++
tests/meson.build | 1 +
2 files changed, 15 insertions(+)
create mode 100644 tests/drm_buddy.c
diff --git a/tests/drm_buddy.c
301 - 358 of 358 matches
Mail list logo
