The flip properties were used by "samsung,s6e8aa0.yaml" only so far. By
introducing "samsung,s6e88a0-ams427ap24.yaml" they become more common.
Signed-off-by: Jakob Hauser
Reviewed-by: Krzysztof Kozlowski
---
Patch is based on current branch drm-misc-next.
---
.../bindings/display/panel/panel-co
fwnode needs to be set for a device for fw_devlink to be able to
track/enforce its dependencies correctly. Without this, you'll see error
messages like this when the supplier has probed and tries to make sure
all its fwnode consumers are linked to it using device links:
mediatek-drm-dp 1c50.ed
On Wed, Oct 23, 2024 at 12:56 PM Nícolas F. R. A. Prado
wrote:
>
> On Wed, Oct 23, 2024 at 12:13:36PM -0700, Saravana Kannan wrote:
> > fwnode needs to be set for a device for fw_devlink to be able to
> > track/enforce its dependencies correctly. Without this, you'll see error
> > messages like th
It would make it easier to debugs issues similar to the ones
reported[1][2] recently where some devices didn't have the fwnode set.
[1] -
https://lore.kernel.org/all/7b995947-4540-4b17-872e-e107adca4598@notapiano/
[2] - https://lore.kernel.org/all/20240910130019.35081-1-jonath...@nvidia.com/
Sig
Probably easiest for Greg to pull in these changes?
PSA: Do not pull any of these patches into stable kernels. fw_devlink
had a lot of changes that landed in the last year. It's hard to ensure
cherry-picks have picked up all the dependencies correctly. If any of
these really need to get cherry-pic
Hi Dave & Sima,
Here goes drm-intel-fixes towards v6.12-rc5.
Just one Kconfig fix for GVT.
Regards, Joonas
***
drm-intel-fixes-2024-10-24:
- Fix DRM_I915_GVT_KVMGT dependencies in Kconfig
The following changes since commit 42f7652d3eb527d03665b09edac47f85fb600924:
Linux 6.12-rc4 (2024-10-
Hi Bjorn,
> Subject: Re: [PATCH v2 1/5] PCI/P2PDMA: Don't enforce ACS check for
> functions of same device
>
> On Sun, Oct 20, 2024 at 10:21:29PM -0700, Vivek Kasireddy wrote:
> > Functions of the same PCI device (such as a PF and a VF) share the
> > same bus and have a common root port and typic
On Thu, 24 Oct 2024 01:50:34 + Matthew Brost
wrote:
> > On Wed, 23 Oct 2024 16:39:44 -0700 Matthew Brost
> > wrote:
> >
> > > Implement migrate_device_pfns to prepare an array of PFNs for migration.
> > > Handles non-contiguous ranges of device pages that require migration.
> >
> > OK, t
Hi Logan,
> Subject: Re: [PATCH v2 1/5] PCI/P2PDMA: Don't enforce ACS check for
> functions of same device
>
>
>
> On 2024-10-22 09:16, Bjorn Helgaas wrote:
> > On Sun, Oct 20, 2024 at 10:21:29PM -0700, Vivek Kasireddy wrote:
> >> Functions of the same PCI device (such as a PF and a VF) share t
Hi Dmitry,
> Subject: Re: [PATCH v2 2/5] drm/virtio: Add a helper to map and note the
> dma addrs and lengths
>
> On 10/22/24 07:51, Kasireddy, Vivek wrote:
> > Hi Dmitry,
> >
> >>
> >> On 8/13/24 06:49, Vivek Kasireddy wrote:
> >>> +long virtgpu_dma_buf_import_sgt(struct virtio_gpu_mem_entry
> *
> -Original Message-
> From: dri-devel On Behalf Of
> Arun R Murthy
> Sent: Wednesday, September 25, 2024 8:38 PM
> To: intel...@lists.freedesktop.org; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org
> Cc: Murthy, Arun R
> Subject: [PATCHv4 4/7] drm/i915/histogram:
> -Original Message-
> From: dri-devel On Behalf Of
> Arun R Murthy
> Sent: Wednesday, September 25, 2024 8:38 PM
> To: intel...@lists.freedesktop.org; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org
> Cc: Murthy, Arun R
> Subject: [PATCHv2 2/7] drm/i915/histogram: A
> -Original Message-
> From: dri-devel On Behalf Of
> Arun R Murthy
> Sent: Wednesday, September 25, 2024 8:38 PM
> To: intel...@lists.freedesktop.org; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org
> Cc: Murthy, Arun R
> Subject: [PATCHv2 2/7] drm/i915/histogram: A
Add bindings for Samsung AMS427AP24 panel with S6E88A0 controller.
Signed-off-by: Jakob Hauser
Reviewed-by: Krzysztof Kozlowski
---
Patch is based on current branch drm-misc-next.
Changes in v3:
- Dropped the second "bindings" in the commit subject.
- Applied 4 spaces indentation in the examp
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Reviewed-by: Tomi Valkeinen
Acked-by: Sakari Ailus
---
drivers/media/platform/xilinx/xilinx-tpg.c | 14 +++---
1 file changed, 3 insertions(+), 11 deletions(-)
diff --git a/drivers/med
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Acked-by: Helge Deller
---
drivers/video/fbdev/omap2/omapfb/dss/dpi.c| 3 +-
drivers/video/fbdev/omap2/omapfb/dss/dss-of.c | 66 ---
drivers/video/fbdev/omap2/omapfb/dss/dss
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Reviewed-by: Tomi Valkeinen
Acked-by: Helge Deller
---
drivers/gpu/drm/omapdrm/dss/dpi.c | 3 ++-
drivers/gpu/drm/omapdrm/dss/sdi.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
di
We already have of_graph_get_next_endpoint(), but it is not
intuitive to use in some case.
(X) node {
(Y) ports {
(P0)port@0 { endpoint { remote-endpoint = ...; };};
(P10) port@1 { endpoint { remote-endpoint = ...; };
(P11)
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Acked-by: Mark Brown
---
sound/soc/generic/audio-graph-card.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/generic/audio-graph-card.c
b/sound/soc/generic/audio-
Current test-component.c is using for_each_endpoint_of_node()
for parsing "port", because there was no "port" base loop before.
It has been assuming 1 port has 1 endpoint here.
But now we can use "port" base loop (= for_each_of_graph_port()).
Let's replace for_each function from "endpoint" base to
Current of_graph_get_next_endpoint() can be replaced by using
new of_graph_get_next_port().
Signed-off-by: Kuninori Morimoto
---
drivers/of/property.c | 18 +-
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git a/drivers/of/property.c b/drivers/of/property.c
index fcc60
Hi Rob, Saravana, Tomi, Laurent, Sakari, Mark
This is v8 patch-set
Current Of-graph has "endpoint base" for loop, but doesn't have
"port base" loop. "endpoint base" loop only is not enough.
This patch-set add new "port base" for loop, and use it.
v7 -> v8
- add Acked-by from Sakari/Hel
We have endpoint base functions
- of_graph_get_next_endpoint()
- of_graph_get_endpoint_count()
- for_each_endpoint_of_node()
Here, for_each_endpoint_of_node() loop finds each endpoints
ports {
port@0 {
(1) endpoint {...};
On Wed, Oct 23, 2024 at 06:22:17PM -0700, Andrew Morton wrote:
> On Wed, 23 Oct 2024 16:39:43 -0700 Matthew Brost
> wrote:
>
> > Part of series [1]. Sending as individual patch ahead of that series as
> > this is a prerequisite for merging.
>
> That's news to me - singleton patches are perfectl
On Mon, Oct 21, 2024 at 9:30 AM Maxime Ripard wrote:
>
> Hi TJ,
>
> Thanks for your review
>
> On Tue, Oct 01, 2024 at 11:03:41PM +0200, T.J. Mercier wrote:
> > On Mon, Sep 30, 2024 at 4:41 PM Maxime Ripard wrote:
> > >
> > > Following a recent discussion at last Plumbers, John Stultz, Sumit
> >
drm_gpu_scheduler.submit_wq is used to submit jobs, jobs are in the path
of dma-fences, and dma-fences are in the path of reclaim. Mark scheduler
work queue with WQ_MEM_RECLAIM to ensure forward progress during
reclaim; without WQ_MEM_RECLAIM, work queues cannot make forward
progress during reclaim
From: Maxime Ripard
The TXP data structure has a name too generic for the multiple variants
we'll have to support. Let's rename it to mention the SoC it applies to.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/tests/vc4_mock.c | 4 ++--
drivers/gpu/drm/vc
There are a few minor changes in the display list generation
for the D-step of the chip, so add them.
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_plane.c | 72 ++---
drivers/gpu/drm/vc4/vc4_regs.h | 9 --
2 files changed, 60 insertions(+),
Hi Krzysztof,
On 23.10.24 09:15, Krzysztof Kozlowski wrote:
On Tue, Oct 22, 2024 at 11:33:35PM +0200, Jakob Hauser wrote:
The flip properties were used by "samsung,s6e8aa0.yaml" only so far. By
introducing "samsung,s6e88a0-ams427ap24.yaml" they become more common.
Signed-off-by: Jakob Hauser
Hi
Am 22.10.24 um 21:15 schrieb Pavel Machek:
Hi!
- interface for setting multiple LEDs at once
- interface for setting a range of LEDs at once
How are LEDs ordered? I don't believe range makes much sense.
Range would allow for efficiently changing the color of all LEDs. But i agree
that thi
Implement migrate_device_pfns to prepare an array of PFNs for migration.
Handles non-contiguous ranges of device pages that require migration.
v2:
- s/migrate_device_vma_range/migrate_device_prepopulated_range
- Drop extra mmu invalidation (Vetter)
v3:
- s/migrate_device_prepopulated_range/migr
Part of series [1]. Sending as individual patch ahead of that series as
this is a prerequisite for merging.
Matt
[1] https://patchwork.freedesktop.org/series/137870/
Matthew Brost (1):
mm/migrate: Add migrate_device_pfns
include/linux/migrate.h | 1 +
mm/migrate_device.c | 52 ++
Hi Sakari
> > > > + * Parent device node can be used as @parent whether device node has
> > > > ports node or not.
> > >
> > > This line should be wrapped, no reason to have it longer than 80 chars.
> >
> > We can use 100 char now on upstream ?
> >
> > commit bdc48fa11e46f867ea4d75fa59ee
On Tue, Oct 22, 2024 at 12:18:52PM +0300, Mika Kuoppala wrote:
> Matthew Brost writes:
>
> > Non-contiguous VRAM cannot easily be mapped in TTM nor can non-visible
> > VRAM easily be accessed. Add ttm_bo_access, which is similar to
> > ttm_bo_vm_access, to access such memory.
> >
> > v4:
> > - F
From: Maxime Ripard
The BCM2712 MOP and MOPLET can handle addresses larger than 32bits
through an extra register. We can easily support it and make it
conditional based on the compatible through a boolean in our variant
structure.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
On 23/10/2024 17:36, Mohamed, Zaeem wrote:
[AMD Official Use Only - AMD Internal Distribution Only]
Hi,
A patch addressing this will be sent out soon.
Great! Thanks for the heads up!
Melissa
Thanks,
Zaeem
-Original Message-
From: Melissa Wen
Sent: Tuesday, October 22, 2024 11:
The LXD M9189A panel is based on the EK79007AD3 DSI display controller.
It currently supports only 4 lane operation.
Signed-off-by: Rouven Czerwinski
---
MAINTAINERS | 6 +
drivers/gpu/drm/panel/Kconfig| 9 +
drivers/gpu/drm/panel/Makefile |
The LXD M9189A is a 1024x600 MIPI-DSI panel.
Signed-off-by: Rouven Czerwinski
---
.../bindings/display/panel/lxd,m9189a.yaml| 64 +++
1 file changed, 64 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/panel/lxd,m9189a.yaml
diff --git a/Documentat
Hi,
On Wed, 2024-10-23 at 14:44 +0200, Rouven Czerwinski wrote:
> The LXD M9189A is a 1024x600 MIPI-DSI panel.
>
> Signed-off-by: Rouven Czerwinski
> ---
> .../bindings/display/panel/lxd,m9189a.yaml | 64
> +++
> 1 file changed, 64 insertions(+)
> create mode 100644
> Documen
[AMD Official Use Only - AMD Internal Distribution Only]
Hi,
A patch addressing this will be sent out soon.
Thanks,
Zaeem
-Original Message-
From: Melissa Wen
Sent: Tuesday, October 22, 2024 11:58 AM
To: Mohamed, Zaeem ; Wentland, Harry
; Li, Sun peng (Leo) ; Siqueira,
Rodrigo ; Deuc
On Wed, Oct 23, 2024 at 12:13:36PM -0700, Saravana Kannan wrote:
> fwnode needs to be set for a device for fw_devlink to be able to
> track/enforce its dependencies correctly. Without this, you'll see error
> messages like this when the supplier has probed and tries to make sure
> all its fwnode co
On 10/21/2024 3:01 PM, Konrad Dybcio wrote:
> On 21.10.2024 11:25 AM, Akhil P Oommen wrote:
>> On Sat, Oct 19, 2024 at 04:14:13PM +0300, Dmitry Baryshkov wrote:
>>> On Sat, Oct 19, 2024 at 03:01:46PM +0530, Akhil P Oommen wrote:
On Fri, Oct 18, 2024 at 03:11:38PM +, Arnd Bergmann wrote:
>>
Hello,
On Wed, Oct 23, 2024 at 09:52:53AM +0200, Maarten Lankhorst wrote:
> New submission!
> I've added documentation for each call, and integrated the renaming from
> drm cgroup to dev cgroup, based on maxime ripard's work.
>
> Maxime has been testing this with dma-buf heaps and v4l2 too, and i
On 10/22/2024 11:19 AM, Krzysztof Kozlowski wrote:
> On Mon, Oct 21, 2024 at 05:23:43PM +0530, Akhil P Oommen wrote:
>> Add a new schema which extends opp-v2 to support a new vendor specific
>> property required for Adreno GPUs found in Qualcomm's SoCs. The new
>> property called "qcom,opp-acd-leve
Hi,
Am 22.10.24 um 17:02 schrieb Armin Wolf:
Am 22.10.24 um 11:37 schrieb Pavel Machek:
Hi!
Personally I really like the idea to just emulate a HID LampArray device
for this instead or rolling our own API. I believe there need to be
strong arguments to go with some alternative NIH API and I
From: Maxime Ripard
The RaspberryPi firmware clocks driver uses in several instances a
container_of to retrieve the struct raspberrypi_clk_data from a pointer
to struct clk_hw. Let's create a small function to avoid duplicating it
all over the place.
Signed-off-by: Maxime Ripard
Signed-off-by:
fwnode needs to be set for a device for fw_devlink to be able to
track/enforce its dependencies correctly. Without this, you'll see error
messages like this when the supplier has probed and tries to make sure
all its fwnode consumers are linked to it using device links:
mediatek-drm-dp 1c50.ed
Hi Dave, Simona,
Fixes for 6.12.
The following changes since commit 42f7652d3eb527d03665b09edac47f85fb600924:
Linux 6.12-rc4 (2024-10-20 15:19:38 -0700)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git
tags/amd-drm-fixes-6.12-2024-10-23
for you to fe
Hi!
> > > > > Personally I really like the idea to just emulate a HID LampArray
> > > > > device
> > > > > for this instead or rolling our own API. I believe there need to be
> > > > > strong arguments to go with some alternative NIH API and I have not
> > > > > heard such arguments yet.
> > > >
Am 22.10.24 um 11:05 schrieb Benjamin Tissoires:
Sorry I should have answered earlier...
On Oct 09 2024, Werner Sembach wrote:
Resend because HTML mail ..., but I think I now know when Thunderbird does
it: Every time I include a link it gets converted.
Hi
Am 08.10.24 um 17:21 schrieb Benjam
From: Maxime Ripard
We'll have multiple TXP instances in the BCM2712, so we can't use a
single encoder type anymore. Let's tie the encoder type to the
compatible.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_drv.h | 1 +
drivers/gpu/drm/vc4/vc4_txp.c
From: Maxime Ripard
The HDMI controllers found in the BCM2712 are largely the ones found in
the BCM2711 with a different PHY.
There's some difference with how timings are split between registers,
and HDMI1 is now able to run at 4k/60Hz.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenso
From: Maxime Ripard
Starting with BCM2712, we'll have a two TXP. Let's follow the HDMI
example and add two encoder types for TXP: TXP0 and TXP1.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/tests/vc4_mock.c | 4 +-
drivers/gpu/drm/vc4/tests/vc
It is permitted for a plane to be configured such that none
of it is on-screen via either negative dest rectangle X,Y
offset, or an offset that is greater than the crtc dimensions.
These planes were resized via drm_atomic_helper_check_plane_state
such that the source rectangle had a zero width or
This series adds the required DRM, clock, and DT changes
required to support the display hardware on Pi5.
There are a couple of minor fixes first before the main patches.
Many of the patches were authored by Maxime whilst working
for us, however there have been a number of fixes squashed
into his
From: Maxime Ripard
The HVS found in the BCM2712, while having a similar role, is very
different from the one found in the previous SoCs. Indeed, the register
layout is fairly different, and the DLIST format is new as well.
Let's introduce the needed functions to support the new HVS.
This commi
Pi 0-3 have no deep colour support and only 24bpp output,
so max_bpc should remain as 8, and no HDR metadata property
should be registered.
Fixes: ba8c0faebbb0 ("drm/vc4: hdmi: Enable 10/12 bpc output")
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_hdmi.c | 5 +
1 file changed, 5
From: Maxime Ripard
The BCM2712 has an evolution of what used to be called TXP in the
earlier SoCs, but is now called MOP.
There's a few differences still, so we can add a new compatible to deal
with them easily.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/
The default was to have enable_bg_fill disabled and the first
plane set it if it wasn't opaque and covering the whole screen.
However that meant that if no planes were enabled, then the
background fill wasn't enabled, and would give a striped
output from the uninitialised output buffer.
Initialise
BCM2712 still uses the firmware clocks and power drivers, so add
them to the base device tree.
Signed-off-by: Dave Stevenson
---
arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts | 28
1 file changed, 28 insertions(+)
diff --git a/arch/arm64/boot/dts/broadcom/bcm2712-rpi
From: Maxime Ripard
BCM2712 has an extra clock exposed by the firmware called DISP, and used
by (at least) the HVS. Let's add it to the list of clocks to register in
Linux.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/clk/bcm/clk-raspberrypi.c | 5 +
inc
From: Maxime Ripard
Some code path in vc4 are conditional to a generation and cannot be
executed on others. Let's put a WARN_ON if that ever happens.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_hvs.c | 30 --
drivers/gpu
Adds the HVS and associated hardware blocks to support the HDMI
and writeback connectors on BCM2712 / Pi5.
Signed-off-by: Dave Stevenson
---
arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts | 14 ++
arch/arm64/boot/dts/broadcom/bcm2712.dtsi| 188 +++
2 files changed,
From: Maxime Ripard
The MOPLET doesn't have the BYTE_ENABLE field to set, but the TXP and
MOP do, so let's add a boolean to control whether or not we need to set
it.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_drv.h | 1 +
drivers/gpu/drm/vc4/vc4_txp
From: Dom Cobley
The ISP clock can be controlled by the driver, so register it
with the clock subsystem.
Signed-off-by: Dom Cobley
Signed-off-by: Dave Stevenson
---
drivers/clk/bcm/clk-raspberrypi.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/clk/bcm/clk-raspberrypi.c
b/dr
The D-Step has some minor variations in the hardware, so needs
matching changes to DT.
Add a new DTS file that modifies the existing (C-step) devicetree.
Signed-off-by: Dave Stevenson
---
arch/arm64/boot/dts/broadcom/Makefile | 1 +
arch/arm64/boot/dts/broadcom/bcm2712-d-rpi-5-b.d
From: Dom Cobley
There isn't a reason not to minimise the clocks, and it saves
some power.
Signed-off-by: Dom Cobley
Signed-off-by: Dave Stevenson
---
drivers/clk/bcm/clk-raspberrypi.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/clk/bcm/clk-raspberrypi.c
b/drivers/clk/b
The D-step has increased FIFO sizes of the MAI_THR blocks,
resulting in changes to the register masking. Add support for
it.
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_hdmi.c | 19 +--
drivers/gpu/drm/vc4/vc4_regs.h | 9 +
2 files changed, 26 insertions(+)
THe registers have been moved around, and a couple of minor changes
made, so adapt for this.
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_drv.h | 6 ++
drivers/gpu/drm/vc4/vc4_hvs.c | 154 +
drivers/gpu/drm/vc4/vc4_kms.c | 3 +-
drivers
From: Maxime Ripard
The new writeback controllers that can be found on the BCM2712 require
to have their horizontal and vertical size reduced by one.
Let's tie that behaviour to the compatible so we can support both the
new and old controllers.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave
From: Maxime Ripard
The BCM2712 will have several TXP with small differences. Let's add a
structure tied to the compatible to deal with those differences.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/tests/vc4_mock.c | 4 ++--
drivers/gpu/drm/vc4/vc4_drv
From: Maxime Ripard
The BCM2712 features a simpler TXP called MOPLET. Let's add support for
it.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_txp.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_txp.c b/driv
From: Maxime Ripard
The BCM2712 has a MOPLET controller which is basically a TXP without the
transpose feature.
Express that by adding a new compatible for it.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
Documentation/devicetree/bindings/display/brcm,bcm2835-txp.yaml | 1 +
From: Maxime Ripard
The PixelValves found on the BCM2712 are similar to the ones found in
the previous generation.
Compared to BCM2711:
- the pixelvalves only drive one HDMI controller each
- HDMI1 PixelValve has a FIFO long enough to support 4k at 60Hz
- support has been added for odd horizonta
Add in the compatible string and VC4_GEN_ enum for the D-step
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_drv.c | 1 +
drivers/gpu/drm/vc4/vc4_drv.h | 1 +
drivers/gpu/drm/vc4/vc4_hvs.c | 4
drivers/gpu/drm/vc4/vc4_regs.h | 3 +++
4 files changed, 9 insertions(+)
diff --gi
From: Maxime Ripard
The BCM2712 has a MOP controller which is basically a new revision of
the TXP.
Express that by adding a new compatible for it.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
Documentation/devicetree/bindings/display/brcm,bcm2835-txp.yaml | 4 +++-
1 file c
From: Maxime Ripard
The BCM2712 has an improved display pipeline, most notably with a
different HVS and only HDMI and writeback outputs.
Let's introduce it as a new VideoCore generation and compatible.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_drv
From: Maxime Ripard
The BCM2712 has 3 different pixelvalves that are similar to the ones
found in the previous generations but with slightly different
capabilities.
Express that using a new set of compatibles.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
.../devicetree/bind
From: Maxime Ripard
The BCM2712 SoC comes with a new variation of the videocore display
pipeline. Let's create a new compatible for it.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
Documentation/devicetree/bindings/display/brcm,bcm2835-vc4.yaml | 1 +
1 file changed, 1 inser
From: Maxime Ripard
The BCM2712 has a completely different HVS than the previous
generations, so let's add a new compatible for it.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
Documentation/devicetree/bindings/display/brcm,bcm2835-hvs.yaml | 5 -
1 file changed, 4 inser
From: Maxime Ripard
The BCM2712 HDMI controller uses a slightly different HDMI controller
than the BCM2711, and a completely different PHY.
Let's introduce a new compatible for it.
Signed-off-by: Maxime Ripard
Signed-off-by: Dave Stevenson
---
Documentation/devicetree/bindings/display/brcm,b
Use of_device_get_match_data to retrieve the generation value
as set in the struct of_device_id, rather than manually comparing
compatible strings.
Signed-off-by: Dave Stevenson
---
drivers/gpu/drm/vc4/vc4_drv.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/driv
Hi
Am 22.10.24 um 11:47 schrieb Pavel Machek:
Hi!
Sorry for taking a bit long to respond.
This "illumination" subsystem would (from my perspective) act like some sort of
LED subsystem
for devices with a high count of LEDs, like some RGB keyboards.
This would allow us too:
- provide an abstr
On 10/22/2024 8:35 PM, Rob Clark wrote:
> On Fri, Sep 20, 2024 at 9:15 AM Akhil P Oommen
> wrote:
>>
>> On Wed, Sep 18, 2024 at 08:39:30AM -0700, Rob Clark wrote:
>>> On Wed, Sep 18, 2024 at 12:46 AM Neil Armstrong
>>> wrote:
Hi,
On 17/09/2024 13:14, Antonino Maniscalco wrote
As only second scaler can be used for sharpness check if it
is available and also check if panel fitting is also not enabled,
then set the sharpness. Panel fitting will have the preference
over sharpness property.
v2: Add the panel fitting check before enabling sharpness
v3: Reframe commit message
The sharpness property requires the use of one of the scaler
so need to set the sharpness scaler coefficient values.
These values are based on experiments and vary for different
tap value/win size. These values are normalized by taking the
sum of all values and then dividing each value with a sum.
On 2024-10-23 09:53, Melissa Wen wrote:
There are two events to trace the beginning and the end of
amdgpu_dm_atomic_commit_tail, but only the one ate the beginning was
placed. Place amdgpu_dm_atomic_commit_tail_finish tracepoint at the end
than.
Signed-off-by: Melissa Wen
Reviewed-by: Leo
Add new registers and related bits. Compute the strength
value and tap value based on display mode.
v2: Replace i915/dev_priv with display[Jani]
v3: Create separate file for defining register[Jani]
Add display->drm in debug prints[Jani]
v4: Rebase
Signed-off-by: Nemesa Garg
---
drivers/gpu/
Load the lut values during pipe enable.
v2: Add the display version check
Signed-off-by: Nemesa Garg
---
drivers/gpu/drm/i915/display/intel_crtc.c| 3 +++
drivers/gpu/drm/i915/display/intel_display.c | 6 ++
.../gpu/drm/i915/display/intel_display_types.h | 2 ++
drivers/gpu
Many a times images are blurred or upscaled content is also not as
crisp as original rendered image. Traditional sharpening techniques often
apply a uniform level of enhancement across entire image, which sometimes
result in over-sharpening of some areas and potential loss of natural detail
Introduces the new crtc property "SHARPNESS_STRENGTH" that allows
the user to set the intensity so as to get the sharpness effect.
The value of this property can be set from 0-255.
It is useful in scenario when the output is blurry and user
want to sharpen the pixels. User can increase/decrease the
On Tue, Oct 22, 2024 at 9:27 PM Kai-Heng Feng wrote:
>
>
>
> On 2024/10/22 9:04 PM, Alex Deucher wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > On Tue, Oct 22, 2024 at 2:31 AM Kai-Heng Feng wrote:
> >>
> >> Hi Luke,
> >>
> >> On 2024/10/15 4:04 PM, Luke Jones wrot
On 10/23/24 3:52 AM, Maarten Lankhorst wrote:
The initial version was based roughly on the rdma and misc cgroup
controllers, with a lot of the accounting code borrowed from rdma.
The current version is a complete rewrite with page counter; it uses
the same min/low/max semantics as the memory cgr
On Sat, 19 Oct 2024 at 10:34, Stefan Wahren wrote:
>
> Hi,
>
> Am 17.10.24 um 17:59 schrieb Maxime Ripard:
> > On Thu, Oct 17, 2024 at 05:26:46PM GMT, Stefan Wahren wrote:
> >> Am 17.10.24 um 16:27 schrieb Maxime Ripard:
> >>> On Wed, Oct 16, 2024 at 07:16:43PM GMT, Dave Stevenson wrote:
> Hi
Hi, Moudy:
Moudy Ho 於 2024年10月7日 週一 上午10:28寫道：
>
> 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, the constraints for 'clocks' and
On Wed, 23 Oct 2024 14:44:09 +0200, Rouven Czerwinski wrote:
> The LXD M9189A is a 1024x600 MIPI-DSI panel.
>
> Signed-off-by: Rouven Czerwinski
> ---
> .../bindings/display/panel/lxd,m9189a.yaml| 64 +++
> 1 file changed, 64 insertions(+)
> create mode 100644
> Documenta
Hi, Fei:
Fei Shao 於 2024年10月19日 週六 下午1:30寫道：
>
> There are two kinds of MediaTek DPI devices in the tree: the ones with a
> power domain and those without (or missing). The former are the majority
> and are more common in newer DTs. Only three older DTs fall into the
> latter category: MT2701, MT
Hi, Macpaul:
Macpaul Lin 於 2024年10月3日 週四 上午11:09寫道：
>
> The MediaTek DPI module is typically associated with one of the
> following multimedia power domains:
> - POWER_DOMAIN_DISPLAY
> - POWER_DOMAIN_VDOSYS
> - POWER_DOMAIN_MM
> The specific power domain used varies depending on the SoC design
On 10/23/24 08:20, Christoph Hellwig wrote:
On Wed, Oct 16, 2024 at 11:52:39AM -0700, David Wei wrote:
From: Pavel Begunkov
Currently net_iov stores a pointer to struct dmabuf_genpool_chunk_owner,
which serves as a useful abstraction to share data and provide a
context. However, it's too devme
From: Ian Forbes
[ Upstream commit 28a5dfd4f615539fb22fb6d5c219c199c14e6eb6 ]
Currently the array size is only limited by the largest kmalloc size which
is incorrect. This change will also return a more specific error message
than ENOMEM to userspace.
Signed-off-by: Ian Forbes
Reviewed-by: Zac
1 - 100 of 168 matches
Mail list logo
