From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"David Airlie" <airlied@linux.ie>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Russell King" <linux@armlinux.org.uk>,
"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"Julia Lawall" <Julia.Lawall@lip6.fr>,
"Sean Paul" <seanpaul@chromium.org>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-fbdev@vger.kernel.org, letux-kernel@openphoenux.org,
kernel@pyra-handheld.com
Subject: Re: [PATCH 4/4] omapdss: fix problem enabling VDDS_DSI on OMAP3530 (OpenPandora)
Date: Thu, 09 Nov 2017 03:45:36 +0000 [thread overview]
Message-ID: <3397395.9drm9Essi0@avalon> (raw)
In-Reply-To: <b94c5e773994ee55df9225fc84825bacb3fcb256.1510175371.git.hns@goldelico.com>
Hi Nikolaus,
Thank you for the patch.
On Wednesday, 8 November 2017 23:09:32 EET H. Nikolaus Schaller wrote:
> commit d178e034d565 ("drm: omapdrm: Move FEAT_DPI_USES_VDDS_DSI feature to
> dpi code")
>
> introduced a new match table which turned out to be wrong, at least
> for the 600 MHz OpenPandora using the OMAP3530.
>
> The effect was strange: only the Blue channel of the RGB panel was
> driven while Red and Green stayed black. So a coloured picture turned
> into blue/black.
>
> The GTA04 with DM3730 didn't show the effect.
>
> It turned out that VDDS_DSI was not properly initialized on OMAP3530,
> because the .family string is just "OMAP3" for these processors and
> not "OMAP3xxx".
>
> Therefore we match the .machine attribute.
>
> Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
I've already submitted a similar patch (but without the problem pointed out
below) in the mail thread where we discussed the issue. It is customary to use
the first patch posted (unless it is utterly broken of course). Could you thus
please include it in this series in replacement of this patch ?
> ---
> drivers/gpu/drm/omapdrm/dss/dpi.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/omapdrm/dss/dpi.c
> b/drivers/gpu/drm/omapdrm/dss/dpi.c index 4ed5fde11313..aae3626910bb 100644
> --- a/drivers/gpu/drm/omapdrm/dss/dpi.c
> +++ b/drivers/gpu/drm/omapdrm/dss/dpi.c
> @@ -566,8 +566,7 @@ static int dpi_verify_pll(struct dss_pll *pll)
> }
>
> static const struct soc_device_attribute dpi_soc_devices[] = {
> - { .family = "OMAP3[456]*" },
> - { .family = "[AD]M37*" },
> + { .machine = "OMAP3[456]*" },
You also need
{ .machine = "[AD]M37*" },
otherwise there will be no match for the OMAP3-like AM37xx and DM37xx SoCs.
Another option would be to match on { .family = "OMAP3*" } but there could be
spurious matches, even though I haven't identified any.
> { /* sentinel */ }
> };
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-11-09 3:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 21:09 [PATCH 0/4] Fixes for omapdrm on OpenPandora and GTA04 H. Nikolaus Schaller
2017-11-08 21:09 ` [PATCH 1/4] omapdrm: fix compatible string for td028ttec1 H. Nikolaus Schaller
2017-11-09 3:33 ` Laurent Pinchart
2017-11-09 6:05 ` H. Nikolaus Schaller
[not found] ` <C999B55A-771D-44AF-8072-2F30FE6B54B7-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>
2017-11-09 6:35 ` Laurent Pinchart
2017-11-09 6:48 ` H. Nikolaus Schaller
2017-11-08 21:09 ` [PATCH 2/4] DTS: GTA04: fix panel compatibility string H. Nikolaus Schaller
2017-11-08 21:09 ` [PATCH 3/4] DTS: Pandora: " H. Nikolaus Schaller
2017-11-09 3:36 ` Laurent Pinchart
2017-11-09 6:06 ` H. Nikolaus Schaller
2017-11-08 21:09 ` [PATCH 4/4] omapdss: fix problem enabling VDDS_DSI on OMAP3530 (OpenPandora) H. Nikolaus Schaller
2017-11-09 3:45 ` Laurent Pinchart [this message]
2017-11-09 6:12 ` H. Nikolaus Schaller
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=3397395.9drm9Essi0@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Julia.Lawall@lip6.fr \
--cc=airlied@linux.ie \
--cc=b.zolnierkie@samsung.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hns@goldelico.com \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.com \
/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).