We added some locking to this function, but accidentally forgot to unlock
if zynqmp_dp_mode_configure() failed. Use a guard lock to fix it.
Fixes: a7d5eeaa57d7 ("drm: zynqmp_dp: Add locking")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/xlnx/zynqmp_dp.c | 3 +--
1 file changed, 1 insertion(
Hi Jason and David,
On Fri, 8 Nov 2024 at 19:33, David Hildenbrand wrote:
>
> 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 r
].
>
> [1] https://patchwork.freedesktop.org/patch/617470/?series=136572&rev=2
> [2] https://patchwork.freedesktop.org/patch/617471/?series=136572&rev=2
>
>
> Thanks a lot for those pointers, that is exactly what I was looking for.
>
> And yeah, it is what I feared. You
Enable the Microchip's DSI controller wrapper driver that uses
the Synopsys DesignWare MIPI DSI host controller bridge for
sam9x7 SoC family.
Signed-off-by: Manikandan Muralidharan
---
changes in v6:
- Rewrite commit message
---
arch/arm/configs/at91_dt_defconfig | 1 +
1 file changed, 1 inserti
Add the Microchip's DSI controller wrapper driver that uses
the Synopsys DesignWare MIPI DSI host controller bridge.
Signed-off-by: Manikandan Muralidharan
---
changes in v6:
- Fixed warning reported by Kernel test robot
changes in v4:
- Fixed issues reported by kernel test robot
- replaced sysc
Add the Microchip's DSI controller wrapper driver that uses the
Synopsys DesignWare MIPI DSI host controller bridge for the SAM9X7
SoC series to the MAINTAINERS entry.
Signed-off-by: Manikandan Muralidharan
---
changes in v3:
- Drop T: section
---
MAINTAINERS | 7 +++
1 file changed, 7 inser
Add the 'sam9x75-mipi-dsi' compatible binding, which describes the
Microchip's specific wrapper for the Synopsys DesignWare MIPI DSI HOST
Controller for the sam9x75 series System-on-Chip (SoC) devices.
Signed-off-by: Manikandan Muralidharan
Reviewed-by: Conor Dooley
---
changes in v5:
- Add revi
This patch series adds support for the Microchip's MIPI DSI Controller
wrapper driver that uses the Synopsys DesignWare MIPI DSI host controller
bridge for SAM9X75 SoC series.
Changelogs are available in respective patches.
Manikandan Muralidharan (4):
dt-bindings: display: bridge: add sa
From: Dave Airlie
The upper layer transfer functions expect EBUSY as a return
for when retries should be done.
Fix the AUX error translation, but also check for both errors
in a few places.
Fixes: eb284f4b3781 ("drm/nouveau/dp: Honor GSP link training retry timeouts")
Signed-off-by: Dave Airlie
From: Dave Airlie
eb284f4b3781 drm/nouveau/dp: Honor GSP link training retry timeouts
tried to fix a problem with panel retires, however it appears
the auxch also needs the same treatment, so add the same retry
wrapper around it.
This fixes some eDP panels after a suspend/resume cycle.
Fixes:
Hi,
在 2024/11/11 8:52, c...@kernel.org 写道:
From: yangerkun
[ Upstream commit 64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a ]
After we switch tmpfs dir operations from simple_dir_operations to
simple_offset_dir_operations, every rename happened will fill new dentry
to dest dir's maple tree(&SHMEM_I
Hi,
I have an update on top of what I've said ealier.
Le mercredi 06 novembre 2024 à 14:49 -0500, Nicolas Dufresne a écrit :
> Hi,
>
> Le mercredi 06 novembre 2024 à 16:53 +0100, Benjamin Gaignard a écrit :
> > + nicolas
>
> Thanks for the CC, I'm obviously watching ker...@collabora.com, I don'
/11/06 23:19, Chuck Lever III 写道:
On Nov 6, 2024, at 1:16 AM, Greg KH wrote:
On Thu, Oct 24, 2024 at 09:19:41PM +0800, Yu Kuai wrote:
From: Yu Kuai
Fix patch is patch 27, relied patches are from:
I assume patch 27 is:
libfs: fix infinite directory reads for offset dir
https
From: yangerkun
[ Upstream commit 64a7ce76fb901bf9f9c36cf5d681328fc0fd4b5a ]
After we switch tmpfs dir operations from simple_dir_operations to
simple_offset_dir_operations, every rename happened will fill new dentry
to dest dir's maple tree(&SHMEM_I(inode)->dir_offsets->mt) with a free
key star
From: Chuck Lever
[ Upstream commit 5a1a25be995e1014abd01600479915683e356f5c ]
I'm about to fix a tmpfs rename bug that requires the use of
internal simple_offset helpers that are not available in mm/shmem.c
Signed-off-by: Chuck Lever
Link: https://lore.kernel.org/r/20240415152057.4605-3-...@k
From: Chuck Lever
[ Upstream commit 7beea725a8ca412c6190090ce7c3a13b169592a1 ]
This value is used in several places, so make it a symbolic
constant.
Reviewed-by: Jan Kara
Signed-off-by: Chuck Lever
Link:
https://lore.kernel.org/r/170820142741.6328.12428356024575347885.st...@91.116.238.104.ho
From: Chuck Lever
[ Upstream commit 23cdd0eed3f1fff3af323092b0b88945a7950d8e ]
User space expects the replacement (old) directory entry to have
the same directory offset after the rename.
Suggested-by: Christian Brauner
Fixes: a2e459555c5f ("shmem: stable directory offsets")
Signed-off-by: Chu
From: Chuck Lever
[ Upstream commit ad191eb6d6942bb835a0b20b647f7c53c1d99ca4 ]
When renaming onto an existing directory entry, user space expects
the replacement entry to have the same directory offset as the
original one.
Link: https://gitlab.alpinelinux.org/alpine/aports/-/issues/15966
Fixes:
From: Chuck Lever
Address several bugs in v6.6's libfs/shmemfs, including
CVE-2024-46701.
Link:
https://lore.kernel.org/stable/976c0dd5-4337-4c7d-92c6-a38c2ec33...@oracle.com/T/#me685f54ac17ea1e39265dd5f1bb1f173c557a564
I'm still running the usual set of regression tests, but so far this
set l
From: Chuck Lever
[ Upstream commit ecba88a3b32d733d41e27973e25b2bc580f64281 ]
For simple filesystems that use directory offset mapping, rely
strictly on the directory offset map to tell when a directory has
no children.
After this patch is applied, the emptiness test holds only the RCU
read
The QCOM_SCM_SVC_MP service provides QCOM_SCM_MP_CP_SMMU_APERTURE_ID,
which is used to trigger the mapping of register banks into the SMMU
context for per-processes page tables to function (in case this isn't
statically setup by firmware).
This is necessary on e.g. QCS6490 Rb3Gen2, in order to avo
Support for per-page tables requires the SMMU aparture to be setup, on
some targets this is done statically in firmware, on others it's
expected to be requested in runtime by the driver, through a SCM call.
Marking the series as RFT, as this has been tested on a few different
modern platforms, but
Support for per-process page tables requires the SMMU aparture to be
setup such that the GPU can make updates with the SMMU. On some targets
this is done statically in firmware, on others it's expected to be
requested in runtime by the driver, through a SCM call.
One place where configuration is e
Add a helper to check if the memory stats is zero, this will be used to
check for memory accounting errors.
Signed-off-by: Yunxiang Li
Reviewed-by: Christian König
CC: dri-devel@lists.freedesktop.org
---
drivers/gpu/drm/drm_file.c | 10 ++
include/drm/drm_file.h | 1 +
2 files chan
Lankhorst
> ; Maxime Ripard ;
> Thomas Zimmermann ; David Airlie
> ; Simona Vetter ; Jani Nikula
> ; Joonas Lahtinen
> ; Tvrtko Ursulin ;
> Weil, Oren jer ; linux-...@lists.infradead.org; dri-
> de...@lists.freedesktop.org; intel-...@lists.freedesktop.org; linux-
> ker...@vger
Hi,
Gentle ping.
The patch link is: [PATCH 0/2] drm/amd/display: Fix Null Pointer
Dereference Issues - Zicheng Qu (kernel.org)
<https://lore.kernel.org/linux-kernel/20241105140137.2465572-1-quzich...@huawei.com/>
Best regards,
Zicheng
On 2024/11/5 22:01, Zicheng Qu wrote:
Hi all,
Hi Heiko,
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
> ---
> .../gpu/drm/rockchip/d
Hello Heiko,
Thanks for the patch. Please, see a couple of comments below.
On 2024-11-08 15:44, 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
On Mon, 21 Oct 2024 15:28:06 +0800, Andy Yan wrote:
> From: Andy Yan
>
> The 'state' can't be NULL, we should check crtc_state.
>
> Fix warning:
> drivers/gpu/drm/rockchip/rockchip_drm_vop.c:1096
> vop_plane_atomic_async_check() warn: variable dereferenced before check
> 'state' (see line 1077)
On Tue, 5 Nov 2024 14:38:16 +0100, Thomas Zimmermann wrote:
> The code for detecting and updating the connector status in
> cdn_dp_pd_event_work() has a number of problems.
>
> - It does not aquire the locks to call the detect helper and update
> the connector status. These are struct drm_mode_con
On Fri, 01 Nov 2024 19:01:17 +, Piotr Zalewski wrote:
> Add support for gamma LUT in VOP2 driver. The implementation was inspired
> by one found in VOP1 driver. Blue and red channels in gamma LUT register
> write were swapped with respect to how gamma LUT values are written in
> VOP1. Gamma LUT
On Mon, 28 Oct 2024 15:41:34 +0800, Andy Yan wrote:
> From: Andy Yan
>
> Demote the error message to drm_dbg_kms to only print the message
> if the respective debug messages are enabled.
>
>
Applied, thanks!
[1/1] drm/rockchip: vop2: Don't spam logs in atomic update
commit: 712ec5de382d
: 929beafbe7acce3267c06115e13e03ff6e50548a
patch link:
https://lore.kernel.org/r/20241109-hdmi-mode-valid-v3-3-5348c2368076%40linaro.org
patch subject: [PATCH v3 3/7] drm/vc4: use drm_hdmi_connector_mode_valid()
config: x86_64-allyesconfig
(https://download.01.org/0day-ci/archive/20241110/202411100659.t6wkbfbi
: 929beafbe7acce3267c06115e13e03ff6e50548a
patch link:
https://lore.kernel.org/r/20241109-hdmi-mode-valid-v3-3-5348c2368076%40linaro.org
patch subject: [PATCH v3 3/7] drm/vc4: use drm_hdmi_connector_mode_valid()
config: i386-allmodconfig
(https://download.01.org/0day-ci/archive/20241110/202411100456.0jcsax2b
On Sat, Nov 09, 2024 at 09:27:36AM +0200, Dmitry Baryshkov wrote:
> 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 righ
remove_new(). As
.remove() and .remove_new() have the same prototypes, conversion is done
by just changing the structure member name in the driver initializer.
Signed-off-by: Uwe Kleine-König
---
Hello,
I did a single patch for all of drivers/video/backlight. While I usually
prefer to do one logi
The motivation for this series comes from pending UMD submission work by
AMD [1], ARM [3], and the Xe team, who are also beginning to look at
this. Sima has suggested [4] some common driver preemptive fences and
semantics, which we all agree on. This is the first attempt to implement
them, based on
Use the new DMA_RESV_USAGE_PREEMPT dma-resv slots in Xe for preemptive
fences, and call them in dma-resv/scheduler rather than open-coding the
enabling of signaling before waiting.
Cc: Dave Airlie
Cc: Simona Vetter
Cc: Christian Koenig
Signed-off-by: Matthew Brost
---
drivers/gpu/drm/xe/xe_bo
Update drm_sched_job_add_dependency to detect dma_fence_preempt and
correctly store it in the dedicated preemptive fence xarray ensuring
preempt fence semantics are followed.
Cc: Philipp Stanner
Cc: Danilo Krummrich
Cc: Luben Tuikov
Cc: Dave Airlie
Cc: Simona Vetter
Cc: Christian Koenig
Sign
Use the dma_fence_preempt base class in Xe instead of open-coding the
preemption implementation.
Cc: Dave Airlie
Cc: Simona Vetter
Cc: Christian Koenig
Signed-off-by: Matthew Brost
---
drivers/gpu/drm/xe/xe_guc_submit.c | 3 +
drivers/gpu/drm/xe/xe_hw_engine_group.c | 4 +-
dri
Follow the semantics of DMA_RESV_USAGE_PREEMPT in the DRM scheduler by
storing preemptive fences in a dedicated xarray, which is waited on
after all other fences are signaled. In addition to following these
semantics, pipeline preemptive fences by enabling signaling on all
preemptive fences before
Add a dma_fence_preempt base class with driver ops to implement
preemption, based on the existing Xe preemptive fence implementation.
Cc: Dave Airlie
Cc: Simona Vetter
Cc: Christian Koenig
Signed-off-by: Matthew Brost
---
drivers/dma-buf/Makefile| 2 +-
drivers/dma-buf/dma-fence
Add a new DMA reservation slot, which is the highest priority and used
exclusively for preemptive fences. The semantics of this slot require
that all other fences in other slots must be signaled before any fences
in the preemptive slot enable signaling. These semantics exist to avoid
deadlocks duri
ov 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:
>>>>>>
Make the Lontium LT9611 DSI-to-HDMI bridge driver use the DRM HDMI Codec
framework. This enables programming of Audio InfoFrames using the HDMI
Connector interface and also enables support for the missing features,
including the ELD retrieval and better hotplug support.
Signed-off-by: Dmitry Barys
Extend drm_bridge_connector code to read the EDID and use it to update
connector status if the bridge chain implements HDMI bridge. Performing
it from the generic location minimizes individual bridge's code and
enforces standard behaviour from all corresponding drivers.
Signed-off-by: Dmitry Barys
The HDMI Connectors need to perform a variety of tasks when the HDMI
connector state changes. Such tasks include setting or invalidating CEC
address, notifying HDMI codec driver, updating scrambler data, etc.
Implementing such tasks in a driver-specific callbacks is error prone.
Start implementing
Add necessary glue code to be able to use new HDMI codec framework from
the DRM bridge drivers. The drm_bridge implements a limited set of the
hdmi_codec_ops interface, with the functions accepting both
drm_connector and drm_bridge instead of just a generic void pointer.
This framework is integrat
Several DRM drivers implement HDMI codec support (despite its name it
applies to both HDMI and DisplayPort drivers). Implement generic
framework to be used by these drivers. This removes a requirement to
implement get_eld() callback and provides default implementation for
codec's plug handling.
Th
The no_capture_mute flag might differ from platform to platform,
especially in the case of the wrapping implementations, like the
upcoming DRM HDMI Codec framework. Move the flag next to all other flags
in struct hdmi_codec_pdata.
Acked-by: Mark Brown
Signed-off-by: Dmitry Baryshkov
---
drivers
The upcoming DRM connector HDMI codec implementation is going to use
codec-specific data in the .get_dai_id to get drm_connector. Pass data
to the callback, as it is done with other hdmi_codec_ops callbacks.
Acked-by: Mark Brown
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/bridge/adv7511
While porting lt9611 DSI-to-HDMI bridge driver to use HDMI Connector
framework, I stumbled upon an issue while handling the Audio InfoFrames.
The HDMI codec callbacks weren't receiving the drm_atomic_state, so
there was no simple way to get the drm_connector that stayed at the end
of the bridge cha
Use new drm_hdmi_connector_mode_valid() helper instead of a
module-specific copy.
Reviewed-by: Chen-Yu Tsai
Acked-by: Dave Stevenson
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/vc4/vc4_hdmi.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/vc4/vc4
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.
Reviewed-by: Chen-Yu Tsai
Reviewed-by: Maxime Ripard
Signed-off-by: Dmitry Ba
Replace sun4i_hdmi_connector_atomic_check(), which performs just TMDS
char rate check, with drm_atomic_helper_connector_hdmi_check(), which
performs additional checks basing on the HDMI Connector's state.
Suggested-by: Maxime Ripard
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/sun4i/sun4
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_hdmi_state_helper.c| 21 +++
drivers/gpu/drm/tests/drm_hdmi_state_helper_test.c |
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
Reviewed-by: Maxime Ripard
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/bridge/lontium-lt9611.c | 4 +---
1 file changed, 1 insertion(+), 3 deleti
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 changed, 1 insertion(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/sun4i/sun4i_hdm
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
Reviewed-by: Maxime Ripard
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/display/
Several HDMI drivers have common code pice in the .mode_valid function
that validates RGB / 8bpc rate using the TMDS char rate callbacks.
Move this code piece to the common helper and remove the need to perform
this check manually. In case of DRM_BRIDGE_OP_HDMI bridges, they can
skip the check in
On Fri, Nov 08, 2024 at 08:04:36PM +, Mithil Bavishi wrote:
> 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/
On 08/11/2024 21:04, Mithil Bavishi wrote:
> Add samsung-espresso10 codename for the 10 inch variant
>
> Signed-off-by: Mithil Bavishi
> ---
> Documentation/devicetree/bindings/arm/ti/omap.yaml | 1 +
Squash it. Really, these are just one liners for similar devices.
Best regards,
Krzysztof
On Fri, Nov 08, 2024 at 08:04:34PM +, Mithil Bavishi wrote:
> The LTN101AL03 is a 10.1 inch 800x1280, 24 bit, VESA Compatible, TFT display
> panel
>
> Signed-off-by: Mithil Bavishi
> ---
Squash it with previous patch. Each of such trivial one-liners for
similar device is rev
On Fri, Nov 08, 2024 at 08:04:33PM +, Mithil Bavishi wrote:
> The LTN070NL01 is a 7.0 inch 1024x600, 24 bit, VESA Compatible, TFT display
> panel
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/
On Fri, Nov 08, 2024 at 08:04:32PM +, Mithil Bavishi wrote:
> 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(+)
On Fri, Nov 08, 2024 at 08:04:31PM +, Mithil Bavishi wrote:
> 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(+)
Acked-by: Krzysz
Hi Manikandan,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on drm-misc/drm-misc-next linus/master v6.12-rc6
next-20241108]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting
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
gt; > .get_modes = sun4i_hdmi_get_modes,
> > };
>
> It's only slightly related, but the atomic_check implementation that
> will be the last (direct) user of sun4i_hdmi_clock_valid is wrong and
> doesn't call drm_atomic_helper_connector_hdmi_check
I can send a patch fixing this, but I can't test it.
--
With best wishes
Dmitry
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:
1:16 AM, Greg KH wrote:
On Thu, Oct 24, 2024 at 09:19:41PM +0800, Yu Kuai wrote:
From: Yu Kuai
Fix patch is patch 27, relied patches are from:
I assume patch 27 is:
libfs: fix infinite directory reads for offset dir
https://lore.kernel.org/stable/20241024132225.2271667-12-yuku
, Oct 24, 2024 at 09:19:41PM +0800, Yu Kuai wrote:
From: Yu Kuai
Fix patch is patch 27, relied patches are from:
I assume patch 27 is:
libfs: fix infinite directory reads for offset dir
https://lore.kernel.org/stable/20241024132225.2271667-12-yuku...@huaweicloud.com/
I don't think the
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 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 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
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
401 - 500 of 60780 matches
Mail list logo
