On Mon, 25 Nov 2024 at 13:57, wrote:
>
> On 25/11/2024 12:24, Sasha Finkelstein wrote:
> > On Mon, 25 Nov 2024 at 09:50, Neil Armstrong
> > wrote:
> >>
> >> So this controller only supports a single mode ???
> >>
> > Most likely. On all devices it is connected to a single built-in display.
>
On Mon, 25 Nov 2024 at 09:50, Neil Armstrong wrote:
>
> So this controller only supports a single mode ???
>
Most likely. On all devices it is connected to a single built-in display.
Ack on all other changes, will be fixed for v2.
On November 25, 2024 4:28:00 PM GMT+01:00, Maxime Ripard
wrote:
>On Mon, Nov 25, 2024 at 11:24:25PM +0900, Hector Martin wrote:
>>
>>
>> On 2024/11/25 20:24, Sasha Finkelstein wrote:
>> > On Mon, 25 Nov 2024 at 09:50, Neil Armstrong
>> > wrote:
>> >>
>> >> So this controller only supports a s
Hi Hector,
On 25/11/2024 15:24, Hector Martin wrote:
On 2024/11/25 20:24, Sasha Finkelstein wrote:
On Mon, 25 Nov 2024 at 09:50, Neil Armstrong wrote:
So this controller only supports a single mode ???
Most likely. On all devices it is connected to a single built-in display.
More s
On Mon, Nov 25, 2024 at 11:24:25PM +0900, Hector Martin wrote:
>
>
> On 2024/11/25 20:24, Sasha Finkelstein wrote:
> > On Mon, 25 Nov 2024 at 09:50, Neil Armstrong
> > wrote:
> >>
> >> So this controller only supports a single mode ???
> >>
> > Most likely. On all devices it is connected to
On 2024/11/25 20:24, Sasha Finkelstein wrote:
> On Mon, 25 Nov 2024 at 09:50, Neil Armstrong
> wrote:
>>
>> So this controller only supports a single mode ???
>>
> Most likely. On all devices it is connected to a single built-in display.
More specifically, the controller obviously support
On 25/11/2024 14:14, Sasha Finkelstein wrote:
On Mon, 25 Nov 2024 at 13:57, wrote:
On 25/11/2024 12:24, Sasha Finkelstein wrote:
On Mon, 25 Nov 2024 at 09:50, Neil Armstrong wrote:
So this controller only supports a single mode ???
Most likely. On all devices it is connected to a sin
On 25/11/2024 12:24, Sasha Finkelstein wrote:
On Mon, 25 Nov 2024 at 09:50, Neil Armstrong wrote:
So this controller only supports a single mode ???
Most likely. On all devices it is connected to a single built-in display.
Ack on all other changes, will be fixed for v2.
OK, so instead
This still has the bug that I originally reported at:
https://github.com/AsahiLinux/linux/issues/258
On Sun, Nov 24, 2024 at 11:29:25PM +0100, Sasha Finkelstein via B4 Relay wrote:
> +static int adp_probe(struct platform_device *pdev)
> +{
> + struct adp_drv_private *adp;
> + int err;
> +
On Sun, 24 Nov 2024, Sasha Finkelstein via B4 Relay
wrote:
> diff --git a/drivers/gpu/drm/adp/adp_drv.c b/drivers/gpu/drm/adp/adp_drv.c
> new file mode 100644
> index
> ..36510194e18161ef6514885c764b2e7085c587e5
> --- /dev/null
> +++ b/drivers/gpu/drm/adp/
Hi,
On 24/11/2024 23:29, Sasha Finkelstein via B4 Relay wrote:
From: Sasha Finkelstein
Please use "drm: " and drop gpu from commit title.
This display controller is present on M-series chips and is used
to drive the touchbar display.
Co-developed-by: Janne Grunau
Signed-off-by: Janne Gru
From: Sasha Finkelstein
This display controller is present on M-series chips and is used
to drive the touchbar display.
Co-developed-by: Janne Grunau
Signed-off-by: Janne Grunau
Signed-off-by: Sasha Finkelstein
---
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/Makefile | 1 +
12 matches
Mail list logo
