mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Cyril Brulebois <cyril@debamax.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Rob Herring <robh@kernel.org>,
	Michal Suchanek <msuchanek@suse.de>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] drm/ofdrm: Update expected device name
Date: Mon, 24 Apr 2023 11:07:45 +0200	[thread overview]
Message-ID: <5694a9ab-d474-c101-9398-eea55aab29df@suse.de> (raw)
In-Reply-To: <CAMuHMdW4rZn4p=gQZRWQQSEbQPmzZUd5eN+kP_Yr7bLgTHyvig@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2408 bytes --]

Hi

Am 24.04.23 um 09:33 schrieb Geert Uytterhoeven:
> Hi Cyril,
> 
> CC DT
> 
> On Wed, Apr 12, 2023 at 12:05 PM Cyril Brulebois <cyril@debamax.com> wrote:
>> Since commit 241d2fb56a18 ("of: Make OF framebuffer device names unique"),
>> as spotted by Frédéric Bonnard, the historical "of-display" device is
>> gone: the updated logic creates "of-display.0" instead, then as many
>> "of-display.N" as required.
>>
>> This means that offb no longer finds the expected device, which prevents
>> the Debian Installer from setting up its interface, at least on ppc64el.
>>
>> Given the code similarity it is likely to affect ofdrm in the same way.
>>
>> It might be better to iterate on all possible nodes, but updating the
>> hardcoded device from "of-display" to "of-display.0" is likely to help
>> as a first step.
>>
>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217328
>> Link: https://bugs.debian.org/1033058
>> Fixes: 241d2fb56a18 ("of: Make OF framebuffer device names unique")
>> Cc: stable@vger.kernel.org # v6.2+
>> Signed-off-by: Cyril Brulebois <cyril@debamax.com>
> 
> Thanks for your patch, which is now commit 3a9d8ea2539ebebd
> ("drm/ofdrm: Update expected device name") in fbdev/for-next.
> 
>> --- a/drivers/gpu/drm/tiny/ofdrm.c
>> +++ b/drivers/gpu/drm/tiny/ofdrm.c
>> @@ -1390,7 +1390,7 @@ MODULE_DEVICE_TABLE(of, ofdrm_of_match_display);
>>
>>   static struct platform_driver ofdrm_platform_driver = {
>>          .driver = {
>> -               .name = "of-display",
>> +               .name = "of-display.0",
>>                  .of_match_table = ofdrm_of_match_display,
>>          },
>>          .probe = ofdrm_probe,
> 
> Same comment as for "[PATCH 1/2] fbdev/offb: Update expected device
> name".
> 
> https://lore.kernel.org/r/CAMuHMdVGEeAsmb4tAuuqqGJ-4+BBETwEwYJA+M9NyJv0BJ_hNg@mail.gmail.com

Sorry that I missed this patch. I agree that it's probably not correct. 
At least in ofdrm, we want to be able to use multiple framebuffers at 
the same time; a feature that has been broken by this change.

Best regards
Thomas

> 
> Gr{oetje,eeting}s,
> 
>                          Geert
> 

-- 
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2023-04-24  9:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  9:55 Updating hardcoded "of-display" devices Cyril Brulebois
2023-04-12  9:55 ` [PATCH 1/2] fbdev/offb: Update expected device name Cyril Brulebois
2023-04-16 12:34   ` Salvatore Bonaccorso
2023-06-15 13:03     ` Linux regression tracking (Thorsten Leemhuis)
2023-06-15 13:06       ` Thomas Zimmermann
2023-06-15 13:21         ` Michal Suchánek
2023-06-15 20:09           ` Rob Herring
2023-06-15 21:19             ` Cyril Brulebois
2023-06-20  6:24               ` Helge Deller
2023-06-20  8:04                 ` Michal Suchánek
2023-06-15 13:12       ` Cyril Brulebois
2023-04-22  9:50   ` Helge Deller
2023-04-24  7:31   ` Geert Uytterhoeven
2023-07-10 16:36   ` Michal Suchánek
2023-04-12  9:55 ` [PATCH 2/2] drm/ofdrm: " Cyril Brulebois
2023-04-24  7:33   ` Geert Uytterhoeven
2023-04-24  9:07     ` Thomas Zimmermann [this message]
2023-04-24  9:35       ` Helge Deller
2023-05-22  9:37         ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:44       ` Michal Suchánek
2023-07-10 16:36   ` Michal Suchánek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5694a9ab-d474-c101-9398-eea55aab29df@suse.de \
    --to=tzimmermann@suse.de \
    --cc=cyril@debamax.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msuchanek@suse.de \
    --cc=robh@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®