linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: stefan@agner.ch
Cc: thierry.reding@gmail.com, linux@arm.linux.org.uk,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
	marcel@ziswiler.com
Subject: Re: [PATCH v2 3/3] ARM: tegra: initial add of Colibri T30
Date: Thu, 15 May 2014 12:37:55 -0600	[thread overview]
Message-ID: <53750983.3080705@wwwdotorg.org> (raw)
In-Reply-To: <a8f01e573dcb7d563833ddcda30567e8ac7626ed.1400103181.git.stefan@agner.ch>

On 05/14/2014 03:45 PM, stefan@agner.ch wrote:
> From: Stefan Agner <stefan@agner.ch>
> 
> This patch adds the device tree to support Toradex Colibri T30, a
> computer on module which can be used on different carrier boards.
> 
> The module consists of a Tegra 30 SoC, two PMIC, DDR3L RAM, eMMC,
> a LM95245 temperature sensor and an AX88772B USB Ethernet
> Controller. Furthermore, there is a STMPE811 and SGTL5000 audio
> codec which are not yet supported. Anything that is not self
> contained on the module is disabled by default.
> 
> The device tree for the Evaluation Board includes the modules
> device tree and enables the supported pheripherials of the carrier
> board (the Evaluation Board supports almost all of them).

I've applied this to Tegra's for-3.16/dt branch.

A changelog in each individual patch would be useful. Splitting out
patches for the DRM tree and the Tegra tree into different series would
be useful. In this case, they don't depend on each-other.

      reply	other threads:[~2014-05-15 18:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 21:45 [PATCH v2 0/4] ARM: tegra: initial support for Colibri T30 stefan
2014-05-14 21:45 ` [PATCH v2 1/3] ARM: tegra: enable MCP251x CAN controller and DS1307 RTC stefan
2014-05-15 18:15   ` Stephen Warren
2014-05-14 21:45 ` [PATCH v2 2/3] drm/panel: add support for EDT panels stefan
2014-05-15  7:51   ` Thierry Reding
2014-05-15  8:24     ` Stefan Agner
2014-05-15  9:12       ` Thierry Reding
2014-05-15  9:35         ` Philipp Zabel
2014-05-15  9:39           ` Stefan Agner
2014-05-15  8:27     ` Philipp Zabel
2014-05-15  9:08       ` Thierry Reding
2014-05-15  9:30         ` Philipp Zabel
2014-05-15  9:36         ` Stefan Agner
2014-05-14 21:45 ` [PATCH v2 3/3] ARM: tegra: initial add of Colibri T30 stefan
2014-05-15 18:37   ` Stephen Warren [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=53750983.3080705@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marcel@ziswiler.com \
    --cc=stefan@agner.ch \
    --cc=thierry.reding@gmail.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).