Hi,
Am 26.09.24 um 20:39 schrieb Armin Wolf:
Am 26.09.24 um 19:44 schrieb Werner Sembach:
The TUXEDO Sirius 16 Gen1 and TUXEDO Sirius 16 Gen2 devices have a per-key
controllable RGB keyboard backlight. The firmware API for it is implemented
via WMI.
To make the backlight userspace configurabl
This commit updates described non-existent parameters 'wave_cnt' and
'vmid', and failed to describe the existing 'queue_cnt' parameter.
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c:954: warning: Excess function
parameter 'vmid' description in 'get_wave_count'.
drivers/gpu/drm/amd/amdgpu/amdg
The ethernet-phy node in mt8395-genio-1200-evk.dts was triggering a
dtbs_check error. The error message was:
eth-phy0@1: $nodename:0: 'eth-phy0@1' does not match
'^ethernet-phy(@[a-f0-9]+)?$'
Fix this issue by replacing 'eth-phy' node to generic 'ethernet-phy'.
Fixes: f2b543a191b6
The infra-iommu node in mt8195.dtsi was triggering a CHECK_DTBS error due
to an excessively long 'interrupts' property. The error message was:
infra-iommu@10315000: interrupts: [[0, 795, 4, 0], [0, 796, 4, 0],
[0, 797, 4, 0], [0, 798, 4, 0], [0, 799, 4, 0]]
The infracfg_ao node in mt8195.dtsi was causing a dtbs_check error.
The error message was:
syscon@10001000: compatible: ['mediatek,mt8195-infracfg_ao', 'syscon',
'simple-mfd'] is too long
To resolve this, remove 'simple-mfd' from the 'compatible' property of the
infracfg_ao node.
On 27/09/2024 02:26, Dmitry Baryshkov wrote:
On Thu, Sep 26, 2024 at 02:52:35PM GMT, Tomi Valkeinen wrote:
Hi,
On 21/09/2024 23:15, Dmitry Baryshkov wrote:
On Mon, Sep 16, 2024 at 02:51:57PM GMT, Tomi Valkeinen wrote:
Hi,
We have an issue where two devices have dependencies to each other,
ac
Hi,
On Thu, Sep 26, 2024 at 4:03 PM Christian König
wrote:
>
> Am 26.09.24 um 15:52 schrieb Sumit Garg:
> > [Resend in plain text format as my earlier message was rejected by
> > some mailing lists]
> >
> > On Thu, 26 Sept 2024 at 19:17, Sumit Garg wrote:
> >> On 9/25/24 19:31, Christian König w
From: Moudy Ho
The display node in mt8195.dtsi was triggering a CHECK_DTBS error due
to an excessively long 'clocks' property:
display@14f06000: clocks: [[31, 14], [31, 43], [31, 44]] is too long
To resolve this issue, apply the limit by setting 'maxItems: 3' in MT8195
additional condition.
F
Update the documentation to specify linking to a relevant GitLab
issue or email report for each new flake entry. Added specific
GitLab issue urls for i915, msm and amdgpu driver.
Acked-by: Abhinav Kumar # msm
Acked-by: Dmitry Baryshkov # msm
Signed-off-by: Vignesh Raman
---
v2:
- Add gitlab is
>
>
>-Original Message-
>From: Dmitry Baryshkov
>Sent: Thursday, September 26, 2024 4:07 PM
>To: Hermes Wu (吳佳宏)
>Cc: Kenneth Hung (洪家倫) ; Andrzej Hajda
>; Neil Armstrong ; Robert
>Foss ; Laurent Pinchart ;
>Jonas Karlman ; Jernej Skrabec ;
>Maarten Lankhorst ; Maxime Ripard
>; Thom
>
>-Original Message-
>From: Dmitry Baryshkov
>Sent: Thursday, September 26, 2024 4:07 PM
>To: Hermes Wu (吳佳宏)
>Cc: Kenneth Hung (洪家倫) ; Andrzej Hajda
>; Neil Armstrong ; Robert
>Foss ; Laurent Pinchart ;
>Jonas Karlman ; Jernej Skrabec ;
>Maarten Lankhorst ; Maxime Ripard
>; Thomas
>-Original Message-
>From: Dmitry Baryshkov
>Sent: Thursday, September 26, 2024 8:58 PM
>To: Hermes Wu (吳佳宏)
>Cc: Kenneth Hung (洪家倫) ; Andrzej Hajda
>; Neil Armstrong ; Robert
>Foss ; Laurent Pinchart ;
>Jonas Karlman ; Jernej Skrabec ;
>Maarten Lankhorst ; Maxime Ripard
>; Thomas
On Thu, 2024-09-26 at 11:38 +0200, AngeloGioacchino Del Regno wrote:
> Il 25/09/24 16:34, Conor Dooley ha scritto:
> > On Wed, Sep 25, 2024 at 04:42:59PM +0800, Macpaul Lin wrote:
> > >
> > > On 9/25/24 00:00, Conor Dooley wrote:
> > > > On Tue, Sep 24, 2024 at 01:42:01PM +0200, AngeloGioacchino D
On Thu, Sep 26, 2024 at 02:52:35PM GMT, Tomi Valkeinen wrote:
> Hi,
>
> On 21/09/2024 23:15, Dmitry Baryshkov wrote:
> > On Mon, Sep 16, 2024 at 02:51:57PM GMT, Tomi Valkeinen wrote:
> > > Hi,
> > >
> > > We have an issue where two devices have dependencies to each other,
> > > according to drive
On Thu, Sep 26, 2024 at 03:58:11PM GMT, Maxime Ripard wrote:
> On Thu, Sep 26, 2024 at 04:32:59PM GMT, Dmitry Baryshkov wrote:
> > On Thu, Sep 26, 2024 at 08:17:09AM GMT, manikanda...@microchip.com wrote:
> > > On 23/09/24 11:37 am, Dmitry Baryshkov wrote:
> > > > EXTERNAL EMAIL: Do not click links
On Thu, Sep 26, 2024 at 04:09:03PM GMT, Alexander Stein wrote:
> Hi Dmitry,
>
> Am Donnerstag, 26. September 2024, 08:05:56 CEST schrieb Dmitry Baryshkov:
> > On Thu, Sep 26, 2024 at 07:55:51AM GMT, Alexander Stein wrote:
> > > From: Matthias Schiffer
> > >
> > > The PIXCLK needs to be enabled i
On 9/26/2024 12:06 AM, Vignesh Raman wrote:
Update the documentation to require linking to a relevant GitLab
issue for each new flake entry instead of an email report. Added
specific GitLab issue URLs for i915, xe and other drivers.
Signed-off-by: Vignesh Raman
---
v2:
- Add gitlab issue li
Use the postamble to reset perf counters when switching between rings,
except when sysprof is enabled, analogously to how they are reset
between submissions when switching pagetables.
Reviewed-by: Akhil P Oommen
Tested-by: Neil Armstrong # on SM8650-QRD
Tested-by: Neil Armstrong # on SM8550-QRD
This series implements preemption for A7XX targets, which allows the GPU to
switch to an higher priority ring when work is pushed to it, reducing latency
for high priority submissions.
This series enables L1 preemption with skip_save_restore which requires
the following userspace patches to functi
Some userspace changes are necessary so add a flag for userspace to
advertise support for preemption when creating the submitqueue.
When this flag is not set preemption will not be allowed in the middle
of the submitted IBs therefore mantaining compatibility with older
userspace.
The flag is reje
Add trace points corresponding to preemption being triggered and being
completed for latency measurement purposes.
Reviewed-by: Akhil P Oommen
Tested-by: Neil Armstrong # on SM8650-QRD
Tested-by: Neil Armstrong # on SM8550-QRD
Tested-by: Neil Armstrong # on SM8450-HDK
Signed-off-by: Antonino M
This patch implements preemption feature for A6xx targets, this allows
the GPU to switch to a higher priority ringbuffer if one is ready. A6XX
hardware as such supports multiple levels of preemption granularities,
ranging from coarse grained(ringbuffer level) to a more fine grained
such as draw-cal
Initialize with 4 rings to enable preemption.
For now only on a750 as other targets require testing.
Add the "preemption_enabled" module parameter to override this for other
a7xx targets.
Tested-by: Neil Armstrong # on SM8650-QRD
Tested-by: Neil Armstrong # on SM8550-QRD
Tested-by: Neil Armstr
Adds a field to `adreno_info` to store the GPU specific preempt record
size.
Reviewed-by: Akhil P Oommen
Tested-by: Neil Armstrong # on SM8650-QRD
Tested-by: Neil Armstrong # on SM8550-QRD
Tested-by: Neil Armstrong # on SM8450-HDK
Signed-off-by: Antonino Maniscalco
---
drivers/gpu/drm/msm/ad
Add documentation about the preemption feature supported by the msm
driver.
Signed-off-by: Antonino Maniscalco
---
Documentation/gpu/msm-preemption.rst | 99
1 file changed, 99 insertions(+)
diff --git a/Documentation/gpu/msm-preemption.rst
b/Documentation/
In mesa CP_SET_CTXSWITCH_IB is renamed to CP_SET_AMBLE and some other
names are changed to match KGSL. Import those changes.
The changes have not been merged yet in mesa but are necessary for this
series.
Tested-by: Neil Armstrong # on SM8650-QRD
Tested-by: Neil Armstrong # on SM8550-QRD
Tested
The bv_fence field of rbmemptrs was being used incorrectly as the BV
rptr shadow pointer in some places.
Add a bv_rptr field and change the code to use that instead.
Reviewed-by: Akhil P Oommen
Tested-by: Neil Armstrong # on SM8650-QRD
Tested-by: Neil Armstrong # on SM8550-QRD
Tested-by: Neil
With preemption it is not enough to track the current_ctx_seqno globally
as execution might switch between rings.
This is especially problematic when current_ctx_seqno is used to
determine whether a page table switch is necessary as it might lead to
security bugs.
Track current context per ring.
Add missing bitfields to CONTEXT_SWITCH_CNTL in a6xx.xml.
Tested-by: Neil Armstrong # on SM8650-QRD
Tested-by: Neil Armstrong # on SM8550-QRD
Tested-by: Neil Armstrong # on SM8450-HDK
Signed-off-by: Antonino Maniscalco
---
drivers/gpu/drm/msm/registers/adreno/a6xx.xml | 7 ++-
1 file chan
On Fri, 27 Sep 2024, Dave Airlie wrote:
> > > It has been more than a month since I've sent this patch set and I
> > > haven't got a clear yes or not for the same. I understand maintainers
> > > are busy people, but I'd really appreciate if I get some response for
> > > this series of patches from
Hi Dave, Simona,
Another pull request for v6.13, to keep up with the huge rate of
changes. :-)
Forgot to mention in the summary that Louis Chauvet is taking over from
Rodrigo Siqueira as vkmms maintainer, sorry about that!
Cheers,
Maarten
drm-misc-next-2024-09-26:
drm-misc-next for v6.13:
On Fri, 27 Sept 2024 at 04:03, Jiri Kosina wrote:
>
> On Thu, 26 Sep 2024, Aditya Garg wrote:
>
> > It has been more than a month since I've sent this patch set and I
> > haven't got a clear yes or not for the same. I understand maintainers
> > are busy people, but I'd really appreciate if I get s
From: Rob Clark
The CP_SMMU_TABLE_UPDATE _should_ be waiting for idle, but on some
devices (x1-85, possibly others), it seems to pass that barrier while
there are still things in the event completion FIFO waiting to be
written back to memory.
Work around that by adding a fence wait before contex
Mario and Melissa,
Another regression identified on this patch - DP Display is not listed
as an audio device after this patch is applied.
Cheers,
Alex Hung
On 9/18/24 15:38, Mario Limonciello wrote:
From: Melissa Wen
drm_edid_connector_update() updates display info, filling ELD with audio
I have an old monitor that reports a zero EDID block, which results in a
warning message. This happens on every screen save cycle, and maybe in
some other situations, and over time the whole kernel log gets filled
with these redundant messages.
Make most of these prints conditional on bad_edid_cou
On Thu, 26 Sep 2024, Aditya Garg wrote:
> It has been more than a month since I've sent this patch set and I
> haven't got a clear yes or not for the same. I understand maintainers
> are busy people, but I'd really appreciate if I get some response for
> this series of patches from the HID and
On Fri, Sep 13, 2024 at 12:51:31PM -0700, Rob Clark wrote:
> From: Rob Clark
>
> The CP_SMMU_TABLE_UPDATE _should_ be waiting for idle, but on some
> devices (x1-85, possibly others), it seems to pass that barrier while
> there are still things in the event completion FIFO waiting to be
> written
> On 26 Sep 2024, at 11:33 PM, Jiri Kosina wrote:
>
> On Thu, 26 Sep 2024, Aditya Garg wrote:
>
>> It has been more than a month since I've sent this patch set and I
>> haven't got a clear yes or not for the same. I understand maintainers
>> are busy people, but I'd really appreciate if I get
Am 26.09.24 um 19:44 schrieb Werner Sembach:
The TUXEDO Sirius 16 Gen1 and TUXEDO Sirius 16 Gen2 devices have a per-key
controllable RGB keyboard backlight. The firmware API for it is implemented
via WMI.
To make the backlight userspace configurable this driver emulates a
LampArray HID device a
On Thu, 26 Sep 2024, Aditya Garg wrote:
> >> It has been more than a month since I've sent this patch set and I
> >> haven't got a clear yes or not for the same. I understand maintainers
> >> are busy people, but I'd really appreciate if I get some response for
> >> this series of patches from the
I have an old monitor that reports a zero EDID block, which results in a
warning message. This happens on every screen save cycle, and maybe in
some other situations, and over time the whole kernel log gets filled
with these redundant messages.
Make most of these prints conditional on bad_edid_cou
Hi,
took some time but now a first working draft of the suggested new way of
handling per-key RGB keyboard backlights is finished. See:
https://lore.kernel.org/all/1fb08a74-62c7-4d0c-ba5d-648e23082...@tuxedocomputers.com/
First time for me sending a whole new driver to the LKML, so please excuse
mi
The TUXEDO Sirius 16 Gen1 and TUXEDO Sirius 16 Gen2 devices have a per-key
controllable RGB keyboard backlight. The firmware API for it is implemented
via WMI.
To make the backlight userspace configurable this driver emulates a
LampArray HID device and translates the input from hidraw to the
corre
It has been more than a month since I've sent this patch set and I haven't got
a clear yes or not for the same. I understand maintainers are busy people, but
I'd really appreciate if I get some response for this series of patches from
the HID and DRM maintainers.
Thanks
Aditya
> On 11 Sep 2024
On Thu, Sep 26, 2024 at 7:44 PM Yafang Shao wrote:
>
> In kstrdup(), it is critical to ensure that the dest string is always
> NUL-terminated. However, potential race condidtion can occur between a
condition
> writer and a reader.
>
> Consider the following scenario involving task->comm:
>
>
> > -static void edid_block_status_print(enum edid_block_status status,
> > +static void edid_block_status_print(struct drm_connector *connector,
> > + enum edid_block_status status,
> > const struct edid *block,
> >
On 9/25/24 3:51 AM, Christian König wrote:
Am 25.09.24 um 01:05 schrieb Dmitry Baryshkov:
On Tue, Sep 24, 2024 at 01:13:18PM GMT, Andrew Davis wrote:
On 9/23/24 1:33 AM, Dmitry Baryshkov wrote:
Hi,
On Fri, Aug 30, 2024 at 09:03:47AM GMT, Jens Wiklander wrote:
Hi,
This patch set is based on
Hi,
On Thu, Sep 26, 2024 at 2:29 AM Pin-yen Lin wrote:
>
> The bridge might miss the display change events when it's powered off.
> This happens when a user changes the external monitor when the system
> is suspended and the embedded controller doesn't not wake AP up.
>
> It's also observed that
On Thu, 26 Sep 2024, Andi Kleen wrote:
> I have an old monitor that reports a zero EDID block, which results in a
> warning message. This happens on every screen save cycle, and maybe in
> some other situations, and over time the whole kernel log gets filled
> with these redundant messages.
>
> Ma
On 26 September 2024 at 5:50pm, Alex Deucher wrote:
Can you attach your dmesg output? There was a regression in the dma
subsystem what was fixed by this commit:
commit b348b6d17fd1d5d89b86db602f02be
a54a754bd8
Author: Leon Romanovsky
Date: Sun Sep 22 21:09:48 2024 +0300
dma-mapping: repor
On 9/26/24 13:59, Qianqiang Liu wrote:
Break the for loop immediately upon finding the target, making the
process more efficient.
Signed-off-by: Qianqiang Liu
applied.
Thanks!
Helge
---
drivers/video/fbdev/core/fbcon.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff
On Sun, Sep 22, 2024 at 12:28 AM Christian Zigotzky
wrote:
>
> Hi All,
>
> The lastest Git kernel doesn't boot anymore after the latest DRM updates
> (drm-next-2024-09-19). [1]
>
> I tested it with an AMD Radeon HD 6970 (Cayman XT) and with an AMD
> Radeon HD 5870 (Cypress XT).
>
> I reverted the
On Thu, Sep 26, 2024 at 07:14:49PM +0800, Macpaul Lin wrote:
> Add power domain binding to the mediatek DPI controller for MT8185.
This wording is confusing, no binding is being added here, you're just
allowing one property.
> The dpi node in mt8195.dtsi was triggering a dtbs_check error:
> dp-
On Thu, Sep 26, 2024 at 07:14:46PM +0800, Macpaul Lin wrote:
> The infra-iommu node in mt8195.dtsi was triggering a CHECK_DTBS error due
> to an excessively long 'interrupts' property. The error message was:
>
> infra-iommu@10315000: interrupts: [[0, 795, 4, 0], [0, 796, 4, 0],
>
On Thu, Sep 26, 2024 at 02:29:26PM +0300, Dzmitry Sankouski wrote:
> Add binding for the Samsung s6e3ha8 panel found in the Samsung S9.
>
> Signed-off-by: Dzmitry Sankouski
>
> ---
> Changes for v5:
> - fix required properties order
> - fix example indentation
>
> Changes in v4:
> - change dts
From: Francesco Dolcini
Wait for the command transmission to be completed in the DSI transfer
function polling for the dc_start bit to go back to idle state after the
transmission is started.
This is documented in the datasheet and failures to do so lead to
commands corruption.
Fixes: ff1ca6397
On Thu, Sep 26, 2024 at 03:51:09PM +0200, Maxime Ripard wrote:
> Hi,
>
> On Thu, Sep 26, 2024 at 06:32:53AM GMT, Andi Kleen wrote:
> > I have an old monitor that reports a zero EDID block, which results in a
> > warning message. This happens on every screen save cycle, and maybe in
> > some other
Hi Dmitry,
Am Donnerstag, 26. September 2024, 08:05:56 CEST schrieb Dmitry Baryshkov:
> On Thu, Sep 26, 2024 at 07:55:51AM GMT, Alexander Stein wrote:
> > From: Matthias Schiffer
> >
> > The PIXCLK needs to be enabled in SCFG before accessing certain DCU
> > registers, or the access will hang. F
On Thu, Sep 26, 2024 at 04:59:00PM +0300, Jani Nikula wrote:
> On Thu, 26 Sep 2024, Andi Kleen wrote:
> > I have an old monitor that reports a zero EDID block, which results in a
> > warning message. This happens on every screen save cycle, and maybe in
> > some other situations, and over time the
Am 26.09.24 um 15:52 schrieb Sumit Garg:
[Resend in plain text format as my earlier message was rejected by
some mailing lists]
On Thu, 26 Sept 2024 at 19:17, Sumit Garg wrote:
On 9/25/24 19:31, Christian König wrote:
Am 25.09.24 um 14:51 schrieb Dmitry Baryshkov:
On Wed, Sep 25, 2024 at 10:
On 9/25/24 19:31, Christian König wrote:
Am 25.09.24 um 14:51 schrieb Dmitry Baryshkov:
On Wed, Sep 25, 2024 at 10:51:15AM GMT, Christian König wrote:
Am 25.09.24 um 01:05 schrieb Dmitry Baryshkov:
On Tue, Sep 24, 2024 at 01:13:18PM GMT, Andrew Davis wrote:
On 9/23/24 1:33 AM, Dmitry Baryshko
On Thu, 26 Sep 2024, Andi Kleen wrote:
> I have an old monitor that reports a zero EDID block, which results in a
> warning message. This happens on every screen save cycle, and maybe in
> some other situations, and over time the whole kernel log gets filled
> with these redundant messages. Printi
On Thu, Sep 26, 2024 at 04:32:59PM GMT, Dmitry Baryshkov wrote:
> On Thu, Sep 26, 2024 at 08:17:09AM GMT, manikanda...@microchip.com wrote:
> > On 23/09/24 11:37 am, Dmitry Baryshkov wrote:
> > > EXTERNAL EMAIL: Do not click links or open attachments unless you know
> > > the content is safe
> > >
> It may be a good opportunity to switch these over to drm_notice_once()
> instead.
I looked at it, but the callers to several levels don't have the
drm pointer that would be needed for that. It would require changing
them, and then all the drivers which call into the generic EDID code.
And even t
[Resend in plain text format as my earlier message was rejected by
some mailing lists]
On Thu, 26 Sept 2024 at 19:17, Sumit Garg wrote:
>
> On 9/25/24 19:31, Christian König wrote:
>
> Am 25.09.24 um 14:51 schrieb Dmitry Baryshkov:
>
> On Wed, Sep 25, 2024 at 10:51:15AM GMT, Christian König wrote
Hi,
On Thu, Sep 26, 2024 at 06:32:53AM GMT, Andi Kleen wrote:
> I have an old monitor that reports a zero EDID block, which results in a
> warning message. This happens on every screen save cycle, and maybe in
> some other situations, and over time the whole kernel log gets filled
> with these red
On 24/09/2024 10:12, Thomas Zimmermann wrote:
Call drm_client_setup_with_fourcc() to run the kernel's default client
setup for DRM. Set fbdev_probe in struct drm_driver, so that the client
setup can start the common fbdev client.
v5:
- select DRM_CLIENT_SELECTION
v2:
- use drm_client_setup_with_
On 26/09/2024 13:01, Mahadevan wrote:
> Document the DPU for Qualcomm SA8775P platform.
>
> Signed-off-by: Mahadevan
> ---
>
> [v2]
> - Use fake DISPCC nodes to avoid clock dependencies in dt-bindings. [Dmitry]
> - Update bindings by fixing dt_binding_check tool errors (update includes in
> exa
On 26/09/2024 09:15, Philipp Stanner wrote:
On Mon, 2024-09-23 at 15:35 +0100, Tvrtko Ursulin wrote:
Ping Christian and Philipp - reasonably happy with v2? I think it's
the
only unreviewed patch from the series.
Howdy,
sry for the delay, I had been traveling.
I have a few nits below regar
On 26/09/2024 13:01, Mahadevan wrote:
> +
> + clocks:
> +items:
> + - description: Display AHB
> + - description: Display hf AXI
> + - description: Display core
> +
> + iommus:
> +maxItems: 1
> +
> + interconnects:
> +maxItems: 3
> +
> + interconnect-names:
> +max
On 24/09/2024 10:12, Thomas Zimmermann wrote:
Call drm_client_setup_with_color_mode() to run the kernel's default
client setup for DRM. Set fbdev_probe in struct drm_driver, so that
the client setup can start the common fbdev client.
v5:
- select DRM_CLIENT_SELECTION
v3:
- add DRM_FBDEV_DMA_DRIV
On 9/26/24 09:32, Andi Kleen wrote:
I have an old monitor that reports a zero EDID block, which results in a
warning message. This happens on every screen save cycle, and maybe in
some other situations, and over time the whole kernel log gets filled
with these redundant messages. Printing it only
On Thu, Sep 26, 2024 at 08:17:09AM GMT, manikanda...@microchip.com wrote:
> On 23/09/24 11:37 am, Dmitry Baryshkov wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> > content is safe
> >
> > On Mon, Sep 23, 2024 at 05:50:22AM GMT, manikanda...@microchip.com w
I have an old monitor that reports a zero EDID block, which results in a
warning message. This happens on every screen save cycle, and maybe in
some other situations, and over time the whole kernel log gets filled
with these redundant messages. Printing it only once should be
sufficient.
Mark all
On Thu, Sep 26, 2024 at 04:31:33PM +0530, Mahadevan wrote:
> Document the MDSS hardware found on the Qualcomm SA8775P platform.
>
> Signed-off-by: Mahadevan
> ---
>
> [v2]
> - Use fake DISPCC nodes to avoid clock dependencies in dt-bindings. [Dmitry]
> - Update bindings by fixing dt_binding_chec
On Thu, Sep 26, 2024 at 08:56:29AM GMT, Marco Rodolfi wrote:
> Orientation quirk code take panel resolution into account when
> determining panel orientation. Add orientation configuration for the
> popular aftermarket DeckHD panel, which resolution (1200x1920) differs
> from the standard panel (80
On Thu, Sep 26, 2024 at 09:01:06AM GMT, Marco Rodolfi wrote:
> Orientation quirk code take panel resolution into account when
> determining panel orientation. Add orientation configuration for the
> popular aftermarket DeckHD panel, which resolution (1200x1920) differs
> from the standard panel (80
On Thu, Sep 26, 2024 at 04:31:37PM GMT, Mahadevan wrote:
> Add mdss0 and mdp devicetree nodes for sa8775p target.
>
> Signed-off-by: Mahadevan
>
> ---
>
> This patch depends on the clock enablement change:
> https://lore.kernel.org/all/20240816-sa8775p-mm-v3-v1-0-77d53c3c0...@quicinc.com/
>
>
On Tue, Sep 24, 2024 at 05:57:07PM GMT, Vignesh Raman wrote:
> Hi,
>
> On 12/09/24 11:18, Dmitry Baryshkov wrote:
> > On Mon, Sep 09, 2024 at 07:34:04AM GMT, Rob Clark wrote:
> > > On Mon, Sep 9, 2024 at 2:54 AM Dmitry Baryshkov
> > > wrote:
> > > >
> > > > On Mon, 9 Sept 2024 at 10:50, Maxime R
On Thu, Sep 26, 2024 at 04:31:36PM GMT, Mahadevan wrote:
> Add definitions for the display hardware used on the
> Qualcomm SA8775P platform.
>
> Signed-off-by: Mahadevan
> ---
Reviewed-by: Dmitry Baryshkov
Minor nit below.
> [v2]
> - Reorder compatible string of DPU based on alphabetical orde
On 24/09/2024 10:13, Thomas Zimmermann wrote:
Rework fbdev probing to support fbdev_probe in struct drm_driver
and remove the old fb_probe callback. Provide an initializer macro
for struct drm_driver that sets the callback according to the kernel
configuration.
Call drm_client_setup() to run the
Hi,
On 24/09/2024 10:13, Thomas Zimmermann wrote:
Store instances of drm_fb_helper and struct omap_fbdev separately.
This will allow omapdrm to use the common fbdev client, which allocates
its own instance of struct drm_fb_helper.
There is at most one instance of each per DRM device, so both ca
On Thu, Sep 26, 2024 at 04:31:35PM GMT, Mahadevan wrote:
> Add Mobile Display Subsystem (MDSS) support for the SA8775P platform.
>
> Signed-off-by: Mahadevan
> ---
>
> [v2]
> - Update commit message. [Dmitry]
> - Reorder compatible string of MDSS based on alphabetical order. [Dmitry]
> - add reg
On Thu, 26 Sep 2024 16:31:33 +0530, Mahadevan wrote:
> Document the MDSS hardware found on the Qualcomm SA8775P platform.
>
> Signed-off-by: Mahadevan
> ---
>
> [v2]
> - Use fake DISPCC nodes to avoid clock dependencies in dt-bindings. [Dmitry]
> - Update bindings by fixing dt_binding_check to
On Thu, 26 Sep 2024 16:31:34 +0530, Mahadevan wrote:
> Document the DPU for Qualcomm SA8775P platform.
>
> Signed-off-by: Mahadevan
> ---
>
> [v2]
> - Use fake DISPCC nodes to avoid clock dependencies in dt-bindings. [Dmitry]
> - Update bindings by fixing dt_binding_check tool errors (update i
On Thu, Sep 26, 2024 at 04:31:34PM GMT, Mahadevan wrote:
> Document the DPU for Qualcomm SA8775P platform.
>
> Signed-off-by: Mahadevan
> ---
>
> [v2]
> - Use fake DISPCC nodes to avoid clock dependencies in dt-bindings. [Dmitry]
> - Update bindings by fixing dt_binding_check tool errors (update
On Thu, Sep 26, 2024 at 04:31:33PM GMT, Mahadevan wrote:
> Document the MDSS hardware found on the Qualcomm SA8775P platform.
>
> Signed-off-by: Mahadevan
> ---
>
> [v2]
> - Use fake DISPCC nodes to avoid clock dependencies in dt-bindings. [Dmitry]
> - Update bindings by fixing dt_binding_check
On Thu, Sep 26, 2024 at 03:51:34PM GMT, Hermes Wu wrote:
> From: Hermes Wu
>
> Add aux-i2c operaction in order to support the MCCS function.
Brevity is the soul of wit. However in the commit message we appreciate
more details. Is it enough to get monitor control to work? Or is there
anything lef
On Thu, Sep 26, 2024 at 04:55:02PM GMT, Mahadevan P wrote:
> Sorry, Please ignore this thread/coverletter
>
go/upstream and adopt b4, please.
On Thu, 26 Sept 2024 at 11:46, wrote:
>
> >On Thu, Sep 26, 2024 at 03:47:53PM GMT, Hermes Wu wrote:
> >> From: Hermes Wu
> >>
> >> Add aux operaction command which supports read DPCD KSV FIFO with aux
> >> fifo.
> >
> >Nit: AUX, FIFO. Please be consistent in your commit messages.
> >
> >>
> >>
>
Break the for loop immediately upon finding the target, making the
process more efficient.
Signed-off-by: Qianqiang Liu
---
drivers/video/fbdev/core/fbcon.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/video/fbdev/core/fbcon.c b/drivers/video/fbdev/core/fbc
On 24/09/2024 10:12, Thomas Zimmermann wrote:
Call drm_client_setup() to run the kernel's default client setup
for DRM. Set fbdev_probe in struct drm_driver, so that the client
setup can start the common fbdev client.
The tidss driver specifies a preferred color mode of 32. As this
is the defaul
Hi Dave, Sima,
this is the PR for drm-misc-fixes for this week. Mostly the usual small
changes. That fix in the atomic-modesetting code touches UAPI code, but
does not change the UAPI itself.
Best regards
Thomas
drm-misc-fixes-2024-09-26:
Short summary of fixes pull:
atomic:
- Use correct type
Add binding for the Samsung s6e3ha8 panel found in the Samsung S9.
Signed-off-by: Dzmitry Sankouski
---
Changes for v5:
- fix required properties order
- fix example indentation
Changes in v4:
- change dts example intendation from tabs
to spaces
- remove reset-gpios description
---
Documentat
Hi,
On 21/09/2024 23:15, Dmitry Baryshkov wrote:
On Mon, Sep 16, 2024 at 02:51:57PM GMT, Tomi Valkeinen wrote:
Hi,
We have an issue where two devices have dependencies to each other,
according to drivers/base/core.c's fw_devlinks, and this prevents them from
probing. I've been adding debugging
Il 26/09/24 09:50, Hermes Wu ha scritto:
From: Hermes Wu
When running the HDCP CTS test on UNIGRAF DPR-100.
KSV list must be read from DPCD with 5 byte boundary.
The original aux operation using AUX_NATIVE_READ can not read back the
KSV list correctly.
Change to CMD_AUX_GET_KSV_LIST operaction
Add support for MIPI-DSI based S6E3HA8 AMOLED panel
driver. This panel has 1440x2960 resolution, 5.8-inch physical
size, and can be found in starqltechn device.
Brightness regulation is not yet supported.
Signed-off-by: Dzmitry Sankouski
---
Changes for v5:
- return ctx.accum_err instead of 0 wh
On Wed, Sep 25, 2024 at 07:25:34PM -0500, Benjamin Hoefs wrote:
> Hello,
>
> I am using a Dell WD19TB dock with a 3440x1440 monitor. Using it at
> 100Hz used to work but recently I tried it again and discovered it no longer
> did, specifically the modeset seems to silently fail with no error messa
The s6e3ha8 is a 1440x2960 DPI AMOLED display panel from Samsung Mobile
Displays (SMD)
Signed-off-by: Dzmitry Sankouski
---
Changes in v5:
- Split patchset per subsystem
- Link to v4:
https://lore.kernel.org/r/20240913-starqltechn_integration_upstream-v4-0-2d2efd5c5...@gmail.com
---
Dzmitry S
1 - 100 of 186 matches
Mail list logo
