On Thu, May 22, 2025 at 07:47:00PM +0300, Cristian Ciocaltea wrote:
> On 5/22/25 7:06 PM, Maxime Ripard wrote:
> > On Mon, May 19, 2025 at 01:35:46PM +0300, Cristian Ciocaltea wrote:
> >> On 5/19/25 10:22 AM, Maxime Ripard wrote:
> >>> Hi,
> >>>
> >>> On Fri, Apr 25, 2025 at 01:27:05PM +0300, Crist
Hi
Am 22.05.25 um 17:09 schrieb Lucas De Marchi:
On Thu, May 22, 2025 at 04:52:18PM +1000, Dave Airlie wrote:
From: Dave Airlie
This reduces this struct from 16 to 8 bytes, and it gets embedded
into a lot of things.
Signed-off-by: Dave Airlie
Replied too early on cover. Chatting with Mich
The function mod_hdcp_hdcp1_enable_encryption() calls the function
get_first_active_display(), but does not check its return value.
The return value is a null pointer if the display list is empty.
This will lead to a null pointer dereference in
mod_hdcp_hdcp2_enable_encryption().
Add a null pointe
From: Chaoyi Chen
Convert it to drm bridge driver, it will be convenient for us to
migrate the connector part to the display driver later.
Signed-off-by: Chaoyi Chen
---
drivers/gpu/drm/rockchip/rockchip_lvds.c | 68 ++--
1 file changed, 29 insertions(+), 39 deletions(-)
d
On Fri, May 23, 2025 at 03:52:26PM -0400, Abdulrasaq Lawani wrote:
> diff --git a/Documentation/gpu/introduction.rst
> b/Documentation/gpu/introduction.rst
> index
> 91bb0efc96d69921a122c5265b1431fa18110a7a..2653048ad4bb0ecbc2b676295440442dddbabae6
> 100644
> --- a/Documentation/gpu/introduction
Hi Dmitry,
On 2025/5/24 6:17, Dmitry Baryshkov wrote:
On Fri, May 23, 2025 at 09:13:10AM +0800, Chaoyi Chen wrote:
From: Chaoyi Chen
Convert it to drm bridge driver, it will be convenient for us to
migrate the connector part to the display driver later.
Considering that some code depend on t
On Sun, 25 May 2025 at 15:33, Dmitry Baryshkov
wrote:
>
> On Sat, May 24, 2025 at 07:58:13PM +0200, Aleksandrs Vinarskis wrote:
> > On Sat, 24 May 2025 at 17:33, Dmitry Baryshkov
> > wrote:
> > >
> > > On Sat, May 24, 2025 at 01:48:40PM +0200, Jens Glathe via B4 Relay wrote:
> > > > From: Jens Gl
On Fri, May 9, 2025 at 8:56 AM Luca Ceresoli wrote:
>
> devm_drm_bridge_alloc() is the new API to be used for allocating (and
> partially initializing) a private driver struct embedding a struct
> drm_bridge.
>
> For many drivers having a simple code flow in the probe function, this
> commit does
This patch enhances dual-backlight handling by explicitly linking
primary and secondary backlight devices using new fields:
- `is_secondary`: Marks if a device is secondary in a pair
- `secondary`: Points to the associated secondary device (if any)
- `primary`: Points to the primary device (for se
From: Aradhya Bhatia
The AM62x and AM62Px SoCs feature 2 OLDI TXes each, which makes it
possible to connect them in dual-link or cloned single-link OLDI display
modes. The current OLDI support in tidss_dispc.c can only support for
a single OLDI TX, connected to a VP and doesn't really support
con
From: Aradhya Bhatia
Reduce tab size from 8 spaces to 4 spaces to make the bindings
consistent, and easy to expand.
Acked-by: Rob Herring (Arm)
Reviewed-by: Laurent Pinchart
Reviewed-by: Tomi Valkeinen
Signed-off-by: Aradhya Bhatia
Signed-off-by: Aradhya Bhatia
---
.../bindings/display/ti/
From: Aradhya Bhatia
The OLDI transmitters (TXes) do not have registers of their own, and are
dependent on the source video-ports (VPs) from the DSS to provide
configuration data. This hardware doesn't directly sit on the internal
bus of the SoC, but does so via the DSS. Hence, the OLDI TXes are
The dss dt schema and the tidss driver have kept the single-link OLDI in
AM65x integrated with the parent video-port (VP) from DSS (as the OLDI
configuration happens from the source VP only).
To help configure the dual-lvds modes that the OLDI has to offer in
devices AM62x and later, a new OLDI bri
Hello all,
This patch series adds support for the dual OLDI TXes supported in Texas
Instruments' AM62x and AM62Px family of SoCs. The OLDI TX hardware supports
single-lvds, lvds-clone, and dual-lvds modes. These TXes have now been
represented through DRM bridges within TI-DSS.
* Some history and
According to the C11 standard (ISO/IEC 9899:2011, 6.5.7):
"If E1 has a signed type and E1 x 2^E2 is not representable in the result
type, the behavior is undefined."
Shifting 1 << 31 causes signed integer overflow, which leads to undefined
behavior.
Fix this by explicitly using 'BIT(31)' to ensur
On Sat, May 24, 2025 at 07:58:13PM +0200, Aleksandrs Vinarskis wrote:
> On Sat, 24 May 2025 at 17:33, Dmitry Baryshkov
> wrote:
> >
> > On Sat, May 24, 2025 at 01:48:40PM +0200, Jens Glathe via B4 Relay wrote:
> > > From: Jens Glathe
> > >
> > > Device tree for the Lenovo Thinkbook 16 G7 QOY
> >
On Sun, May 25, 2025 at 06:53:36AM -0300, Val Packett wrote:
> Cannot confirm which variant exactly it is, as the EDID alphanumeric data
> contains '0RGNR' <0x80> 'NE14QDM' and ends there; but it's 60 Hz and with
> touch.
>
> I do not have access to datasheets for these panels, so the timing is
>
On Mon, Apr 7, 2025 at 9:24 AM Luca Ceresoli wrote:
>
> devm_drm_bridge_alloc() is the new API to be used for allocating (and
> partially initializing) a private driver struct embedding a struct
> drm_bridge.
>
> For many drivers having a simple code flow in the probe function, this
> commit does
On 25/05/2025 12:48, Daniel Stone wrote:
> On Sun, 25 May 2025 at 06:16, Krzysztof Kozlowski
> wrote:
>> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml
>> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml
>> @@ -45,9 +45,8 @@ properties:
>
Hi Eero,
On Thu, 22 May 2025 at 00:56, Eero Tamminen wrote:
> On 21.5.2025 10.06, Geert Uytterhoeven wrote:
> > On Wed, 21 May 2025 at 01:59, Eero Tamminen wrote:
> >> I tried your "atari-drm-wip-v1" branch commits on top of 6.14.
> >
> > Thanks for testing!
> >
> >> After some minor changes tho
On Sun, 25 May 2025 at 06:16, Krzysztof Kozlowski
wrote:
> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml
> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,ovl-2l.yaml
> @@ -45,9 +45,8 @@ properties:
>- description: OVL-2L Clock
>
>iommu
When registering a backlight device, if a device with the same name
already exists, append "-secondary" to the new device's name. This is
useful for platforms with dual backlight drivers (e.g. some panels use
dual ktz8866), where both instances need to coexist.
For now, only one secondary instance
Cannot confirm which variant exactly it is, as the EDID alphanumeric data
contains '0RGNR' <0x80> 'NE14QDM' and ends there; but it's 60 Hz and with
touch.
I do not have access to datasheets for these panels, so the timing is
a guess that was tested to work fine on this laptop.
Signed-off-by: Val
On Thu, 8 May 2025 15:06:09 +0200
Markus Burri wrote:
> The buffer is set to 20 characters. If a caller write more characters,
> count is truncated to the max available space in "simple_write_to_buffer".
> To protect from OoB access, check that the input size fit into buffer and
> add a zero ter
On Thu, 8 May 2025 15:06:09 +0200
Markus Burri wrote:
> The buffer is set to 20 characters. If a caller write more characters,
> count is truncated to the max available space in "simple_write_to_buffer".
> To protect from OoB access, check that the input size fit into buffer and
> add a zero ter
On Sun, 11 May 2025 15:27:07 +0100
Jonathan Cameron wrote:
> On Thu, 8 May 2025 15:06:07 +0200
> Markus Burri wrote:
>
> > The buffer is set to 80 character. If a caller write more characters,
> > count is truncated to the max available space in "simple_write_to_buffer".
> > But afterwards a s
27 matches
Mail list logo
