Hi Marek,
On Mon, 22 Sept 2025 at 20:58, Marek Vasut
wrote:
> Call mipi_dsi_pixel_format_to_bpp() once in rcar_mipi_dsi_set_display_timing()
> and store the value into a variable. This slightly simplifies the code.
>
> No functional change.
>
> Signed-off-by: Marek Vasut
Thanks for your patch!
cc Ruben
Am 22.09.25 um 19:43 schrieb Mehdi Ben Hadj Khelifa:
Replace kmalloc with kmalloc array in drm/gud/gud_pipe.c since the
calculation inside kmalloc is dynamic "width * height" and added
u_char as the size of each element.
Signed-off-by: Mehdi Ben Hadj Khelifa
---
drivers/gpu/drm/gud/
From: Hermes Wu
When connect to device that can only training done by step training,
skip auto training when link training restart before unplug device.
The driver performs a full cycle of attempting auto link training and
then manual link training on each modeset. Save time by skipping the
auto
Hi Christian,
>
> Hi guys,
>
> On 22.09.25 08:59, Kasireddy, Vivek wrote:
> > Hi Jason,
> >
> >> Subject: Re: [PATCH v4 1/5] PCI/P2PDMA: Don't enforce ACS check for
> device
> >> functions of Intel GPUs
> >>
> >> On Fri, Sep 19, 2025 at 06:22:45AM +, Kasireddy, Vivek wrote:
> In this ca
Add API dw_hdmi_set_sample_iec958() for IEC958 format because audio device
driver needs IEC958 information to configure this specific setting.
Signed-off-by: Shengjiu Wang
Acked-by: Liu Ying
Tested-by: Alexander Stein
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi-gp-audio.c | 5 +
drivers/g
The HDMI TX Parallel Audio Interface (HTX_PAI) is a digital module that
acts as the bridge between the Audio Subsystem to the HDMI TX Controller.
This IP block is found in the HDMI subsystem of the i.MX8MP SoC.
Data received from the audio subsystem can have an arbitrary component
ordering. The HT
Add API dw_hdmi_to_plat_data() to fetch plat_data because audio device
driver needs it to enable(disable)_audio().
Signed-off-by: Shengjiu Wang
Acked-by: Liu Ying
Tested-by: Alexander Stein
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 6 ++
include/drm/bridge/dw_hdmi.h | 2
The IEC958 subframe format SNDRV_PCM_FMTBIT_IEC958_SUBFRAME_LE are used
in HDMI and DisplayPort to describe the audio stream, but hardware device
may need to reorder the IEC958 bits for internal transmission, so need
these standard bits definitions for IEC958 subframe format.
Signed-off-by: Shengj
Add binding for the i.MX8MP HDMI parallel Audio interface block.
The HDMI TX Parallel Audio Interface (HTX_PAI) is a digital module that
acts as the bridge between the Audio Subsystem to the HDMI TX Controller.
This IP block is found in the HDMI subsystem of the i.MX8MP SoC.
Aud2htx module in Aud
The HDMI TX Parallel Audio Interface (HTX_PAI) is a digital module that
acts as the bridge between the Audio Subsystem to the HDMI TX Controller.
Add HDMI PAI driver on i.MX8MP to make HDMI audio function fully work.
changes in v7:
- add back the mutex which removed in v6
- add Tested-by tag from
On 2025-09-23 at 05:10 +1000, Timur Tabi wrote...
> On Mon, 2025-09-22 at 21:30 +1000, Alistair Popple wrote:
>
>
> > +const GSP_REGISTRY_NUM_ENTRIES: usize = 2;
> > +struct RegistryEntry {
> > +key: &'static str,
> > +value: u32,
> > +}
>
> Probably should add a comment saying that alt
On Tue, Sep 23, 2025 at 11:40:33AM +0800, Chaoyi Chen wrote:
> On 9/23/2025 11:17 AM, Dmitry Baryshkov wrote:
>
> > On Tue, Sep 23, 2025 at 09:53:06AM +0800, Chaoyi Chen wrote:
> > > Hi Dmitry,
> > >
> > > On 9/23/2025 9:12 AM, Dmitry Baryshkov wrote:
> > > > On Mon, Sep 22, 2025 at 09:20:34AM +0
On 2025-09-23 at 11:07 +1000, John Hubbard wrote...
> On 9/22/25 12:12 PM, Timur Tabi wrote:
> > On Mon, 2025-09-22 at 21:30 +1000, Alistair Popple wrote:
> >> +
> >> + /// Check if the RISC-V core is active.
> >> + ///
> >> + /// Returns `true` if the RISC-V core is active, `false` other
On 2025-09-23 at 12:16 +1000, John Hubbard wrote...
> On 9/22/25 9:08 AM, Danilo Krummrich wrote:
> > On 9/22/25 1:30 PM, Alistair Popple wrote:
> >> +// SAFETY: No DMA allocations have been made yet
> >
> > It's not really about DMA allocations that have been made previously, there
> >
On Mon, Sep 22, 2025 at 08:13:00AM -0700, Rob Clark wrote:
> On Fri, Sep 19, 2025 at 11:35 AM Dmitry Baryshkov
> wrote:
> >
> > On Fri, Sep 19, 2025 at 10:24:31PM +0800, Xiangxu Yin wrote:
> > > QCS615 platform requires non-default logical-to-physical lane mapping due
> > > to its unique hardware
On 9/19/25 23:26, Zi Yan wrote:
> On 19 Sep 2025, at 1:01, Balbir Singh wrote:
>
>> On 9/18/25 12:49, Zi Yan wrote:
>>> On 16 Sep 2025, at 8:21, Balbir Singh wrote:
>>>
Add routines to support allocation of large order zone device folios
and helper functions for zone device folios, to ch
On Mon, 2025-09-22 at 18:07 -0700, John Hubbard wrote:
> In the spirit of the current "soul" of patchsets, which is "get
> GPU firmware running on Ampere/Ada"), I think let's defer the HALs
> until the first patchset that needs them.
Fair enough, but maybe this patchset should make it clear that i
On 9/23/25 12:09, Zi Yan wrote:
> On 22 Sep 2025, at 21:50, Balbir Singh wrote:
>
>> On 9/23/25 07:09, Zi Yan wrote:
>>> On 16 Sep 2025, at 8:21, Balbir Singh wrote:
>>>
Add support for splitting device-private THP folios, enabling fallback
to smaller page sizes when large page allocatio
On 9/18/25 02:40, Pekka Paalanen wrote:
On Tue, 16 Sep 2025 17:01:07 -0600
Alex Hung wrote:
On 8/26/25 03:03, Pekka Paalanen wrote:
On Thu, 21 Aug 2025 11:54:32 -0600
Alex Hung wrote:
On 8/21/25 06:23, Xaver Hugl wrote:
We user space folks have been convinced at this point that the
On 9/23/25 12:23, Zi Yan wrote:
> On 16 Sep 2025, at 8:21, Balbir Singh wrote:
>
>> Extend migrate_vma_collect_pmd() to handle partially mapped large folios
>> that require splitting before migration can proceed.
>>
>> During PTE walk in the collection phase, if a large folio is only
>> partially
On Tue, 16 Sep 2025 20:11:03 +0800, Xiangxu Yin wrote:
> Add DisplayPort controller binding for Qualcomm SM6150 SoC.
> SM6150 uses the same controller IP as SM8150.
> Declare 'qcom,sm6150-dp' as a fallback compatible to
> 'qcom,sm8150-dp' and 'qcom,sm8350-dp' for consistency with existing
> bindi
On 9/23/2025 7:38 AM, Dmitry Baryshkov wrote:
> On Mon, Sep 22, 2025 at 07:28:17PM +0800, Xiangxu Yin wrote:
>> On 9/22/2025 5:45 PM, Dmitry Baryshkov wrote:
>>> On Mon, Sep 22, 2025 at 02:58:17PM +0800, Xiangxu Yin wrote:
On 9/20/2025 2:41 AM, Dmitry Baryshkov wrote:
> On Fri, Sep 19, 2
On 9/23/2025 11:17 AM, Dmitry Baryshkov wrote:
On Tue, Sep 23, 2025 at 09:53:06AM +0800, Chaoyi Chen wrote:
Hi Dmitry,
On 9/23/2025 9:12 AM, Dmitry Baryshkov wrote:
On Mon, Sep 22, 2025 at 09:20:34AM +0800, Chaoyi Chen wrote:
From: Chaoyi Chen
The RK3399 SoC integrates two USB/DP combo PHY
On 9/23/2025 11:22 AM, Dmitry Baryshkov wrote:
On Tue, Sep 23, 2025 at 10:09:38AM +0800, Chaoyi Chen wrote:
On 9/23/2025 9:50 AM, Dmitry Baryshkov wrote:
On Mon, Sep 22, 2025 at 09:20:37AM +0800, Chaoyi Chen wrote:
From: Chaoyi Chen
The RK3399 has two USB/DP combo PHY and one CDN-DP contro
On Tue, Sep 23, 2025 at 10:09:38AM +0800, Chaoyi Chen wrote:
> On 9/23/2025 9:50 AM, Dmitry Baryshkov wrote:
>
> > On Mon, Sep 22, 2025 at 09:20:37AM +0800, Chaoyi Chen wrote:
> > > From: Chaoyi Chen
> > >
> > > The RK3399 has two USB/DP combo PHY and one CDN-DP controller. And
> > > the CDN-DP
On Tue, Sep 23, 2025 at 09:53:06AM +0800, Chaoyi Chen wrote:
> Hi Dmitry,
>
> On 9/23/2025 9:12 AM, Dmitry Baryshkov wrote:
> > On Mon, Sep 22, 2025 at 09:20:34AM +0800, Chaoyi Chen wrote:
> > > From: Chaoyi Chen
> > >
> > > The RK3399 SoC integrates two USB/DP combo PHYs, each of which
> > > su
On Tue, Sep 23, 2025 at 09:34:39AM +0800, Chaoyi Chen wrote:
> On 9/23/2025 9:10 AM, Dmitry Baryshkov wrote:
>
> > On Mon, Sep 22, 2025 at 09:20:33AM +0800, Chaoyi Chen wrote:
> > > From: Chaoyi Chen
> > >
> > > Add default DRM AUX HPD bridge device when register DisplayPort
> > > altmode. That
On 9/23/2025 9:50 AM, Dmitry Baryshkov wrote:
On Mon, Sep 22, 2025 at 09:20:37AM +0800, Chaoyi Chen wrote:
From: Chaoyi Chen
The RK3399 has two USB/DP combo PHY and one CDN-DP controller. And
the CDN-DP can be switched to output to one of the PHYs. If both ports
are plugged into DP, DP will s
On 9/23/25 07:09, Zi Yan wrote:
> On 16 Sep 2025, at 8:21, Balbir Singh wrote:
>
>> Add support for splitting device-private THP folios, enabling fallback
>> to smaller page sizes when large page allocation or migration fails.
>>
>> Key changes:
>> - split_huge_pmd(): Handle device-private PMD ent
On Tue, Sep 23, 2025 at 09:30:05AM +0800, Icenowy Zheng wrote:
> 在 2025-09-23星期二的 09:11 +0800，Icenowy Zheng写道：
> > 在 2025-09-23星期二的 04:00 +0300，Dmitry Baryshkov写道：
> > > On Sun, Sep 21, 2025 at 04:34:43PM +0800, Icenowy Zheng wrote:
> > > > T-Head TH1520 SoC contains a Synopsys DesignWare HDMI cont
Add a helper to get LayerBlend secondary input selection. This is
needed by disabling CRTC at boot in an upcoming commit which tries
to get the selection.
Reviewed-by: Frank Li
Signed-off-by: Liu Ying
---
v2:
- Collect Frank's R-b tag.
---
drivers/gpu/drm/imx/dc/dc-lb.c | 21 ++
Add a helper to get ExtDst source selection. This is needed by
disabling CRTC at boot in an upcoming commit which tries to get
the source selection.
Reviewed-by: Frank Li
Signed-off-by: Liu Ying
---
v2:
- Collect Frank's R-b tag.
---
drivers/gpu/drm/imx/dc/dc-ed.c | 26
Add i.MX8qxp prefetch engine DT binding files to
'DRM DRIVERS FOR FREESCALE IMX8 DISPLAY CONTROLLER' section.
Reviewed-by: Frank Li
Signed-off-by: Liu Ying
---
v2:
- Collect Frank's R-b tag.
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
0
Display Prefetch Resolve Gasket(PRG) is a part of a FetchUnit's
prefetch engine. It sits between a Display Prefetch Resolve
Channel(DPRC) and a FetchUnit. Add a platform driver to support
the PRG.
Reviewed-by: Frank Li
Signed-off-by: Liu Ying
---
v2:
- Manage clocks with bulk interfaces. (Fra
Add bindings for i.MX8qxp/qm Display Prefetch Resolve Channel.
Reviewed-by: Rob Herring
Signed-off-by: Liu Ying
---
Changed commit message to use imperative mood.
---
.../bindings/display/imx/fsl,imx8qxp-dprc.yaml | 100 +
1 file changed, 100 insertions(+)
diff --git
a
river.
Patch 14 uses prefetch engine in imx8-dc KMS driver.
[1] https://lore.kernel.org/lkml/20201207165945.ga430...@robh.at.kernel.org/
[2] https://lore.kernel.org/lkml/20201207170206.ga434...@robh.at.kernel.org/
Signed-off-by: Liu Ying
---
Changes in v2:
- Rebase the patch series onto next-202
On 9/22/2025 6:01 PM, Dmitry Baryshkov wrote:
On Mon, Sep 22, 2025 at 09:20:36AM +0800, Chaoyi Chen wrote:
From: Chaoyi Chen
This patch add support for get PHY lane info without help of extcon.
There is no extcon needed if the Type-C controller is present. In this
case, the lane info can be
On 9/23/2025 9:10 AM, Dmitry Baryshkov wrote:
On Mon, Sep 22, 2025 at 09:20:33AM +0800, Chaoyi Chen wrote:
From: Chaoyi Chen
Add default DRM AUX HPD bridge device when register DisplayPort
altmode. That makes it redundant for each Type-C driver to implement
a similar registration process in e
On Mon, Sep 22, 2025 at 11:01 AM Liu Ying wrote:
>
> On 09/10/2025, Shengjiu Wang wrote:
> > Hi
> >
> > On Tue, Sep 9, 2025 at 2:39 PM Maxime Ripard wrote:
> >>
> >> Hi,
> >>
> >> On Wed, Sep 03, 2025 at 06:41:05PM +0800, Shengjiu Wang wrote:
> >>> On Tue, Sep 2, 2025 at 12:52 AM Luca Ceresoli
On Mon, Sep 22, 2025 at 09:20:34AM +0800, Chaoyi Chen wrote:
> From: Chaoyi Chen
>
> The RK3399 SoC integrates two USB/DP combo PHYs, each of which
> supports software-configurable pin mapping and DisplayPort lane
> assignment. These capabilities enable the PHY itself to handle both
> mode switch
在 2025-09-23星期二的 03:53 +0300，Dmitry Baryshkov写道：
> On Sun, Sep 21, 2025 at 04:34:41PM +0800, Icenowy Zheng wrote:
> > This is a from-scratch driver targeting Verisilicon DC-series
> > display
> > controllers, which feature self-identification functionality like
> > their
> > GC-series GPUs.
> >
>
On 9/22/25 12:12 PM, Timur Tabi wrote:
> On Mon, 2025-09-22 at 21:30 +1000, Alistair Popple wrote:
>> +
>> + /// Check if the RISC-V core is active.
>> + ///
>> + /// Returns `true` if the RISC-V core is active, `false` otherwise.
>> + #[expect(unused)]
>> + pub(crate) fn is_riscv_ac
On Sun, Sep 21, 2025 at 04:34:43PM +0800, Icenowy Zheng wrote:
> T-Head TH1520 SoC contains a Synopsys DesignWare HDMI controller (paired
> with DesignWare HDMI TX PHY Gen2) that takes the "DP" output from the
> display controller.
>
> Add a driver for this controller utilizing the common DesignWa
On Sun, Sep 21, 2025 at 04:34:41PM +0800, Icenowy Zheng wrote:
> This is a from-scratch driver targeting Verisilicon DC-series display
> controllers, which feature self-identification functionality like their
> GC-series GPUs.
>
> Only DC8200 is being supported now, and only the main framebuffer i
return MODE_CLOCK_HIGH;
>
> /*
>
> ---
> base-commit: b5bad77e1e3c7249e4c0c88f98477e1ee7669b63
> change-id: 20250922-modeclk-fix-a870375d9960
>
> Best regards,
> --
> Jessica Zhang
>
--
With best wishes
Dmitry
Introduce TXVMVPRMSET0R_BPP_MASK macro and use FIELD_PREP() to generate
appropriate bitfield from mask and value without bitshift, assign this
value into vprmset0r. Remove TXVMVPRMSET0R_CSPC_RGB which is never used,
replace it with code comment next to TXVMVPRMSET0R_CSPC_YCbCr.
Replace (mode->flag
On 16 Sep 2025, at 8:21, Balbir Singh wrote:
> Add support for splitting device-private THP folios, enabling fallback
> to smaller page sizes when large page allocation or migration fails.
>
> Key changes:
> - split_huge_pmd(): Handle device-private PMD entries during splitting
> - Preserve RMAP_E
On Sun, Sep 21, 2025 at 04:34:40PM +0800, Icenowy Zheng wrote:
> Verisilicon has a series of display controllers prefixed with DC and
> with self-identification facility like their GC series GPUs.
>
> Add a device tree binding for it.
>
> Depends on the specific DC model, it can have either one o
On Sun, 21 Sep 2025 16:34:39 +0800, Icenowy Zheng wrote:
> VeriSilicon is a Silicon IP vendor, which is the current owner of
> Vivante series video-related IPs and Hantro series video codec IPs.
>
> Add a vendor prefix for this company.
>
> Signed-off-by: Icenowy Zheng
> ---
> No changes in v2
On 16 Sep 2025, at 8:21, Balbir Singh wrote:
> Add device-private THP support to reverse mapping infrastructure, enabling
> proper handling during migration and walk operations.
>
> The key changes are:
> - add_migration_pmd()/remove_migration_pmd(): Handle device-private
> entries during folio
On Fri, 19 Sep 2025 22:24:18 +0800, Xiangxu Yin wrote:
> Add device tree binding documentation for the Qualcomm QMP USB3+DP PHY
> on QCS615 Platform. This PHY supports both USB3 and DP functionality
> over USB-C, with PHY mode switching capability. It does not support
> combo mode.
>
> Signed-of
On Mon, 15 Sep 2025 11:51:23 -0400, Frank Li wrote:
> Add innolux,n133hse-ea1 13.3" TFT LCD panel and nlt,nl12880bc20-spwg-24
> 12.1" WXGA (1280 x 800) LVDS TFT LCD panel.
>
> Fix below CHECK_DTBS warnings:
> arch/arm/boot/dts/nxp/imx/imx6q-novena.dtb: /panel: failed to match any
> schema with
On 22.09.25 15:27, Jason Gunthorpe wrote:
> On Mon, Sep 22, 2025 at 03:20:49PM +0200, Christian König wrote:
>
>> At least on AMD GPUs when you want to have a DMA-buf for a specific
>> part of the VFs resources then you ask the hypervisor driver
>> managing the PF for that and not the VFIO driver.
On Mon, 2025-09-22 at 21:30 +1000, Alistair Popple wrote:
> +
> + /// Check if the RISC-V core is active.
> + ///
> + /// Returns `true` if the RISC-V core is active, `false` otherwise.
> + #[expect(unused)]
> + pub(crate) fn is_riscv_active(&self, bar: &Bar0) -> Result {
> +
Replace kmalloc -> kmalloc_array in drm/amd/amdgpu/amdgpu_ras.c .
As per said in the Documentation/process/deprecated.rst, dynamic size
calculation should not be performed in memory allocator function
arguments due to the risk of overflow.
Signed-off-by: Moktar SELLAMI
---
drivers/gpu/drm/amd/a
From: David Laight
[ Upstream commit 495bba17cdf95e9703af1b8ef773c55ef0dfe703 ]
Always pass a 'type' through to __clamp_once(), pass '__auto_type' from
clamp() itself.
The expansion of __types_ok3() is reasonable so it isn't worth the added
complexity of avoiding it when a fixed type is used fo
From: Linus Torvalds
[ Upstream commit dc1c8034e31b14a2e5e212104ec508aec44ce1b9 ]
Now that we no longer have any C constant expression contexts (ie array
size declarations or static initializers) that use min() or max(), we
can simpify the implementation by not having to worry about the result
s
在 2025/9/22 14:31, Thomas Zimmermann 写道:
Hi
Am 05.09.25 um 04:43 schrieb Zizhi Wo:
[BUG]
Recently, we encountered a KASAN warning as follows:
kasan_report+0xaf/0xe0 mm/kasan/report.c:588
fb_pad_aligned_buffer+0x12f/0x150 drivers/video/fbdev/core/fbmem.c:116
ccw_putcs_aligned drivers/video/f
From: Alexandr Sapozhnikov
Return value of function 'drm_vma_node_allow', called
at i915_gem_mman.c:670, is not checked, but it is usually
checked for this function
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Signed-off-by: Alexandr Sapozhnikov
---
drivers/gpu/drm/i915
From: Linus Torvalds
[ Upstream commit 4477b39c32fdc03363affef4b11d48391e6dc9ff ]
Commit 3a7e02c040b1 ("minmax: avoid overly complicated constant
expressions in VM code") added the simpler MIN_T/MAX_T macros in order
to avoid some excessive expansion from the rather complicated regular
min/max m
From: David Laight
[ Upstream commit 2b97aaf74ed534fb838d09867d09a3ca5d795208 ]
The bodies of __signed_type_use() and __unsigned_type_use() are much the
same size as their names - so put the bodies in the only line that expands
them.
Similarly __signed_type() is defined separately for 64bit and
From: David Laight
[ Upstream commit c3939872ee4a6b8bdcd0e813c66823b31e6e26f7 ]
At some point the definitions for clamp() got added in the middle of the
ones for min() and max(). Re-order the definitions so they are more
sensibly grouped.
Link:
https://lkml.kernel.org/r/8bb285818e4846469121c8
From: David Laight
[ Upstream commit a5743f32baec4728711bbc01d6ac2b33d4c67040 ]
Use BUILD_BUG_ON_MSG(statically_true(ulo > uhi), ...) for the sanity check
of the bounds in clamp(). Gives better error coverage and one less
expansion of the arguments.
Link:
https://lkml.kernel.org/r/34d53778977
This series backports 15 patches to update minmax.h in the 6.6.y branch,
aligning it with v6.17-rc7.
The ultimate goal is to synchronize all longterm branches so that they
include the full set of minmax.h changes.
The key motivation is to bring in commit d03eba99f5bf ("minmax: allow
min()/max()/c
> On Sun, Sep 21, 2025 at 09:37:02PM +, Farber, Eliav wrote:
> > > On Fri, Sep 19, 2025 at 10:17:00AM +, Eliav Farber wrote:
> > > > This series includes a total of 27 patches, to align minmax.h of
> > > > v5.15.y with v6.17-rc6.
> > > >
> > > > The set consists of 24 commits that directly
From: David Laight
[ Upstream commit 10666e99204818ef45c702469488353b5bb09ec7 ]
- Change three to several.
- Remove the comment about retaining constant expressions, no longer true.
- Realign to nearer 80 columns and break on major punctiation.
- Add a leading comment to the block before __signe
From: David Laight
[ Upstream commit 71ee9b16251ea4bf7c1fe222517c82bdb3220acc ]
Patch series "minmax.h: Cleanups and minor optimisations".
Some tidyups and minor changes to minmax.h.
This patch (of 7):
Link:
https://lkml.kernel.org/r/c50365d214e04f9ba256d417c8beb...@acums.aculab.com
Link:
h
From: Linus Torvalds
[ Upstream commit 3a7e02c040b130b5545e4b115aada7bacd80a2b6 ]
The minmax infrastructure is overkill for simple constants, and can
cause huge expansions because those simple constants are then used by
other things.
For example, 'pageblock_order' is a core VM constant, but bec
From: Linus Torvalds
[ Upstream commit cb04e8b1d2f24c4c2c92f7b7529031fc35a16fed ]
We only had a couple of array[] declarations, and changing them to just
use 'MAX()' instead of 'max()' fixes the issue.
This will allow us to simplify our min/max macros enormously, since they
can now unconditiona
From: Linus Torvalds
[ Upstream commit 22f5468731491e53356ba7c028f0fdea20b18e2c ]
This clarifies the rules for min()/max()/clamp() type checking and makes
them a much more efficient macro expansion.
In particular, we now look at the type and range of the inputs to see
whether they work together
From: Linus Torvalds
[ Upstream commit 1a251f52cfdc417c84411a056bc142cbd77baef4 ]
This just standardizes the use of MIN() and MAX() macros, with the very
traditional semantics. The goal is to use these for C constant
expressions and for top-level / static initializers, and so be able to
simplif
On Mon, 2025-09-22 at 21:30 +1000, Alistair Popple wrote:
> /// Creates a self-mapping page table for `obj` at its beginning.
> -fn create_pte_array(obj: &mut CoherentAllocation) {
> +fn create_pte_array(obj: &mut CoherentAllocation,
> skip: usize) {
Please add documentation for the 'skip' param
Hi!
> + led-controller@45 {
> + compatible = "awinic,aw2013";
> + reg = <0x45>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + vcc-supply = <&pm8937_l10>;
> + vio-supply = <&pm8937_l5>;
> +
> + led@0
On Mon, 2025-09-22 at 21:30 +1000, Alistair Popple wrote:
> +const GSP_REGISTRY_NUM_ENTRIES: usize = 2;
> +struct RegistryEntry {
> +key: &'static str,
> +value: u32,
> +}
Probably should add a comment saying that although GSP-RM technically supports
strings as values, we
don't intend t
Convert register bits to BIT() macro and bitfields to GENMASK()/FIELD_PREP()
macros.
Most of this patchset is boring mechanical conversion.
Noteworthy patches are 6 and 7 , those introduce handling of DSI mode flags
and convert use of DRM_MODE_FLAG_P.SYNC into DRM_MODE_FLAG_N.SYNC, but that
shoul
On 2025-09-18 04:33, Tseng, Chuan Yu (Max) wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> On 9/16/25 4:56 PM, Xaver Hugl wrote:
>> Am Mo., 15. Sept. 2025 um 17:49 Uhr schrieb Michel Dänzer
>> :
>>> On 15.09.25 17:37, Derek Foreman wrote:
On 9/15/25 5:01 AM, Michel Dä
The RXSETR_CRCEN(n) and RXSETR_ECCEN(n) macros both take parameter (n),
add the missing macro parameter. Neither of those macros is used by the
driver, so for now the bug is harmless.
Fixes: 685e8dae19df ("drm/rcar-du: dsi: Implement DSI command support")
Signed-off-by: Marek Vasut
---
Cc: David
Call mipi_dsi_pixel_format_to_bpp() once in rcar_mipi_dsi_set_display_timing()
and store the value into a variable. This slightly simplifies the code.
No functional change.
Signed-off-by: Marek Vasut
---
Cc: David Airlie
Cc: Geert Uytterhoeven
Cc: Kieran Bingham
Cc: Laurent Pinchart
Cc: Maar
Convert register bitfields to GENMASK() macro where applicable.
Use FIELD_PREP() throughout the driver.
Signed-off-by: Marek Vasut
---
Cc: David Airlie
Cc: Geert Uytterhoeven
Cc: Kieran Bingham
Cc: Laurent Pinchart
Cc: Maarten Lankhorst
Cc: Magnus Damm
Cc: Maxime Ripard
Cc: Simona Vetter
Cache DSI mode flags in new mode_flags member of struct rcar_mipi_dsi .
Configure TXVMSETR register based on the content of DSI mode flags in
case the controller operates in video mode.
Rename TXVMSETR_H..BPEN_EN to TXVMSETR_H..BPEN and drop TXVMSETR_H..BPEN_DIS
which resolves to 0. Update TXVMSET
Introduce TXVMPSPHSETR_DT_MASK macro and use FIELD_PREP() to generate
appropriate bitfield from mask and value without bitshift.
Do not convert bits and bitfields to BIT() and GENMASK() yet, to be
consisten with the current style. Conversion to BIT() and GENMASK()
macros is done at the very end of
Introduce CLOCKSET1_CLKINSEL_MASK macro and remove bitshift from
values to make this bitfield usable with FIELD_PREP(). There are
no users of this bitfield, hence no updates to the DSI driver.
Do not convert bits and bitfields to BIT() and GENMASK() yet, to be
consisten with the current style. Con
On Mon, Sep 22, 2025 at 10:42:52AM -0700, Rob Clark wrote:
> On Mon, Sep 22, 2025 at 9:46 AM Stephan Gerhold
> wrote:
> >
> > On Mon, Sep 22, 2025 at 09:41:07AM -0700, Rob Clark wrote:
> > > On Mon, Sep 22, 2025 at 9:33 AM Stephan Gerhold
> > > wrote:
> > > > On Wed, Jul 23, 2025 at 12:08:49PM -0
On 2025-09-22 19:45, Pavel Machek wrote:
Hi!
+ led-controller@45 {
+ compatible = "awinic,aw2013";
+ reg = <0x45>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ vcc-supply = <&pm8937_l10>;
+ vio-supply
On Mon, Sep 22, 2025 at 02:27:00PM +0200, gre...@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> minmax: make generic MIN() and MAX() macros available everywhere
>
> to the 6.6-stable tree which can be found at:
>
> http://www.kern
On Fri, Sep 12, 2025 at 08:17:13AM +, Tzung-Bi Shih wrote:
> Some resources can be removed asynchronously, for example, resources
> provided by a hot-pluggable device like USB. When holding a reference
> to such a resource, it's possible for the resource to be removed and
> its memory freed, l
Reviewed-by: Alex Hung
On 9/1/25 15:51, Melissa Wen wrote:
Remove this flag as the driver stopped managing it individually since
commit a4056c2a6344 ("drm/amd/display: use HW hdr mult for brightness
boost"). After some back and forth it was reintroduced as a condition to
`set_output_transfer_fu
On Mon, Sep 22, 2025 at 03:45:54PM +0200, Thomas Zimmermann wrote:
Commit 1a194e6c8e1e ("fbcon: fix integer overflow in fbcon_do_set_font")
introduced an out-of-bounds access by storing data and allocation sizes
in the same variable. Restore the old size calculation and use the new
variable 'allo
During conversion of WARN_ON_ONCE to drm_WARN_ON_ONCE in commit
2d2f1dc74cfb ("drm: gud: replace WARN_ON/WARN_ON_ONCE with drm
versions"), the IS_ERR check was accidentally removed, breaking the
gud_connector_add_properties() function, as any valid pointer in
state_val would produce an error.
The
On 9/20/2025 2:41 AM, Dmitry Baryshkov wrote:
> On Fri, Sep 19, 2025 at 10:24:29PM +0800, Xiangxu Yin wrote:
>> Add QCS615-specific configuration for USB/DP PHY, including DP init
>> routines, voltage swing tables, and platform data. Add compatible
>> "qcs615-qmp-usb3-dp-phy".
>>
>> Signed-off-by
On Mon, Sep 22, 2025 at 06:59:10AM +, Kasireddy, Vivek wrote:
> > You can't translate a dma_addr_t to anything in the Xe PF driver
> > anyhow, once it goes through the IOMMU the necessary information is lost.
> Well, I already tested this path (via IOMMU, with your earlier vfio-pci +
> dmabuf
ions(-)
>
> --
> 2.49.0
>
>
>
My bot found new DTB warnings on the .dts files added or changed in this
series.
Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these w
This is a note to let you know that I've just added the patch titled
minmax: simplify min()/max()/clamp() implementation
to the 6.6-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
min
пн, 22 вер. 2025 р. о 10:27 Mikko Perttunen пише:
>
> On Monday, September 22, 2025 3:30 PM Svyatoslav Ryhel wrote:
> > пн, 22 вер. 2025 р. о 09:23 Mikko Perttunen пише:
> > >
> > > On Monday, September 22, 2025 2:13 PM Svyatoslav Ryhel wrote:
> > > > пн, 22 вер. 2025 р. о 07:44 Mikko Perttunen
On Mon, Sep 22, 2025 at 09:41:07AM -0700, Rob Clark wrote:
> On Mon, Sep 22, 2025 at 9:33 AM Stephan Gerhold
> wrote:
> > On Wed, Jul 23, 2025 at 12:08:49PM -0700, Rob Clark wrote:
> > > If we hit an error path in GEM obj creation before msm_gem_new_handle()
> > > updates obj->resv to point to the
On 22/09/2025 13:56, 김강민 wrote:
Dear Linux kernel developers and maintainers,
This is to report a kernel bug discovered in the i915 driver using my
modified syzkaller.
Kernel driver involved: i915
Version detected by syzkaller:
- Commit version: c330cb607721
Latest version tested for NULL p
On Mon, Sep 22, 2025 at 9:33 AM Stephan Gerhold
wrote:
>
> Hi Rob,
>
> On Wed, Jul 23, 2025 at 12:08:49PM -0700, Rob Clark wrote:
> > If we hit an error path in GEM obj creation before msm_gem_new_handle()
> > updates obj->resv to point to the gpuvm resv object, then obj->resv
> > still points to
Hi Rob,
On Wed, Jul 23, 2025 at 12:08:49PM -0700, Rob Clark wrote:
> If we hit an error path in GEM obj creation before msm_gem_new_handle()
> updates obj->resv to point to the gpuvm resv object, then obj->resv
> still points to &obj->_resv. In this case we don't want to decrement
> the refcount
> Make sure to drop the references taken to the vtg devices by
VTG device?
> of_find_device_by_node() when looking up their driver data during
> component probe.
…
How do you think about to increase the application of scope-based resource
managem
On 9/22/25 1:30 PM, Alistair Popple wrote:
> +// SAFETY: No DMA allocations have been made yet
It's not really about DMA allocations that have been made previously, there is
no unsafe behavior in that.
It's about the method must not be called concurrently with any DMA allocation or
mappin
1 - 100 of 191 matches
Mail list logo
