From: paul.kocialkowski@bootlin.com (Paul Kocialkowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/sun4i: Add missing frontend compatibles for A10, A13, A20 and A31
Date: Fri, 20 Apr 2018 09:33:36 +0200 [thread overview]
Message-ID: <f89313a67594665f4ddf88e76947ba642b554358.camel@bootlin.com> (raw)
In-Reply-To: <20180419150759.ldi676ejnbtmb27z@flea>
Hi,
On Thu, 2018-04-19 at 17:07 +0200, Maxime Ripard wrote:
> On Thu, Apr 19, 2018 at 02:56:38PM +0200, Paul Kocialkowski wrote:
> > Although frontend nodes are defined in the device-trees of the
> > aforementioned platforms, there are no matching compatibles defined
> > in
> > the driver. This makes it impossible to probe the frontend on these
> > platforms.
> >
> > Adding the appropriate compatibles to the driver fixes the issue.
> >
> > Signed-off-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
> > ---
> > drivers/gpu/drm/sun4i/sun4i_frontend.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/sun4i/sun4i_frontend.c
> > b/drivers/gpu/drm/sun4i/sun4i_frontend.c
> > index 85f75046712c..c5a3de11817d 100644
> > --- a/drivers/gpu/drm/sun4i/sun4i_frontend.c
> > +++ b/drivers/gpu/drm/sun4i/sun4i_frontend.c
> > @@ -658,6 +658,10 @@ static const struct dev_pm_ops
> > sun4i_frontend_pm_ops = {
> > };
> >
> > const struct of_device_id sun4i_frontend_of_table[] = {
> > + { .compatible = "allwinner,sun7i-a10-display-frontend" },
> > + { .compatible = "allwinner,sun7i-a13-display-frontend" },
> > + { .compatible = "allwinner,sun7i-a20-display-frontend" },
> > + { .compatible = "allwinner,sun7i-a31-display-frontend" },
>
> Most of these compatibles are wrong, so it won't really work :)
Sorry for screwing up so bad...
> If you only tested it on the A20, just add it. We didn't add all of
> them because there's some slight variations between the generations
> that are not yet taken into account.
That makes sense. I will thus send v2 with A20 only and send follow-up
patches for other platforms when tested and properly working.
Thanks!
--
Paul Kocialkowski, Bootlin (formerly Free Electrons)
Embedded Linux and kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180420/b97e801d/attachment.sig>
prev parent reply other threads:[~2018-04-20 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 12:56 [PATCH] drm/sun4i: Add missing frontend compatibles for A10, A13, A20 and A31 Paul Kocialkowski
2018-04-19 15:07 ` Maxime Ripard
2018-04-20 7:33 ` Paul Kocialkowski [this message]
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=f89313a67594665f4ddf88e76947ba642b554358.camel@bootlin.com \
--to=paul.kocialkowski@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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