From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Nishanth Menon" <nm@ti.com>, "Tony Lindgren" <tony@atomide.com>,
"Paul Walmsley" <paul@pwsan.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Felipe Balbi <balbi@ti.com>, Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCH 0/9] ARM: DRA7: add display support
Date: Mon, 16 Feb 2015 10:30:52 +0200 [thread overview]
Message-ID: <54E1AABC.5010907@ti.com> (raw)
In-Reply-To: <54DE1FD9.6030801@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On 13/02/15 18:01, Nishanth Menon wrote:
> On 02/13/2015 09:11 AM, Tomi Valkeinen wrote:
>> Hi,
>>
>> This series adds the arch/arm/ side of the display support for DRA7 (DRA72x,
>> DRA74x, AM54xx) SoCs. Also support for HDMI output on x15 and DRA72 EVM boards
>> is added.
>>
>> The series is based on OMAPDSS driver patches in fbdev changes for 3.20, which
>> have been merged to Linus' tree.
>>
>> The changes are very similar to OMAP5 DSS. All the other patches look fine to
>> me except the "RFC: ARM: DRA7: enable DSS_DESHDCP_CLKEN". That's been discussed
>> earlier with Paul and Tero, but I don't think we have any good solution for it
>> yet.
>
> Is there some specific tag I can test this on (some next perhaps?), I
Linus's master or linux-next should work. This series is based on the
fbdev changes for 3.20. So if Linus' master or linux-next doesn't work,
v3.19 + fbdev-3.20 + this series should work.
> Further are you proposing this for 3.20 or 3.21 window? 3.20, we seem
> to have already missed.
3.21.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-02-16 8:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 15:11 [PATCH 0/9] ARM: DRA7: add display support Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 1/9] arm/dts: dra7xx: add 'ti,set-rate-parent' for dss_dss_clk Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 2/9] ARM: DRA7: hwmod: add DMM hwmod description Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 3/9] ARM: DRA7: hwmod: set DSS submodule parent hwmods Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 4/9] ARM: OMAP: display: change compat names to array Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 5/9] ARM: OMAP2+: display: detect DRA7 DSS Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 6/9] arm/dts: dra7.dtsi: add DSS support Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 7/9] arm/dts: dra72-evm.dts: add HDMI Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 8/9] arm/dts: am57xx-beagle-x15.dts: " Tomi Valkeinen
2015-02-13 15:11 ` [PATCH 9/9] RFC: ARM: DRA7: enable DSS_DESHDCP_CLKEN Tomi Valkeinen
2015-02-13 15:25 ` Nishanth Menon
2015-02-13 15:42 ` Tero Kristo
2015-02-20 11:46 ` Tomi Valkeinen
2015-02-20 12:59 ` Tero Kristo
2015-02-20 13:48 ` Tomi Valkeinen
2015-02-20 16:59 ` Tero Kristo
2015-02-16 8:28 ` Tomi Valkeinen
2015-02-13 16:01 ` [PATCH 0/9] ARM: DRA7: add display support Nishanth Menon
2015-02-16 8:30 ` 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=54E1AABC.5010907@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=t-kristo@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).