From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH/RFC 0/7] Remove the omapdrm device from platform code
Date: Thu, 15 Dec 2016 13:04:38 +0200 [thread overview]
Message-ID: <c59e26d6-0475-7d13-6bf1-ca785d0aa8f3@ti.com> (raw)
In-Reply-To: <2042929.xqZ0CNKz48@avalon>
[-- Attachment #1.1.1: Type: text/plain, Size: 485 bytes --]
On 15/12/16 12:07, Laurent Pinchart wrote:
>> Or do you have any other ideas how to pass flags to the driver based on
>> the SoC revision?
>
> Or retrieve the SoC revision in the driver. I know this is a bad thing to do
> in general, but when handling errata that are specific to certain ES versions,
> it's hard to avoid. https://patchwork.kernel.org/patch/9141381/ has been
> developed for that (or at least a very similar) purpose.
Ah, that should work.
Tomi
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-12-15 11:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 23:38 [PATCH/RFC 0/7] Remove the omapdrm device from platform code Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 1/7] drm: omapdrm: Add OMAP revision to omapdss platform data Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 2/7] ARM: OMAP2+: Populate the omapdss platform data OMAP revision Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 3/7] drm: omapdrm: Retrieve OMAP revision from omapdss Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 4/7] ARM: OMAP2+: Remove omapdrm platform data Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 5/7] drm: omapdrm: " Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 6/7] drm: omapdrm: Register omapdrm platform device in omapdss driver Laurent Pinchart
2016-12-14 8:20 ` Tomi Valkeinen
2016-12-14 11:54 ` Laurent Pinchart
2016-12-13 23:38 ` [PATCH/RFC 7/7] ARM: OMAP2+: Remove unused omapdrm platform device Laurent Pinchart
2016-12-14 1:58 ` [PATCH/RFC 8/7] drm: omapdrm: Handle DSI pin muxing internally Laurent Pinchart
2016-12-14 1:58 ` [PATCH/RFC 9/7] drm: omapdrm: Don't forward set_min_bus_tput() to no-op platform code Laurent Pinchart
2016-12-14 1:58 ` [PATCH/RFC 10/7] ARM: OMAP2+: Remove DSI pin muxing Laurent Pinchart
2016-12-14 1:58 ` [PATCH/RFC 11/7] ARM: OMAP2+: Remove omapdss set_min_bus_tput platform data callback Laurent Pinchart
2016-12-14 1:58 ` [PATCH/RFC 12/7] drm: omapdrm: Remove unused omapdss platform data fields Laurent Pinchart
2016-12-18 0:54 ` [PATCH/RFC v1.1 12/7] drm: omapdrm: Remove unused omapdss platform data field Laurent Pinchart
2016-12-14 15:05 ` [PATCH/RFC 0/7] Remove the omapdrm device from platform code Tony Lindgren
2016-12-15 8:08 ` Tomi Valkeinen
2016-12-15 10:07 ` Laurent Pinchart
2016-12-15 11:04 ` Tomi Valkeinen [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=c59e26d6-0475-7d13-6bf1-ca785d0aa8f3@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-omap@vger.kernel.org \
--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