linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: device trees for Energy Micro's EFM32 Cortex-M3 SoCs
Date: Tue, 17 Dec 2013 14:17:30 +0100	[thread overview]
Message-ID: <20131217131730.GI14866@pengutronix.de> (raw)
In-Reply-To: <20131217113750.GB5307@netboy>

On Tue, Dec 17, 2013 at 12:37:51PM +0100, Richard Cochran wrote:
> On Mon, Dec 16, 2013 at 08:12:03PM +0100, Uwe Kleine-K?nig wrote:
> 
> > +		cmu: cmu at 400c8000 {
> > +			compatible = "efm32gg,cmu";
> 
> I was able to run this on the EFM32LG without problems.  Are you sure
> this CMU node is specific to the GG, or can it be shared?
I remember me being grumpy because I found some differences between the
GG and some other efm32 device. After looking again I cannot find the
problem. Maybe the LG is compatible but some other is not.

Can I assume your feedback as Tested-by:?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2013-12-17 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 19:09 [GIT PULL] Support for efm32 Uwe Kleine-König
2013-12-16 19:12 ` [PATCH 2/2] ARM: device trees for Energy Micro's EFM32 Cortex-M3 SoCs Uwe Kleine-König
2013-12-17 11:37   ` Richard Cochran
2013-12-17 13:17     ` Uwe Kleine-König [this message]
2013-12-17 15:31       ` Richard Cochran
2013-12-17 16:16         ` Uwe Kleine-König
2013-12-19 22:45 ` [GIT PULL] Support for efm32 Kevin Hilman
  -- strict thread matches above, loose matches on Subject: below --
2013-12-16 19:11 [PATCH 2/2] ARM: device trees for Energy Micro's EFM32 Cortex-M3 SoCs Uwe Kleine-König

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=20131217131730.GI14866@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).