Could you please check this patch.
Best regards
Hoegeun
> -Original Message-
> From: dri-devel On Behalf Of
> Hoegeun Kwon
> Sent: Monday, January 16, 2023 6:44 PM
> To: dri-devel@lists.freedesktop.org; hoegeun.k...@samsung.com
> Subject: [PATCH libdrm] vbltest: add option to use high pi
The driver checks if the pixel clock of the given mode matches an entry
in the mpll config table. At least for the Synopsys phy the frequencies
in the mpll table are meant as a frequency range up to which the entry
works, not as a frequency that must match the pixel clock. Return
MODE_OK when the p
Another round of these patches. Only change this time is the addition
of a patch to limit the resolutions to the ones supported by the VOP
driver which should resolve the regression reported by FUKAUMI Naoki.
Sascha
Changes since v3:
- Add patch to limit VOP resolutions to hardware capabilities
The different VOP variants support different maximum resolutions. Reject
resolutions that are not supported by a specific variant.
This hasn't been a problem in the upstream driver so far as 1920x1080
has been the maximum resolution supported by the HDMI driver and that
resolution is supported by
This adds the PLL/phy settings to support higher resolutions like 4k@30.
The values were taken from the Rockchip downstream Kernel.
Tested-by: Michael Riesch
Link: https://lore.kernel.org/r/20220926080435.259617-3-s.ha...@pengutronix.de
Tested-by: Nicolas Frattaroli
Tested-by: Dan Johansen
Link
The Rockchip PLL drivers are currently table based and support only
the most common pixelclocks. Discard all modes we cannot achieve
at all. Normally the desired pixelclocks have an exact match in the
PLL driver, nevertheless allow for a 0.1% error just in case.
Tested-by: Nicolas Frattaroli
Test
Hello Christoph!
On Fri, 2023-02-03 at 08:14 +0100, Christoph Hellwig wrote:
> On Mon, Jan 16, 2023 at 09:52:10AM +0100, John Paul Adrian Glaubitz wrote:
> > We have had a discussion between multiple people invested in the SuperH
> > port and
> > I have decided to volunteer as a co-maintainer of
On 06.02.2023 19:32, Andi Shyti wrote:
From: Aravind Iddamsetty
During module load the punit might still be busy with its booting
routines. During this time we try to communicate with it but we
fail because we don't receive any feedback from it and we return
immediately with a -EINVAL fatal err
On 06/02/2023 09.11, Frieder Schrempf wrote:
> On 03.02.23 13:29, Rasmus Villemoes wrote:
>> On 01/02/2023 23.00, Marek Vasut wrote:
>>> On 1/30/23 13:45, Rasmus Villemoes wrote:
On 27/01/2023 12.30, Marek Vasut wrote:
> On 1/27/23 12:04, Jagan Teki wrote:
>>> Thanks, but that's e
Den 07.02.2023 kl. 09.44 skrev Sascha Hauer:
The different VOP variants support different maximum resolutions. Reject
resolutions that are not supported by a specific variant.
This hasn't been a problem in the upstream driver so far as 1920x1080
has been the maximum resolution supported by the
On 2/7/23 10:09, Rasmus Villemoes wrote:
[...]
Now hotplug-detect doesn't work with the current sn65dsi86 driver, but
that's a separate issue; when I boot with a monitor attached, its edid
is correctly read out. But I still don't get any output, and the monitor
says "no signal" - my naive attem
On Fri, 3 Feb 2023 at 15:54, Ashutosh Dixit wrote:
>
> Previous documentation suggested that PL1 power limit is always
> enabled. However we now find this not to be the case on some
> platforms (such as ATSM). Therefore enable PL1 power limit during hwmon
> initialization.
For some reason it look
Am 06.02.23 um 19:20 schrieb Danilo Krummrich:
On 2/6/23 17:14, Christian König wrote:
Concentrating this discussion on a very big misunderstanding first.
Am 06.02.23 um 14:27 schrieb Danilo Krummrich:
[SNIP]
My understanding is that userspace is fully responsible on the parts
of the GPU VA s
On Tue, Feb 07, 2023 at 10:16:57AM +0100, Dan Johansen wrote:
>
> Den 07.02.2023 kl. 09.44 skrev Sascha Hauer:
> > The different VOP variants support different maximum resolutions. Reject
> > resolutions that are not supported by a specific variant.
> >
> > This hasn't been a problem in the upstr
Hi Dmitry,
On Tue, Jan 10, 2023 at 5:37 PM Dmitry Baryshkov
wrote:
> On 10/01/2023 08:57, Laurentiu Palcu wrote:
> > On Mon, Jan 09, 2023 at 10:26:28PM +0200, Dmitry Baryshkov wrote:
> >> On 09/01/2023 18:21, Laurentiu Palcu wrote:
> >>> It looks like there are some issues with this patchset... :
On Tue, Jan 10, 2023 at 11:20 AM Geert Uytterhoeven
wrote:
> On Tue, Jan 10, 2023 at 8:07 AM Laurentiu Palcu
> wrote:
> > On Mon, Jan 09, 2023 at 10:26:28PM +0200, Dmitry Baryshkov wrote:
> > > On 09/01/2023 18:21, Laurentiu Palcu wrote:
> > > > It looks like there are some issues with this patch
Hi Geert,
On 07/02/2023 10:40, Geert Uytterhoeven wrote:
Hi Dmitry,
On Tue, Jan 10, 2023 at 5:37 PM Dmitry Baryshkov
wrote:
On 10/01/2023 08:57, Laurentiu Palcu wrote:
On Mon, Jan 09, 2023 at 10:26:28PM +0200, Dmitry Baryshkov wrote:
On 09/01/2023 18:21, Laurentiu Palcu wrote:
It looks lik
Hi Neil,
On Tue, Feb 7, 2023 at 10:59 AM Neil Armstrong
wrote:
> On 07/02/2023 10:40, Geert Uytterhoeven wrote:
> > On Tue, Jan 10, 2023 at 5:37 PM Dmitry Baryshkov
> > wrote:
> >> On 10/01/2023 08:57, Laurentiu Palcu wrote:
> >>> On Mon, Jan 09, 2023 at 10:26:28PM +0200, Dmitry Baryshkov wrote:
vdd-supply = <&vreg_l11b_1p2>;
+
+reset-gpios = <&tlmm 133 GPIO_ACTIVE_LOW>;
+
+port {
+panel0_in: endpoint {
+remote-endpoint = <&dsi0_out>;
+};
};
};
};
Hi Rob,
Thanks for the review.
On Wed, Jan 18, 2023 at 4:17 AM Rob Herring wrote:
>
> On Mon, Jan 16, 2023 at 07:08:19PM +0800, Pin-yen Lin wrote:
> > From: Nicolas Boichat
> >
> > Add bindings for Generic GPIO mux driver.
> >
> > Signed-off-by: Nicolas Boichat
> > Signed-off-by: Pin-yen Lin
Hi Lyude,
Thanks for letting me know!
I just sent out a v11 and already received some review comments, but
reviews are always welcomed if you have time to take a look.
Regards,
Pin-yen
On Tue, Jan 31, 2023 at 7:10 AM Lyude Paul wrote:
>
> Don't know if this still needs reviews from me (feel fr
On 07/02/2023 11:02, Geert Uytterhoeven wrote:
Hi Neil,
On Tue, Feb 7, 2023 at 10:59 AM Neil Armstrong
wrote:
On 07/02/2023 10:40, Geert Uytterhoeven wrote:
On Tue, Jan 10, 2023 at 5:37 PM Dmitry Baryshkov
wrote:
On 10/01/2023 08:57, Laurentiu Palcu wrote:
On Mon, Jan 09, 2023 at 10:26:28P
Hi Neil,
On Tue, Feb 7, 2023 at 11:02 AM Geert Uytterhoeven wrote:
> On Tue, Feb 7, 2023 at 10:59 AM Neil Armstrong
> wrote:
> > On 07/02/2023 10:40, Geert Uytterhoeven wrote:
> > > On Tue, Jan 10, 2023 at 5:37 PM Dmitry Baryshkov
> > > wrote:
> > >> On 10/01/2023 08:57, Laurentiu Palcu wrote:
On Tue, Feb 07, 2023 at 06:07:44PM +0800, Pin-yen Lin wrote:
> On Wed, Jan 18, 2023 at 4:17 AM Rob Herring wrote:
> > On Mon, Jan 16, 2023 at 07:08:19PM +0800, Pin-yen Lin wrote:
> > > From: Nicolas Boichat
> > >
> > > Add bindings for Generic GPIO mux driver.
> > >
> > > Signed-off-by: Nicolas Bo
Hi Dmitry,
On Tue, 24 Jan 2023, Dmitry Baryshkov wrote:
There are two flags attemting to guard connector polling:
poll_enabled and poll_running. While poll_enabled semantics is clearly
defined and fully adhered (mark that drm_kms_helper_poll_init() was
called and not finalized by the _fi
Hi Laurent,
On Tue, Feb 7, 2023 at 6:25 PM Laurent Pinchart
wrote:
>
> On Tue, Feb 07, 2023 at 06:07:44PM +0800, Pin-yen Lin wrote:
> > On Wed, Jan 18, 2023 at 4:17 AM Rob Herring wrote:
> > > On Mon, Jan 16, 2023 at 07:08:19PM +0800, Pin-yen Lin wrote:
> > > > From: Nicolas Boichat
> > > >
> >
On 07/02/2023 03.47, Javier Martinez Canillas wrote:
> Hello Lina,
>
> On 2/5/23 13:51, Asahi Lina wrote:
>> Other functions touching shmem->sgt take the pages lock, so do that here
>> too. drm_gem_shmem_get_pages() & co take the same lock, so move to the
>> _locked() variants to avoid recursive l
Hi Andrzej,
> > During module load the punit might still be busy with its booting
> > routines. During this time we try to communicate with it but we
> > fail because we don't receive any feedback from it and we return
> > immediately with a -EINVAL fatal error.
> >
> > At this point the driver l
On 2/7/23 11:33, Asahi Lina wrote:
> On 07/02/2023 03.47, Javier Martinez Canillas wrote:
>> Hello Lina,
>>
>> On 2/5/23 13:51, Asahi Lina wrote:
>>> Other functions touching shmem->sgt take the pages lock, so do that here
>>> too. drm_gem_shmem_get_pages() & co take the same lock, so move to the
>
Hi Sascha,
On 2023-02-07 09:44, Sascha Hauer wrote:
> The different VOP variants support different maximum resolutions. Reject
> resolutions that are not supported by a specific variant.
>
> This hasn't been a problem in the upstream driver so far as 1920x1080
> has been the maximum resolution sup
On 2/7/23 10:35, Christian König wrote:
Am 06.02.23 um 19:20 schrieb Danilo Krummrich:
On 2/6/23 17:14, Christian König wrote:
Concentrating this discussion on a very big misunderstanding first.
Am 06.02.23 um 14:27 schrieb Danilo Krummrich:
[SNIP]
My understanding is that userspace is fully
During the driver conversion to shmem, there is a missing page shift when
computing the start address in GPU memory.
This leads to graphic garbage when connecting to the remote BMC, depending
on the PCI start address.
Tested on a sr645 affected by this bug.
Fixes: f2fa5a99ca81 ("drm/ast: Convert
Hi Sascha,
On 2023-02-07 09:44, Sascha Hauer wrote:
> The Rockchip PLL drivers are currently table based and support only
> the most common pixelclocks. Discard all modes we cannot achieve
> at all. Normally the desired pixelclocks have an exact match in the
> PLL driver, nevertheless allow for a
Hi
Am 07.02.23 um 11:53 schrieb Jocelyn Falempe:
During the driver conversion to shmem, there is a missing page shift when
computing the start address in GPU memory.
This leads to graphic garbage when connecting to the remote BMC, depending
on the PCI start address.
Tested on a sr645 affected b
Hi
Am 05.02.23 um 13:51 schrieb Asahi Lina:
Other functions touching shmem->sgt take the pages lock, so do that here
Really? I was just locking at the Lima driver and it apparently access
sgt without locking in [1]. Not that I disagree with the patch in general.
Best regards
Thomas
[1]
ht
Hi Stanislaw,
On 2/1/23 12:20, Stanislaw Gruszka wrote:
Hi
I was about to send debugfs support for ivpu and noticed that there
are current changes that deprecate drm_devel->debugfs_init callback.
Further I looked at this commit [1], that stated we should not
use drm_minor for debugfs and sysfs
On 07/02/2023 12:17, Thomas Zimmermann wrote:
Hi
Am 07.02.23 um 11:53 schrieb Jocelyn Falempe:
During the driver conversion to shmem, there is a missing page shift when
computing the start address in GPU memory.
This leads to graphic garbage when connecting to the remote BMC,
depending
on the
On Mon, Feb 06, 2023 at 07:42:32PM -0500, Lyude Paul wrote:
> On Wed, 2023-02-01 at 17:04 +0200, Imre Deak wrote:
> >
> > Yes, this patch should have no functional change, so please check what
> > would apply to other drivers as well.
> >
> > Could you also check Ville's comment about storing sta
On Tue, Feb 07, 2023 at 10:46:49AM +, Jonas Karlman wrote:
> Hi Sascha,
> On 2023-02-07 09:44, Sascha Hauer wrote:
> > The different VOP variants support different maximum resolutions. Reject
> > resolutions that are not supported by a specific variant.
> >
> > This hasn't been a problem in th
On Wed, 25 Jan 2023 12:59:53 +
Joshua Ashton wrote:
> On 1/23/23 20:30, Sebastian Wick wrote:
> > A new property to control YCC and subsampling would be the more
> > complete path here. If we actually want to fix this in the short-term
> > though, we should handle the YCC and RGB Colorspace v
On Fri, 13 Jan 2023 11:24:07 -0500
Harry Wentland wrote:
> This patchset enables the DP and HDMI infoframe properties
> in amdgpu.
>
> The first two patches are not completely related to the rest. The
> first patch allows for HDR_OUTPUT_METADATA with EOTFs that are
> unknown in the kernel.
>
>
On Tue, Feb 07, 2023 at 11:01:26AM +, Jonas Karlman wrote:
> Hi Sascha,
>
> On 2023-02-07 09:44, Sascha Hauer wrote:
> > The Rockchip PLL drivers are currently table based and support only
> > the most common pixelclocks. Discard all modes we cannot achieve
> > at all. Normally the desired pix
Hi all,
On Mon, Feb 06, 2023 at 01:48:53PM +0200, Imre Deak wrote:
> Add the MST topology for a CRTC to the atomic state if the driver
> needs to force a modeset on the CRTC after the encoder compute config
> functions are called.
>
> Later the MST encoder's disable hook also adds the state, but
t in any later version?
$ git log --oneline --author=dmitry next-20230207
drivers/gpu/drm/drm_probe_helper.c
c8268795c9a9 drm/probe-helper: enable and disable HPD on connectors
78b991ccfa64 drm/poll-helper: merge drm_kms_helper_poll_disable() and _fini()
$
On Mon, 23 Jan 2023 21:38:11 +0100
Christian König wrote:
> Am 23.01.23 um 21:26 schrieb André Almeida:
> > Create a document that specifies how to deal with DRM device resets for
> > kernel and userspace drivers.
> >
> > Signed-off-by: André Almeida
> > ---
> > Documentation/gpu/drm-reset.rst
> -Original Message-
> From: Dmitry Baryshkov
> Sent: Tuesday, January 31, 2023 6:29 PM
> To: Vinod Polimera (QUIC) ; dri-
> de...@lists.freedesktop.org; linux-arm-...@vger.kernel.org;
> freedr...@lists.freedesktop.org; devicet...@vger.kernel.org
> Cc: linux-ker...@vger.kernel.org; robdc
> -Original Message-
> From: Dmitry Baryshkov
> Sent: Tuesday, January 31, 2023 6:19 PM
> To: Vinod Polimera (QUIC) ; dri-
> de...@lists.freedesktop.org; linux-arm-...@vger.kernel.org;
> freedr...@lists.freedesktop.org; devicet...@vger.kernel.org
> Cc: Sankeerth Billakanti (QUIC) ; linux
This series will enable color features on sc7280 target which has
primary panel as eDP
The series removes DSPP allocation based on encoder type and allows
the DSPP reservation based on user request via CTM.
The series will release/reserve the dpu resources when ever there is
a topology change
Add DSPP blocks into the topology for reservation, if there
is a CTM request for that composition.
Signed-off-by: Kalyan Thota
---
Changes in v1:
- Minor nits (Dmitry)
Changes in v2:
- Populate DSPPs into the reservation only if CTM is requested (Dmitry)
---
drivers/gpu/drm/msm/disp/dpu1/dpu_en
Clear DSPP reservations from the global state during
rm release
Fixes: e47616df008b ("drm/msm/dpu: add support for color
processing blocks in dpu driver")
Signed-off-by: Kalyan Thota
Reviewed-by: Dmitry Baryshkov
Reviewed-by: Marijn Suijten
---
drivers/gpu/drm/msm/disp/dp
Some features like CTM can be enabled dynamically. Release
and reserve the DPU resources whenever a topology change
occurs such that required hw blocks are allocated appropriately.
Signed-off-by: Kalyan Thota
---
Changes in v1:
- Avoid mode_set call directly (Dmitry)
Changes in v2:
- Minor nits
Return immediately on failure, this will make dpu reservations
part look cleaner.
Signed-off-by: Kalyan Thota
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c
nabled") in
next-20230127 next-20230130 next-20230131
but not in any later version?
$ git log --oneline --author=dmitry next-20230207
drivers/gpu/drm/drm_probe_helper.c
c8268795c9a9 drm/probe-helper: enable and disable HPD on connectors
78b991ccfa64 drm/poll-helper: merge drm_kms_helper_poll_disa
On 2/7/23 14:30, Pekka Paalanen wrote:
> On Mon, 23 Jan 2023 21:38:11 +0100
> Christian König wrote:
>> Am 23.01.23 um 21:26 schrieb André Almeida:
>>>
>>> diff --git a/Documentation/gpu/drm-reset.rst
>>> b/Documentation/gpu/drm-reset.rst
>>> new file mode 100644
>>> index ..0dd11a469
On 07/02/2023 16:29, Kalyan Thota wrote:
Clear DSPP reservations from the global state during
rm release
Fixes: e47616df008b ("drm/msm/dpu: add support for color
processing blocks in dpu driver")
This should fit into a single line (even it is longer than the
recommended l
Hello Pin-yen,
On Tue, Feb 07, 2023 at 06:30:36PM +0800, Pin-yen Lin wrote:
> On Tue, Feb 7, 2023 at 6:25 PM Laurent Pinchart wrote:
> > On Tue, Feb 07, 2023 at 06:07:44PM +0800, Pin-yen Lin wrote:
> > > On Wed, Jan 18, 2023 at 4:17 AM Rob Herring wrote:
> > > > On Mon, Jan 16, 2023 at 07:08:19PM
On 07/02/2023 16:29, Kalyan Thota wrote:
Add DSPP blocks into the topology for reservation, if there
is a CTM request for that composition.
Signed-off-by: Kalyan Thota
---
Changes in v1:
- Minor nits (Dmitry)
Changes in v2:
- Populate DSPPs into the reservation only if CTM is requested (Dmitry
On 07/02/2023 16:29, Kalyan Thota wrote:
Return immediately on failure, this will make dpu reservations
part look cleaner.
Signed-off-by: Kalyan Thota
---
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
Reviewed-by:
On 07/02/2023 16:29, Kalyan Thota wrote:
Some features like CTM can be enabled dynamically. Release
and reserve the DPU resources whenever a topology change
occurs such that required hw blocks are allocated appropriately.
Signed-off-by: Kalyan Thota
---
Changes in v1:
- Avoid mode_set call dire
On 07/02/2023 16:28, Vinod Polimera wrote:
-Original Message-
From: Dmitry Baryshkov
Sent: Tuesday, January 31, 2023 6:19 PM
To: Vinod Polimera (QUIC) ; dri-
de...@lists.freedesktop.org; linux-arm-...@vger.kernel.org;
freedr...@lists.freedesktop.org; devicet...@vger.kernel.org
Cc: San
On 07/02/2023 16:26, Vinod Polimera wrote:
-Original Message-
From: Dmitry Baryshkov
Sent: Tuesday, January 31, 2023 6:29 PM
To: Vinod Polimera (QUIC) ; dri-
de...@lists.freedesktop.org; linux-arm-...@vger.kernel.org;
freedr...@lists.freedesktop.org; devicet...@vger.kernel.org
Cc: lin
On 07/02/2023 11:04, Neil Armstrong wrote:
> Add missing reg property and update example to add dsi top node.
>
> Fixes: ef85db911134 ("dt-bindings: display: panel: document the Visionox
> VTDR6130 AMOLED DSI Panel")
> Signed-off-by: Neil Armstrong
> ---
Reviewed-by: Krzysztof Kozlowski
Best
On 2/7/2023 4:31 AM, Maíra Canal wrote:
Hi Stanislaw,
On 2/1/23 12:20, Stanislaw Gruszka wrote:
Hi
I was about to send debugfs support for ivpu and noticed that there
are current changes that deprecate drm_devel->debugfs_init callback.
Further I looked at this commit [1], that stated we shoul
Further information:
With the above fix, the very early boot console messages are not
rotated. adding "fbcon=rotate:1" to the kernel command line corrects
this. But these early boot console messages are still garbled - it
looks like the display driver in use at the time cannot write to the
screen
On Mon, Feb 06, 2023 at 08:15:56PM -0800, Dmitry Torokhov wrote:
> On Mon, Feb 06, 2023 at 11:35:32AM +, Daniel Thompson wrote:
> > On Tue, Jan 31, 2023 at 02:57:06PM -0800, Dmitry Torokhov wrote:
> > > + dev_info(&spi->dev, "im gpio[%d] is not here
> > > yet, deferring
On 2/7/23 12:43, Jeffrey Hugo wrote:
On 2/7/2023 4:31 AM, Maíra Canal wrote:
Hi Stanislaw,
On 2/1/23 12:20, Stanislaw Gruszka wrote:
Hi
I was about to send debugfs support for ivpu and noticed that there
are current changes that deprecate drm_devel->debugfs_init callback.
Further I looked at
On Tue, 07 Feb 2023 01:32:44 -0800, Matthew Auld wrote:
>
> On Fri, 3 Feb 2023 at 15:54, Ashutosh Dixit wrote:
> >
> > Previous documentation suggested that PL1 power limit is always
> > enabled. However we now find this not to be the case on some
> > platforms (such as ATSM). Therefore enable PL1
Hi Sascha,
On 2023-02-07 13:51, Sascha Hauer wrote:
> On Tue, Feb 07, 2023 at 11:01:26AM +, Jonas Karlman wrote:
>> Hi Sascha,
>>
>> On 2023-02-07 09:44, Sascha Hauer wrote:
>>> The Rockchip PLL drivers are currently table based and support only
>>> the most common pixelclocks. Discard all mod
This cleans up the indentation according to the Linux kernel coding
style, and should fix the warning created by the kernel test robot.
Fixes: 8b08cf2b64f5a60594b07795b2ad518c6d044566 ("OMAP: add TI OMAP
framebuffer driver")
Reported-by: kernel test robot
Signed-off-by: Lucy Mielke
---
This cleans up the indentation according to the Linux kernel coding
style, and should fix the warning created by the kernel test robot.
Fixes: 8b08cf2b64f5a60594b07795b2ad518c6d044566 ("OMAP: add TI OMAP
framebuffer driver")
Reported-by: kernel test robot
Signed-off-by: Lucy Mielke
---
On Tue, 07 Feb 2023 08:12:25 -0800, Dixit, Ashutosh wrote:
>
> On Tue, 07 Feb 2023 01:32:44 -0800, Matthew Auld wrote:
> >
> > On Fri, 3 Feb 2023 at 15:54, Ashutosh Dixit
> > wrote:
> > >
> > > Previous documentation suggested that PL1 power limit is always
> > > enabled. However we now find this
From: Ville Syrjälä
CONFIG_DRM_USE_DYNAMIC_DEBUG breaks debug prints for (at least modular)
drm drivers. The debug prints can be reinstated by manually frobbing
/sys/module/drm/parameters/debug after the fact, but at that point the
damage is done and all debugs from driver probe are lost. This ma
On Tue, Feb 07, 2023 at 04:33:37PM +0200, Jani Nikula wrote:
> From: Ville Syrjälä
>
> CONFIG_DRM_USE_DYNAMIC_DEBUG breaks debug prints for (at least modular)
> drm drivers. The debug prints can be reinstated by manually frobbing
> /sys/module/drm/parameters/debug after the fact, but at that poin
On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
Split pipe-dependent code from dpu_plane_atomic_check() into the
separate function dpu_plane_atomic_check_pipe(). This is one of
Same comment as prev patch, dpu_plane_atomic_check_pipe() --->
dpu_plane_atomic_check_sspp()
preparational steps
On 07/02/2023 19:49, Abhinav Kumar wrote:
On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
Split pipe-dependent code from dpu_plane_atomic_check() into the
separate function dpu_plane_atomic_check_pipe(). This is one of
Same comment as prev patch, dpu_plane_atomic_check_pipe() --->
dpu_plane_a
On 2/7/2023 9:51 AM, Dmitry Baryshkov wrote:
On 07/02/2023 19:49, Abhinav Kumar wrote:
On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
Split pipe-dependent code from dpu_plane_atomic_check() into the
separate function dpu_plane_atomic_check_pipe(). This is one of
Same comment as prev patch
On 07/02/2023 19:57, Abhinav Kumar wrote:
On 2/7/2023 9:51 AM, Dmitry Baryshkov wrote:
On 07/02/2023 19:49, Abhinav Kumar wrote:
On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
Split pipe-dependent code from dpu_plane_atomic_check() into the
separate function dpu_plane_atomic_check_pipe(). T
On 2/7/2023 9:59 AM, Dmitry Baryshkov wrote:
On 07/02/2023 19:57, Abhinav Kumar wrote:
On 2/7/2023 9:51 AM, Dmitry Baryshkov wrote:
On 07/02/2023 19:49, Abhinav Kumar wrote:
On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
Split pipe-dependent code from dpu_plane_atomic_check() into the
s
On Wed, Feb 01, 2023 at 02:28:28PM -0800, Matt Roper wrote:
> XEHPC_LNCFMISCCFGREG0 and XEHPC_L3SCRUB are both in MCR register ranges
> on PVC (with HALFBSLICE and L3BANK replication respectively), so they
> should be explicitly declared as MCR registers and use MCR-aware
> workaround handlers.
>
Hi Neil.
On Tue, Feb 07, 2023 at 11:04:36AM +0100, Neil Armstrong wrote:
> Add missing reg property and update example to add dsi top node.
>
> Fixes: ef85db911134 ("dt-bindings: display: panel: document the Visionox
> VTDR6130 AMOLED DSI Panel")
> Signed-off-by: Neil Armstrong
> ---
> .../bi
On Tue, 7 Feb 2023 at 17:19, Dixit, Ashutosh wrote:
>
> On Tue, 07 Feb 2023 08:12:25 -0800, Dixit, Ashutosh wrote:
> >
> > On Tue, 07 Feb 2023 01:32:44 -0800, Matthew Auld wrote:
> > >
> > > On Fri, 3 Feb 2023 at 15:54, Ashutosh Dixit
> > > wrote:
> > > >
> > > > Previous documentation suggested
On Wed, Feb 01, 2023 at 02:28:29PM -0800, Matt Roper wrote:
> The UNSLICE_UNIT_LEVEL_CLKGATE register programmed by this workaround
> has 'BUS' style reset, indicating that it does not lose its value on
> engine resets. Furthermore, this register is part of the GT forcewake
> domain rather than th
On 07/02/2023 20:08, Abhinav Kumar wrote:
On 2/7/2023 9:59 AM, Dmitry Baryshkov wrote:
On 07/02/2023 19:57, Abhinav Kumar wrote:
On 2/7/2023 9:51 AM, Dmitry Baryshkov wrote:
On 07/02/2023 19:49, Abhinav Kumar wrote:
On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
Split pipe-dependent cod
On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
Rework the code flushing CSC settings for the plane. Separate out the
pipe and pipe_cfg as a preparation for r_pipe support.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 45 +--
1 file cha
On Wed, Feb 01, 2023 at 02:28:30PM -0800, Matt Roper wrote:
> Although registers in the L3 bank/node configuration ranges are marked
> as having "DEV" reset characteristics in the bspec, this appears to be a
> hold-over from pre-Xe_HP platforms. In reality, these registers
> maintain their values
On Tue, Feb 07, 2023 at 07:36:00PM +0100, Sam Ravnborg wrote:
> Hi Neil.
>
>
> On Tue, Feb 07, 2023 at 11:04:36AM +0100, Neil Armstrong wrote:
> > Add missing reg property and update example to add dsi top node.
> >
> > Fixes: ef85db911134 ("dt-bindings: display: panel: document the Visionox
>
On Mon, 06 Feb 2023 16:57:00 +0200, Dmitry Baryshkov wrote:
> The GPU clock controller bindings for the Qualcomm sm8350 platform are
> not correct. The driver uses .fw_name instead of using indices to bind
> parent clocks, thus demanding the clock-names usage. With the proper
> clock-names in pla
On Mon, 06 Feb 2023 16:57:02 +0200, Dmitry Baryshkov wrote:
> Add Adreno A660 to the A635 clause to define all version-specific
> properties. There is no need to add it to the top-level clause, since
> top-level compatible uses pattern to define compatible strings.
>
> Signed-off-by: Dmitry Bary
On Tue, 7 Feb 2023 at 22:05, Abhinav Kumar wrote:
>
>
>
> On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
> > Rework the code flushing CSC settings for the plane. Separate out the
> > pipe and pipe_cfg as a preparation for r_pipe support.
> >
> > Signed-off-by: Dmitry Baryshkov
> > ---
> > driver
On Sat, Feb 04, 2023 at 09:30:38PM +0800, Pin-yen Lin wrote:
> ITE IT6505 can be used in systems to switch the DP traffic between
> two downstreams, which can be USB Type-C DisplayPort alternate mode
> lane or regular DisplayPort output ports.
>
> Update the binding to accommodate this usage by in
On 2/7/2023 12:44 PM, Dmitry Baryshkov wrote:
On Tue, 7 Feb 2023 at 22:05, Abhinav Kumar wrote:
On 2/3/2023 10:21 AM, Dmitry Baryshkov wrote:
Rework the code flushing CSC settings for the plane. Separate out the
pipe and pipe_cfg as a preparation for r_pipe support.
Signed-off-by: Dmitr
On Tue, Feb 07, 2023 at 02:37:16PM -0600, Rob Herring wrote:
> On Tue, Feb 07, 2023 at 07:36:00PM +0100, Sam Ravnborg wrote:
> > Hi Neil.
> >
> >
> > On Tue, Feb 07, 2023 at 11:04:36AM +0100, Neil Armstrong wrote:
> > > Add missing reg property and update example to add dsi top node.
> > >
> > >
Hi Pin-yen,
[...]
> +static int drm_dp_register_mode_switch(struct device *dev,
> +struct fwnode_handle *fwnode,
> +struct drm_dp_typec_switch_desc
> *switch_desc,
> +void *data, typec_mux
On 07.02.2023 06:07, john.c.harri...@intel.com wrote:
> From: John Harrison
>
> Update more print messages to the new scheme.
>
> v2: Also change all errors to %pe rather than %d (MichalW).
> Few other tweaks.
>
> Signed-off-by: John Harrison
LGTM, series is
Reviewed-by: Michal Wajdeczko
On Wed, Feb 01, 2023 at 02:28:31PM -0800, Matt Roper wrote:
> Although register information in the bspec includes a field that is
> supposed to reflect a register's reset characteristics (i.e., whether a
> register maintains its value through engine resets), it's been
> discovered that this informa
Fix glitches when moving cursor close to the edge on a rotated screen
for drivers with one pipe (without pipe split) by halving dst_x_offset.
Reported-by: Xaver Hugl
Signed-off-by: Melissa Wen
---
Hi,
I'm not sure if having dst_x_offset (or only for the one pipe case) is
the right solution, bu
Sorry, I accidentally sent this reply offlist! Resending, my apologies...
On 07/02/2023 20.29, Thomas Zimmermann wrote:
> Hi
>
> Am 05.02.23 um 13:51 schrieb Asahi Lina:
>> Other functions touching shmem->sgt take the pages lock, so do that here
>
> Really? I was just locking at the Lima driver
On Tue, 2023-02-07 at 14:11 +0200, Imre Deak wrote:
> On Mon, Feb 06, 2023 at 07:42:32PM -0500, Lyude Paul wrote:
> > On Wed, 2023-02-01 at 17:04 +0200, Imre Deak wrote:
> > >
> > > Yes, this patch should have no functional change, so please check what
> > > would apply to other drivers as well.
>
On 2/7/23 01:06, John Paul Adrian Glaubitz wrote:
> Hello Christoph!
>
> On Fri, 2023-02-03 at 08:14 +0100, Christoph Hellwig wrote:
>> On Mon, Jan 16, 2023 at 09:52:10AM +0100, John Paul Adrian Glaubitz wrote:
>>> We have had a discussion between multiple people invested in the SuperH
>>> por
The function dsi_read is defined in the dw-mipi-dsi-rockchip.c file, but
not called elsewhere, so remove this unused function.
drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c:362:19: warning: unused
function 'dsi_read'.
Reported-by: Abaci Robot
Link: https://bugzilla.openanolis.cn/show_bug.cgi?
1 - 100 of 114 matches
Mail list logo
