From: "Michal Suchánek" <msuchanek@suse.de>
To: Helge Deller <deller@gmx.de>
Cc: Cyril Brulebois <cyril@debamax.com>,
Rob Herring <robh@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Salvatore Bonaccorso <carnil@debian.org>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] fbdev/offb: Update expected device name
Date: Tue, 20 Jun 2023 10:04:34 +0200 [thread overview]
Message-ID: <20230620080434.GD9196@kitsune.suse.cz> (raw)
In-Reply-To: <3d8c3a8c-68be-422a-c4ff-6d2e99c3f01b@gmx.de>
On Tue, Jun 20, 2023 at 08:24:34AM +0200, Helge Deller wrote:
> On 6/15/23 23:19, Cyril Brulebois wrote:
> > Hi Rob,
> >
> > Rob Herring <robh@kernel.org> (2023-06-15):
> > > On Thu, Jun 15, 2023 at 03:21:07PM +0200, Michal Suchánek wrote:
> > > > At the time this was proposed it was said that "of-display", is wrong,
> > > > and that "of-display.0" must be used for the first device instead, and
> > > > if something breaks an alias can be provided.
> > > >
> > > > So how does one provide an alias so that offb can find "of-display.0"
> > > > as "of-display"?
> > >
> > > I'm not aware of any way. There isn't because device names and paths are
> > > not considered ABI. There are mechanisms for getting stable class device
> > > indices (e.g. i2c0, mmcblk0, fb0, fb1, etc.) though not implemented for
> > > fbN (and please don't add it).
> > >
> > > In any case, this should be an easy fix. Though if "linux,opened" or
> > > "linux,boot-display" is not set, then you'd still get "of-display.0":
> > >
> > > diff --git a/drivers/of/platform.c b/drivers/of/platform.c
> > > index 78ae84187449..e46482cef9c7 100644
> > > --- a/drivers/of/platform.c
> > > +++ b/drivers/of/platform.c
> > > @@ -553,7 +553,7 @@ static int __init of_platform_default_populate_init(void)
> > > if (!of_get_property(node, "linux,opened", NULL) ||
> > > !of_get_property(node, "linux,boot-display", NULL))
> > > continue;
> > > - dev = of_platform_device_create(node, "of-display.0", NULL);
> > > + dev = of_platform_device_create(node, "of-display", NULL);
> > > of_node_put(node);
> > > if (WARN_ON(!dev))
> > > return -ENOMEM;
>
> Michal, does that patch look correct?
> I don't have that hardware, but that way the boot-display gets named
> "of-display" while all others get "of-display.x"....
Yes, that's inconsistent, and IIRC it's what I originally proposed to
preserve compatibility as much as possible.
The patch went through multiple iteration by me and Rob and the final
version that was merged uses the consistent but incompatible naming.
The other option would be to adapt the offb driver, presumably.
I don't understand how the device name figures in attaching the driver
to the device, the only other occurence of of-display is the name of the
offb and ofdrm drivers.
> > I've just replaced my clueless workaround with this patch on top of the
> > kernel found in Debian 12 (Bookworm), i.e. 6.1.27 at this point, and it
> > indeed fixes the black screen problem in the installer's context.
>
> ... at least it fixes the issue.
I would expect as much. I don't have the hardware either but keeping
what was there before, and only adding on top is kind of the least
disruptive way of adding new stuff.
Thanks
Michal
next prev parent reply other threads:[~2023-06-20 8:04 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 [this message]
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
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=20230620080434.GD9196@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=carnil@debian.org \
--cc=cyril@debamax.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).