From: Thierry Reding <thierry.reding@gmail.com>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Andrzej Hajda <a.hajda@samsung.com>,
Terje Bergstrom <tbergstrom@nvidia.com>,
Stephen Warren <swarren@wwwdotorg.org>,
linux-tegra@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, gnurou@gmail.com
Subject: Re: [PATCH v3 4/4] ARM: tegra: roth: add display DT node
Date: Fri, 11 Jul 2014 15:14:22 +0200 [thread overview]
Message-ID: <20140711131421.GD10827@ulmo> (raw)
In-Reply-To: <1404822734-8603-5-git-send-email-acourbot@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
On Tue, Jul 08, 2014 at 09:32:14PM +0900, Alexandre Courbot wrote:
> Tegra DSI support has been fixed to support continuous clock behavior that
> the panel used on SHIELD requires, so finally add its device tree node
> since it is functional.
>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
> ---
> arch/arm/boot/dts/tegra114-roth.dts | 22 +++++++++++++++++++---
> 1 file changed, 19 insertions(+), 3 deletions(-)
I've applied this to Tegra's for-3.17/dt branch. Thanks.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-07-11 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 12:32 [PATCH v3 0/4] drm/dsi/tegra: continuous clock support Alexandre Courbot
2014-07-08 12:32 ` [PATCH v3 1/4] drm/dsi: Flag for non-continuous clock behavior Alexandre Courbot
2014-07-14 8:29 ` Thierry Reding
2014-07-08 12:32 ` [PATCH v3 2/4] drm/panel: Set non-continuous clock flag on supporting panels Alexandre Courbot
2014-07-14 8:30 ` Thierry Reding
2014-07-08 12:32 ` [PATCH v3 3/4] drm/tegra: dsi - Handle non-continuous clock flag Alexandre Courbot
2014-07-14 8:30 ` Thierry Reding
2014-07-08 12:32 ` [PATCH v3 4/4] ARM: tegra: roth: add display DT node Alexandre Courbot
2014-07-11 13:14 ` Thierry Reding [this message]
2014-07-13 2:37 ` Alexandre Courbot
2014-07-14 6:05 ` Thierry Reding
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=20140711131421.GD10827@ulmo \
--to=thierry.reding@gmail.com \
--cc=a.hajda@samsung.com \
--cc=acourbot@nvidia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gnurou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=tbergstrom@nvidia.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).