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 v6 0/3] Updated Cortex-M3 series
Date: Wed, 26 Sep 2012 21:27:59 +0200	[thread overview]
Message-ID: <20120926192759.GC19685@pengutronix.de> (raw)
In-Reply-To: <20120926180349.GF15578@mudshark.cambridge.arm.com>

Hi Will,

On Wed, Sep 26, 2012 at 07:03:49PM +0100, Will Deacon wrote:
> On Tue, Sep 25, 2012 at 04:00:26PM +0100, Uwe Kleine-K?nig wrote:
> > On Tue, Sep 25, 2012 at 03:47:26PM +0100, Jonathan Austin wrote:
> > > Looking at the patch series at a very superficial level, I wonder why
> > > you've chosen not to include any Kconfig/NVIC support at this stage,
> > > especially as you've posted some before and there appears to be
> > > something (presumably) working in your efm32 branch...
> > >
> > > It would be a shame to spend time on merging the basic support if there
> > > are issues that mean the interrupt support won't follow.
> > I plan to expand common/gic.c for interrupt support. Currently I don't
> > do much though because getting feedback and the changes into mainline is
> > quite hard and I don't want to spend time now and hear later that I did
> > it wrong or something. So I put my efforts on hold and only ping from
> > time to time.  :-(
> 
> My personal view is that merging the code without support for interrupts is
> fairly pointless, so the nvic code should certainly be included. I
> wouldn't worry too much about merging it with gic.c initially. That can come
That would be ok for me, too.
> later, especially as we'll need to prise the gic into drivers/ at some point
> (it should be shared with arm64).
> 
> I think one reason for the lack of feedback is the inability for people to
> run this code themselves. I believe Jonny was trying to get started with an
> FPGA / simulation, but some hardware would be great if there's any available...
I think you can order the efm32 devboard[1] via the usual channels.
I don't know if Energymicro has interest to give out some boards into
the community at an reduced price. I will ask.

Best regards
Uwe

[1] http://www.energymicro.com/tools/efm32-giant-gecko-development-kit

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

  reply	other threads:[~2012-09-26 19:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 10:10 [PATCH v6 0/3] Updated Cortex-M3 series Uwe Kleine-König
2012-08-03 10:10 ` [PATCH v6 1/3] ARM: make cr_alignment read-only #ifndef CONFIG_CPU_CP15 Uwe Kleine-König
2012-08-03 10:10 ` [PATCH v6 2/3] Cortex-M3: Add base support for Cortex-M3 Uwe Kleine-König
2012-08-03 10:10 ` [PATCH v6 3/3] Cortex-M3: Add support for exception handling Uwe Kleine-König
2012-08-03 14:07 ` [PATCH v6 0/3] Updated Cortex-M3 series Arnd Bergmann
2012-08-03 14:50   ` Uwe Kleine-König
2012-08-03 15:17     ` Shiraz Hashim
2012-08-04 13:57       ` Uwe Kleine-König
2012-08-03 15:37     ` Jonathan Austin
2012-08-16 20:29 ` Uwe Kleine-König
2012-09-21 19:00   ` Uwe Kleine-König
2012-09-25 14:47     ` Jonathan Austin
2012-09-25 15:00       ` Uwe Kleine-König
2012-09-26 18:03         ` Will Deacon
2012-09-26 19:27           ` Uwe Kleine-König [this message]
2012-10-17  8:14             ` Uwe Kleine-König
2012-10-08 15:43 ` new branch for linux-next [Was: [PATCH v6 0/3] Updated Cortex-M3 series] Uwe Kleine-König
2012-10-08 15:47   ` Russell King - ARM Linux
2012-10-11 22:51     ` Stephen Rothwell
2012-10-15 23:08   ` Stephen Rothwell

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=20120926192759.GC19685@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).