On Wed, Nov 06, 2024 at 11:48:25AM +0100, Luca Ceresoli wrote:
> This message reports a mismatch between new_crtc_state->enable and
> has_connectors, which should be either both true or both false. However it
> does not mention which one is true and which is false, which can be useful
> for debuggi
On Fri, Nov 08, 2024 at 05:11:25PM +, Karan Sanghavi wrote:
> The left shift operation followed by a mask with 0xf will
> always result in 0. To correctly evaluate the expression for
> the bitwise OR operation, use a right shift instead.
>
> Reported by Coverity Scan CID: 1511468
>
> Fixes: 1
Hi,
On 2024/10/1 21:04, Lucas Stach wrote:
Hi Sui,
Am Sonntag, dem 08.09.2024 um 17:43 +0800 schrieb Sui Jingfeng:
It will be called by drm_gem_print_info() if implemented, and it can
provide more information about the framebuffer objects.
Etnaviv GEM BOs are not framebuffer objects.
Signed
On Fri, Nov 08, 2024 at 03:20:48PM +0100, Maxime Ripard wrote:
> On Fri, Nov 01, 2024 at 02:25:05AM +0200, Dmitry Baryshkov wrote:
> > Use new drm_hdmi_connector_mode_valid() helper instead of a
> > module-specific copy.
> >
> > Reviewed-by: Chen-Yu Tsai
> > Signed-off-by: Dmitry Baryshkov
> > -
On Fri, Nov 08, 2024 at 03:17:22PM +0100, Maxime Ripard wrote:
> Hi,
>
> On Fri, Nov 01, 2024 at 02:25:04AM +0200, Dmitry Baryshkov wrote:
> > Add drm_hdmi_connector_mode_valid(), generic helper for HDMI connectors.
> > It can be either used directly or as a part of the .mode_valid callback.
> >
On Thu, Nov 07, 2024 at 04:28:24PM -0800, Stephen Boyd wrote:
> Quoting Dmitry Baryshkov (2024-10-31 15:54:49)
> > On Thu, Oct 31, 2024 at 02:45:29PM -0700, Stephen Boyd wrote:
> > > Quoting Dmitry Baryshkov (2024-10-31 11:42:36)
> > > > On Tue, Oct 29, 2024 at 01:15:51PM -0700, Stephen Boyd wrote:
Hi,
在 2024/11/09 1:03, Liam R. Howlett 写道:
* Chuck Lever III [241108 08:23]:
On Nov 7, 2024, at 8:19 PM, Yu Kuai wrote:
Hi,
在 2024/11/07 22:41, Chuck Lever 写道:
On Thu, Nov 07, 2024 at 08:57:23AM +0800, Yu Kuai wrote:
Hi,
在 2024/11/06 23:19, Chuck Lever III 写道:
On Nov 6, 2024, at 1
Hi,
在 2024/11/08 21:23, Chuck Lever III 写道:
On Nov 7, 2024, at 8:19 PM, Yu Kuai wrote:
Hi,
在 2024/11/07 22:41, Chuck Lever 写道:
On Thu, Nov 07, 2024 at 08:57:23AM +0800, Yu Kuai wrote:
Hi,
在 2024/11/06 23:19, Chuck Lever III 写道:
On Nov 6, 2024, at 1:16 AM, Greg KH wrote:
On Thu, Oc
On Fri, Nov 8, 2024 at 1:43 AM Christian König
wrote:
>
> Hi guys,
>
> as pointed out by Chia-I userspace doesn't see any progress when
> signaling is not enabled and Boris noted that this is because
> dma_fence_array_signaled() never returns true in this case.
>
> Improve this by fixing the dma_f
On Tue, Sep 24, 2024 at 11:30:53AM +0200, Simona Vetter wrote:
> Apologies for the late reply ...
>
Also late reply, just read this.
> On Wed, Sep 04, 2024 at 01:34:18PM +0200, Christian König wrote:
> > Hi Boris,
> >
> > Am 04.09.24 um 13:23 schrieb Boris Brezillon:
> > > > > > > Please read u
On 11/8/24 09:21, Matthew Brost wrote:
On Thu, Nov 07, 2024 at 08:34:45PM -0800, Lizhi Hou wrote:
Add interfaces for user application to submit command and wait for its
completion.
Co-developed-by: Min Ma
Signed-off-by: Min Ma
Signed-off-by: Lizhi Hou
---
drivers/accel/amdxdna/aie2_ctx.c
Create a device tree for the 10 inch variants (P5100, P5110, P5113)
Signed-off-by: Mithil Bavishi
---
.../dts/ti/omap/omap4-samsung-espresso10.dts | 102 ++
1 file changed, 102 insertions(+)
create mode 100644 arch/arm/boot/dts/ti/omap/omap4-samsung-espresso10.dts
diff --git a
Add samsung-espresso10 codename for the 10 inch variant
Signed-off-by: Mithil Bavishi
---
Documentation/devicetree/bindings/arm/ti/omap.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/ti/omap.yaml
b/Documentation/devicetree/bindings/arm/ti/omap.yam
Create a device tree for the 7 inch variants (P3100, P3110, P3113)
Signed-off-by: Mithil Bavishi
---
.../dts/ti/omap/omap4-samsung-espresso7.dts | 70 +++
1 file changed, 70 insertions(+)
create mode 100644 arch/arm/boot/dts/ti/omap/omap4-samsung-espresso7.dts
diff --git a/ar
Add samsung-espresso7 codename for the 7 inch variant
Signed-off-by: Mithil Bavishi
---
Documentation/devicetree/bindings/arm/ti/omap.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/ti/omap.yaml
b/Documentation/devicetree/bindings/arm/ti/omap.yaml
Create common device tree for Samsung Espresso series devices
Let's create a common tree for all the variants first. Later we can
device specific trees based on their screen sizes.
Signed-off-by: Mithil Bavishi
---
.../omap/omap4-samsung-espresso-common.dtsi | 680 ++
1 file c
The LTN101AL03 is a 10.1 inch 800x1280, 24 bit, VESA Compatible, TFT display
panel
Signed-off-by: Mithil Bavishi
---
Documentation/devicetree/bindings/display/panel/panel-lvds.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/panel/panel-lvds.y
The pull request you sent on Sat, 9 Nov 2024 05:31:26 +1000:
> https://gitlab.freedesktop.org/drm/kernel.git tags/drm-fixes-2024-11-09
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/952a33dc08cefde50540cc82abaa2e09f37ef540
Thank you!
--
Deet-doot-dot, I am a bot.
ht
The LTN070NL01 is a 7.0 inch 1024x600, 24 bit, VESA Compatible, TFT display
panel
Signed-off-by: Mithil Bavishi
---
Documentation/devicetree/bindings/display/panel/panel-lvds.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/panel/panel-lvds.ya
Add compatible strings for the Doestek DTC34LM85AM Flat Panel Display
Transmitter
Signed-off-by: Mithil Bavishi
---
Documentation/devicetree/bindings/display/bridge/lvds-codec.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/display/bridge/lvds-codec.yam
Add vendor prefix for Doestek Co., Ltd.
Link: http://www.doestek.co.kr/
Signed-off-by: Mithil Bavishi
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
b/Documentation/devicetre
Add a dedicated DTS file for the TWL6032 PMIC (Phoenix Lite). Already
has driver support with TWL6030 (Phoenix) since both of them are so
similar, some nodes can be reused from TWL6030 as well.
This can be included in the board files like twl6030.
Example:
...
&i2c1 {
twl: twl@48 {
reg
This series adds initial support for the Samsung Galaxy Tab 2
(samsung-espresso7/10) series of devices. It adds support for 6 variants
(P3100, P3110, P3113, P5100, P5110, P5113). Downstream categorised them
based on 3G and WiFi, but since they use different panel, touch
controllers, batteries, I de
On 08.11.24 18:05, Jason Gunthorpe wrote:
On Fri, Nov 08, 2024 at 04:20:30PM +, Fuad Tabba wrote:
Some folios, such as hugetlb folios and zone device folios,
require special handling when the folio's reference count reaches
0, before being freed. Moreover, guest_memfd folios will likely
requ
Hi Linus,
Weekly fixes, usual leaders in amdgpu and xe, then a panel quirk, and
some fixes to imagination and panthor drivers. Seems around the usual
level for this time and don't know of any big problems.
Regards,
Dave.
drm-fixes-2024-11-09:
drm fixes for 6.12-rc7
amdgpu:
- Brightness fix
- DC
Hi Detlev,
Am Freitag, 8. November 2024, 19:50:38 CET schrieb Detlev Casanova:
> Detlev Casanova (3):
> vop2: Add clock resets support
> arm64: dts: rockchip: Add VOP clock resets for rk3588s
> dt-bindings: display: vop2: Add VP clock resets
while it isn't that important for this short seri
Am 26.10.24 um 15:11 schrieb Stefan Wahren:
Hi,
during the investigations of the recent VC4 HDMI Sink issue [1], I was
able to reproduce another issue with vc4 after s2idle resume.
Sometimes ( probability ~ 1 : 30 cases ) I'm able to trigger a HVS
underrun and it's impact is that the HDMI display
The left shift operation followed by a mask with 0xf will
always result in 0. To correctly evaluate the expression for
the bitwise OR operation, use a right shift instead.
Reported by Coverity Scan CID: 1511468
Fixes: 1c66496b1391 ("drm/sprd: add Unisoc's drm mipi dsi&dphy driver")
Reviewed-by:
Add the documentation for VOP2 video ports reset clocks.
One reset can be set per video port.
Reviewed-by: Conor Dooley
Signed-off-by: Detlev Casanova
---
.../display/rockchip/rockchip-vop2.yaml | 40 +++
1 file changed, 40 insertions(+)
diff --git
a/Documentation/device
This adds the needed clock resets for all rk3588(s) based SOCs.
Signed-off-by: Detlev Casanova
---
arch/arm64/boot/dts/rockchip/rk3588-base.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi
b/arch/arm64/boot/dts/rockchip/rk3588-
At the end of initialization, each VP clock needs to be reset before
they can be used.
Failing to do so can put the VOP in an undefined state where the
generated HDMI signal is either lost or not matching the selected mode.
This issue can be reproduced by switching modes multiple times.
Depending
The clock reset must be used when the VOP is configured. Skipping it can
put the VOP in an unknown state where the HDMI signal is either lost or
not matching the selected mode.
This adds support for rk3588(s) based SoCs.
Changes since v2:
- Rebase on latest master
- Add details on how to reproduc
[why]
How we determine the dsc_aux used for dsc decompression in
drm_dp_mst_dsc_aux_for_port() today has defects:
1. The method how we determine a connected peer device is virtual or not
in drm_dp_mst_is_virtual_dpcd() is not always correct. There are DP1.4
products
in the market which don'
[why]
Starting from dp2 where dsc passthrough is introduced, it is required to
identify
the dsc passthrough aux, apart from dsc decompression aux. Existing
drm_dp_mst_port function
that returns dsc_aux alone is not sufficient.
[how]
1. Interface change in drm_dp_mst_dsc_aux_for_port, and depende
The patch series is to refactor existing dsc determination policy for
dsc decompression and dsc passthrough given a mst output port.
Original routine was written based on different peer device types
which is not accurate and shows difficulty when expanding support of
products that do not fully com
On Thu, Nov 07, 2024 at 08:34:45PM -0800, Lizhi Hou wrote:
> Add interfaces for user application to submit command and wait for its
> completion.
>
> Co-developed-by: Min Ma
> Signed-off-by: Min Ma
> Signed-off-by: Lizhi Hou
> ---
> drivers/accel/amdxdna/aie2_ctx.c | 634 +
* Chuck Lever III [241108 08:23]:
>
>
> > On Nov 7, 2024, at 8:19 PM, Yu Kuai wrote:
> >
> > Hi,
> >
> > 在 2024/11/07 22:41, Chuck Lever 写道:
> >> On Thu, Nov 07, 2024 at 08:57:23AM +0800, Yu Kuai wrote:
> >>> Hi,
> >>>
> >>> 在 2024/11/06 23:19, Chuck Lever III 写道:
>
>
> > On
On Fri, Nov 08, 2024 at 04:20:30PM +, Fuad Tabba wrote:
> Some folios, such as hugetlb folios and zone device folios,
> require special handling when the folio's reference count reaches
> 0, before being freed. Moreover, guest_memfd folios will likely
> require special handling to notify it onc
On Friday, 8 November 2024 11:39:57 EST Detlev Casanova wrote:
> On Thursday, 23 May 2024 23:09:26 EST Andy Yan wrote:
> > Hi Detlev，
> >
> > At 2024-05-23 02:57:48, "Detlev Casanova"
>
> wrote:
> > >At the end of initialization, each VP clock needs to be reset before
> > >they can be used.
> >
On Thursday, 23 May 2024 23:09:26 EST Andy Yan wrote:
> Hi Detlev，
>
> At 2024-05-23 02:57:48, "Detlev Casanova"
wrote:
> >At the end of initialization, each VP clock needs to be reset before
> >they can be used.
> >
> >Failing to do so can put the VOP in an undefined state where the
> >generate
On 08/11/2024 16:42, Thomas Zimmermann wrote:
Move the public header file drm_client_setup.h to the clients/
subdirectory and update all drivers. No functional changes.
Thanks, it looks good to me.
Reviewed-by: Jocelyn Falempe
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/amd/amd
On 08/11/2024 16:42, Thomas Zimmermann wrote:
DRM drivers invoke drm_client_setup() to set up in-kernel clients.
No driver should call drm_fbdev_client_setup() directly. Therefore,
unexport the symbol and move the declaration to the internal header
drm_client_internal.h.
Thanks, it looks good t
On Fri Nov 8, 2024 at 5:31 PM CET, Heiko Stübner wrote:
> Am Freitag, 8. November 2024, 16:21:24 CET schrieb Diederik de Haas:
> > On Fri Nov 8, 2024 at 3:44 PM CET, Heiko Stuebner wrote:
> > > From: Heiko Stuebner
> > >
> > > DRM_DEV_ERROR is deprecated and using dev_err_probe saves quite a numbe
On 08/11/2024 16:42, Thomas Zimmermann wrote:
Just move some files around to keep source code well organized. Plus
fix a type in the help text of CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM. No
functional changes.
Thanks, it looks good to me.
Reviewed-by: Jocelyn Falempe
Signed-off-by: Thomas Zimmerma
On 08/11/2024 16:42, Thomas Zimmermann wrote:
The drm_log client will likely be merged into DRM soon. Time to clean
up some of the existing files. This series moves the existing DRM
client for fbdev emulation and its build infrastructure into clients/
subdirectories. Drm_log can then be located t
On 11/8/24 6:59 PM, John Watts wrote:
> On Fri, Nov 08, 2024 at 11:53:57AM +, Andre Przywara wrote:
>> Hi John,
>
> Hi Andre!
>
>> Can you say *why* this patch is needed? Is there something broken that
>> needs fixing? Where does this show and why wasn't this a problem before?
>
> Oops, that
Add optional reset support which is mentioned in vivante,gc.yaml to
allow the driver to work on SoCs whose reset signal is asserted by default
Avoid enabling the interrupt until everything is ready
Signed-off-by: Philippe Lecointre
Reviewed-by: Simon Lenain
---
v2:
- Add missing include of irq.h
Am Freitag, 8. November 2024, 16:21:24 CET schrieb Diederik de Haas:
> On Fri Nov 8, 2024 at 3:44 PM CET, Heiko Stuebner wrote:
> > From: Heiko Stuebner
> >
> > DRM_DEV_ERROR is deprecated and using dev_err_probe saves quite a number
> > of lines too, so convert the error prints for the dsi-driver
The pointer to pgmap in struct page is overlaid with folio
owner_ops. To indicate that a page/folio has owner ops, bit 1 is
set. Therefore, before we can start to using owner_ops, we need
to ensure that all accesses to page pgmap sanitize the pointer
value.
This patch introduces the accessors, whi
From: David Hildenbrand
We replaced a simple put_page() by a putback_active_hugepage() call in
commit 3aaa76e125c1 (" mm: migrate: hugetlb: putback destination hugepage
to active list"), to set the "active" flag on the dst hugetlb folio.
Nowadays, we decoupled the "active" list from the flag, by
From: David Hildenbrand
Let's avoid messing with pages.
Signed-off-by: David Hildenbrand
Signed-off-by: Fuad Tabba
---
mm/hugetlb.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index d58bd815fdf2..a64852280213 100644
--- a/mm/hugetlb.c
Now that we have the folio_owner_ops callback, use it for hugetlb
pages instead of using a dedicated callback.
Since owner_ops is overlaid with lru, we need to unset owner_ops
to allow the use of lru when its isolated. At that point we know
that the reference count is elevated, will not reach 0, a
Now that we have the folio_owner_ops callback, use it for zone
device pages instead of using a dedicated callback.
Note that struct dev_pagemap (pgmap) in struct page is overlaid
with struct folio owner_ops. Therefore, make struct dev_pagemap
contain an instance of struct folio_owner_ops, to handl
Introduce struct folio_owner_ops, a method table that contains
callbacks to owners of folios that need special handling for
certain operations. For now, it only contains a callback for
folio free(), which is called immediately after the folio
refcount drops to 0.
Add a pointer to this struct overl
From: David Hildenbrand
Let's convert hugetlb_cgroup_css_offline() and
hugetlb_cgroup_move_parent() to work on folios. hugepage_activelist
contains folios, not pages.
While at it, rename page_hcg simply to hcg, removing most of the "page"
terminology.
Signed-off-by: David Hildenbrand
Signed-of
From: David Hildenbrand
Let's use a separate list head in the folio, as long as hugetlb folios are
not isolated. This way, we can reuse folio->lru for different purpose
(e.g., owner_ops) as long as they are not isolated.
Consequently, folio->lru will only be used while there is an additional
fol
From: David Hildenbrand
Now that folio_putback_hugetlb() is only called on folios that were
previously isolated through folio_isolate_hugetlb(), let's rename it to
match folio_putback_lru().
Add some kernel doc to clarify how this function is supposed to be used.
Signed-off-by: David Hildenbran
Some folios, such as hugetlb folios and zone device folios,
require special handling when the folio's reference count reaches
0, before being freed. Moreover, guest_memfd folios will likely
require special handling to notify it once a folio's reference
count reaches 0, to facilitate shared to priva
From: David Hildenbrand
Let's make the function name match "folio_isolate_lru()", and add some
kernel doc.
Signed-off-by: David Hildenbrand
Signed-off-by: Fuad Tabba
---
include/linux/hugetlb.h | 4 ++--
mm/gup.c| 2 +-
mm/hugetlb.c| 23 ---
m
On 08/11/2024 14:58, Christian König wrote:
Am 08.11.24 um 12:22 schrieb Tvrtko Ursulin:
On 07/11/2024 16:00, Tvrtko Ursulin wrote:
On 24/10/2024 13:41, Christian König wrote:
The merge function initially handled only individual fences and
arrays which in turn were created by the merge funct
On 08/11/2024 14:18, Christian König wrote:
Am 08.11.24 um 14:01 schrieb Tvrtko Ursulin:
On 08/11/2024 09:42, Christian König wrote:
The function silently assumed that signaling was already enabled for the
dma_fence_array. This meant that without enabling signaling first we
would
never see
The drm_log client will likely be merged into DRM soon. Time to clean
up some of the existing files. This series moves the existing DRM
client for fbdev emulation and its build infrastructure into clients/
subdirectories. Drm_log can then be located there as well.
The core and helper support for i
DRM drivers invoke drm_client_setup() to set up in-kernel clients.
No driver should call drm_fbdev_client_setup() directly. Therefore,
unexport the symbol and move the declaration to the internal header
drm_client_internal.h.
Signed-off-by: Thomas Zimmermann
---
.../gpu/drm/clients/drm_client_in
Move the public header file drm_client_setup.h to the clients/
subdirectory and update all drivers. No functional changes.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 2 +-
drivers/gpu/drm/arm/display/komeda/komeda_drv.c | 2 +-
drivers/gpu/drm/arm/hd
Just move some files around to keep source code well organized. Plus
fix a type in the help text of CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM. No
functional changes.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/Kconfig | 72 +-
drivers/gpu/drm/Makefile
Hi Dave and Simona,
drm-xe-fixes for 6.12-rc7. Still busier than I'd like for an rc7, but
needed particularly for LNL.
thanks,
Lucas De Marchi
drm-xe-fixes-2024-11-08:
Driver Changes:
- Fix ccs_mode setting for Xe2 and later (Balasubramani)
- Synchronize ccs_mode setting with client creation (B
Applied. Thanks! Sorry for the delay.
Alex
On Fri, Nov 8, 2024 at 10:11 AM Advait Dhamorikar
wrote:
>
> Hello,
>
> I have addressed the previous comments,
> Is there something more that I need to address in this version of the patch?
> I would appreciate feedback.
>
> Best regards,
> Advait
>
Hi,
On Fri, Nov 8, 2024 at 12:31 AM Daniel Thompson
wrote:
>
> Going forward, I'll be using my kernel.org address for upstream work.
>
> Signed-off-by: Daniel Thompson
> ---
> Daniel Thompson (2):
> MAINTAINERS: Use Daniel Thompson's korg address for backlight work
> MAINTAINERS: Use
On Fri Nov 8, 2024 at 3:44 PM CET, Heiko Stuebner wrote:
> From: Heiko Stuebner
>
> DRM_DEV_ERROR is deprecated and using dev_err_probe saves quite a number
> of lines too, so convert the error prints for the dsi-driver.
>
> Signed-off-by: Heiko Stuebner
Should this have a Fixes tag?
Because in
Hello,
I have addressed the previous comments,
Is there something more that I need to address in this version of the patch?
I would appreciate feedback.
Best regards,
Advait
On Wed, 9 Oct 2024 at 00:46, Advait Dhamorikar
wrote:
>
> Improves the coding style by updating bit-shift
> operations in
On Fri, 8 Nov 2024 15:18:38 +0100
Christian König wrote:
> > }
> > }
> >
> > dma_fence_array_clear_pending_error(array);
> > return true;
> > }
> >
> > Or if the optimisation to not walk the array when signalling is
> > already enabled is deemed important, perhaps a less thinking ind
Am 08.11.24 um 12:22 schrieb Tvrtko Ursulin:
On 07/11/2024 16:00, Tvrtko Ursulin wrote:
On 24/10/2024 13:41, Christian König wrote:
The merge function initially handled only individual fences and
arrays which in turn were created by the merge function. This allowed
to create the new array by a
On Fri, 8 Nov 2024 10:42:56 +0100
"Christian König" wrote:
> The function silently assumed that signaling was already enabled for the
> dma_fence_array. This meant that without enabling signaling first we would
> never see forward progress.
>
> Fix that by falling back to testing each individua
On 2024-11-08 15:30, Dragan Simic wrote:
On 2024-11-08 15:22, Heiko Stübner wrote:
Am Freitag, 8. November 2024, 15:13:33 CET schrieb Dragan Simic:
On 2024-11-08 15:09, Heiko Stübner wrote:
> Am Freitag, 8. November 2024, 15:05:02 CET schrieb Dragan Simic:
>> On 2024-11-08 14:56, Heiko Stübner
From: Heiko Stuebner
DRM_DEV_ERROR is deprecated and using dev_err_probe saves quite a number
of lines too, so convert the error prints for the dsi-driver.
Signed-off-by: Heiko Stuebner
---
.../gpu/drm/rockchip/dw-mipi-dsi-rockchip.c | 80 ++-
1 file changed, 26 insertions(+)
The dma_direct_alloc() allocate one page at minmium, which size is the CPU
PAGE_SIZE. while the etnaviv_iommuv2_ensure_stlb() only ask for 4KiB. The
rest memory space that beyond 4KiB gets wasted on bigger page size systems.
For example, on 16KiB CPU page size systems, we will waste the rest 12KiB.
The etnaviv_iommuv2_ensure_stlb() function have been replaced by the
etnaviv_iommuv2_ensure_stlb_new(), remove it.
Signed-off-by: Sui Jingfeng
---
drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c | 24 --
1 file changed, 24 deletions(-)
diff --git a/drivers/gpu/drm/etnaviv/etnaviv
Am 16.10.24 um 10:55 schrieb Thomas Hellström:
Initially intended for experimenting with different backup
solutions (shmem vs direct swap cache insertion), abstract
the backup destination using a virtual base class.
Also provide a sample implementation for shmem.
It feels a bit like overkill t
On 2024-11-08 15:22, Heiko Stübner wrote:
Am Freitag, 8. November 2024, 15:13:33 CET schrieb Dragan Simic:
On 2024-11-08 15:09, Heiko Stübner wrote:
> Am Freitag, 8. November 2024, 15:05:02 CET schrieb Dragan Simic:
>> On 2024-11-08 14:56, Heiko Stübner wrote:
>> > Am Freitag, 8. November 2024,
On Fri, 1 Nov 2024 02:25:09 +0200, Dmitry Baryshkov wrote:
> Replace .mode_valid() callback with .hdmi_tmds_char_rate_valid(). It is
> more generic and is used in other mode validation paths. The rate
> validation for .mode_valid() will be performed by the
> drm_bridge_connector code.
>
>
> [ ...
On Fri, 1 Nov 2024 02:25:08 +0200, Dmitry Baryshkov wrote:
> Drop manual check of the TMDS char rate in the mode_valid callback. This
> check is now being performed by the core.
>
> Reviewed-by: Chen-Yu Tsai
> Signed-off-by: Dmitry Baryshkov
>
> [ ... ]
Reviewed-by: Maxime Ripard
Thanks!
Max
On Fri, 1 Nov 2024 02:25:07 +0200, Dmitry Baryshkov wrote:
> Use new drm_bridge_connector_mode_valid() helper if there is a HDMI
> bridge in the bridge chain. This removes the need to perform TMDS char
> rate check manually in the bridge driver.
>
> Reviewed-by: Chen-Yu Tsai
>
> [ ... ]
Reviewe
On 2024-11-08 15:09, Heiko Stübner wrote:
Am Freitag, 8. November 2024, 15:05:02 CET schrieb Dragan Simic:
On 2024-11-08 14:56, Heiko Stübner wrote:
> Am Freitag, 8. November 2024, 14:53:57 CET schrieb Dragan Simic:
>> Perform a few trivial code cleanups, to make one logged message a bit
>> more
Am Freitag, 8. November 2024, 15:13:33 CET schrieb Dragan Simic:
> On 2024-11-08 15:09, Heiko Stübner wrote:
> > Am Freitag, 8. November 2024, 15:05:02 CET schrieb Dragan Simic:
> >> On 2024-11-08 14:56, Heiko Stübner wrote:
> >> > Am Freitag, 8. November 2024, 14:53:57 CET schrieb Dragan Simic:
>
On Fri, Nov 01, 2024 at 02:25:05AM +0200, Dmitry Baryshkov wrote:
> Use new drm_hdmi_connector_mode_valid() helper instead of a
> module-specific copy.
>
> Reviewed-by: Chen-Yu Tsai
> Signed-off-by: Dmitry Baryshkov
> ---
> drivers/gpu/drm/sun4i/sun4i_hdmi_enc.c | 12 +---
> 1 file chan
Hello Sebastian,
On 2024-11-08 15:08, Sebastian Reichel wrote:
On Fri, Nov 08, 2024 at 02:53:58PM +0100, Dragan Simic wrote:
Deferred driver probing shouldn't result in errors or warnings being
logged,
because their presence in the kernel log provides no value and may
actually
cause false impr
Am 08.11.24 um 14:01 schrieb Tvrtko Ursulin:
On 08/11/2024 09:42, Christian König wrote:
The function silently assumed that signaling was already enabled for the
dma_fence_array. This meant that without enabling signaling first we
would
never see forward progress.
Fix that by falling back to
Hi,
On Fri, Nov 01, 2024 at 02:25:04AM +0200, Dmitry Baryshkov wrote:
> Add drm_hdmi_connector_mode_valid(), generic helper for HDMI connectors.
> It can be either used directly or as a part of the .mode_valid callback.
>
> Signed-off-by: Dmitry Baryshkov
> ---
> drivers/gpu/drm/display/drm_hdm
On Fri, Nov 08, 2024 at 07:36:16PM +0530, Parthiban wrote:
> To add, 0x20 will be DE0 <--> LCD0 and DE1 <--> TV0. Below note (copied from
> R40) states the priority of the DE selection, which fails to work? Not sure,
> may be disabling CORE1_SCLK_GATE and CORE1_HCLK_GATE in de2-clk helps.
>
> With
Am Freitag, 8. November 2024, 15:05:02 CET schrieb Dragan Simic:
> Hello Heiko,
>
> On 2024-11-08 14:56, Heiko Stübner wrote:
> > Am Freitag, 8. November 2024, 14:53:57 CET schrieb Dragan Simic:
> >> Perform a few trivial code cleanups, to make one logged message a bit
> >> more
> >> consistent w
Hi,
On Fri, Nov 08, 2024 at 02:53:58PM +0100, Dragan Simic wrote:
> Deferred driver probing shouldn't result in errors or warnings being logged,
> because their presence in the kernel log provides no value and may actually
> cause false impression that some issues exist. Thus, let's no longer pro
Hello Heiko,
On 2024-11-08 14:56, Heiko Stübner wrote:
Am Freitag, 8. November 2024, 14:53:57 CET schrieb Dragan Simic:
Perform a few trivial code cleanups, to make one logged message a bit
more
consistent with the other logged messages by capitalizing its first
word, and
to avoid line wrappi
Hey Dragan,
Am Freitag, 8. November 2024, 14:53:57 CET schrieb Dragan Simic:
> Perform a few trivial code cleanups, to make one logged message a bit more
> consistent with the other logged messages by capitalizing its first word, and
> to avoid line wrapping by using the 100-column width better.
>
Perform a few trivial code cleanups, to make one logged message a bit more
consistent with the other logged messages by capitalizing its first word, and
to avoid line wrapping by using the 100-column width better.
No intended functional changes are introduced by these code cleanups.
Signed-off-by
Deferred driver probing shouldn't result in errors or warnings being logged,
because their presence in the kernel log provides no value and may actually
cause false impression that some issues exist. Thus, let's no longer produce
error messages when getting the dphy results in deferred probing.
T
This is a small series that makes the deferred dphy no longer emit error
messages to the kernel log, which may even be repeated multiple times, to
avoid possible false impression of some issues.
This series also performs a few small, rather trivial code cleanups, to
make the code a bit easier to r
On 08/11/2024 14:33, Thomas Zimmermann wrote:
Hi
Am 08.11.24 um 09:10 schrieb Jocelyn Falempe:
When userspace takes drm_master, the drm_client buffer is no more
visible, so drm_log shouldn't waste CPU cycle to draw on it.
Signed-off-by: Jocelyn Falempe
---
drivers/gpu/drm/drm_log.c | 10 +++
Hi
Am 08.11.24 um 09:10 schrieb Jocelyn Falempe:
When userspace takes drm_master, the drm_client buffer is no more
visible, so drm_log shouldn't waste CPU cycle to draw on it.
Signed-off-by: Jocelyn Falempe
---
drivers/gpu/drm/drm_log.c | 10 --
1 file changed, 8 insertions(+), 2 de
On Fri, Nov 08, 2024 at 11:53:57AM +, Andre Przywara wrote:
> Hi John,
Hi Andre!
> Can you say *why* this patch is needed? Is there something broken that
> needs fixing? Where does this show and why wasn't this a problem before?
Oops, that's a good point. There is currently a bug where the L
> On Nov 7, 2024, at 8:19 PM, Yu Kuai wrote:
>
> Hi,
>
> 在 2024/11/07 22:41, Chuck Lever 写道:
>> On Thu, Nov 07, 2024 at 08:57:23AM +0800, Yu Kuai wrote:
>>> Hi,
>>>
>>> 在 2024/11/06 23:19, Chuck Lever III 写道:
> On Nov 6, 2024, at 1:16 AM, Greg KH wrote:
>
> On Thu, O
1 - 100 of 128 matches
Mail list logo
