From: richardcochran@gmail.com (Richard Cochran)
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 12:37:51 +0100 [thread overview]
Message-ID: <20131217113750.GB5307@netboy> (raw)
In-Reply-To: <1387221123-6794-1-git-send-email-u.kleine-koenig@pengutronix.de>
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?
Thanks,
Richard
> + reg = <0x400c8000 0x400>;
> + interrupts = <32>;
> + #clock-cells = <1>;
> + };
WARNING: multiple messages have this Message-ID (diff)
From: Richard Cochran <richardcochran-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Uwe Kleine-König"
<u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 2/2] ARM: device trees for Energy Micro's EFM32 Cortex-M3 SoCs
Date: Tue, 17 Dec 2013 12:37:51 +0100 [thread overview]
Message-ID: <20131217113750.GB5307@netboy> (raw)
In-Reply-To: <1387221123-6794-1-git-send-email-u.kleine-koenig-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On Mon, Dec 16, 2013 at 08:12:03PM +0100, Uwe Kleine-König wrote:
> + cmu: cmu@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?
Thanks,
Richard
> + reg = <0x400c8000 0x400>;
> + interrupts = <32>;
> + #clock-cells = <1>;
> + };
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-12-17 11:37 UTC|newest]
Thread overview: 14+ 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-16 19:12 ` Uwe Kleine-König
2013-12-17 11:37 ` Richard Cochran [this message]
2013-12-17 11:37 ` Richard Cochran
2013-12-17 13:17 ` Uwe Kleine-König
2013-12-17 13:17 ` Uwe Kleine-König
2013-12-17 15:31 ` Richard Cochran
2013-12-17 15:31 ` Richard Cochran
2013-12-17 16:16 ` Uwe Kleine-König
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
2013-12-16 19:11 ` 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=20131217113750.GB5307@netboy \
--to=richardcochran@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.