Devicetree
 help / color / mirror / Atom feed
From: Gerlando Falauto <gerlando.falauto@keymile.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
	"Longchamp, Valentin" <Valentin.Longchamp@keymile.com>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"Brunck, Holger" <Holger.Brunck@keymile.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Simon Guinot <simon@sequanux.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: DT version of kirkwood_ge0x_init()
Date: Wed, 05 Jun 2013 11:37:36 +0200	[thread overview]
Message-ID: <51AF06E0.6040103@keymile.com> (raw)
In-Reply-To: <51AEFF26.8080004@gmail.com>

Hi Sebastian,

thanks for the info.

On 06/05/2013 11:04 AM, Sebastian Hesselbarth wrote:
[...]
>
> I have irqchip and clocksource drivers ready for Orion SoCs (Kirkwood,
> Dove, Orion5x, MV78x00). Just need some time to rebase and send patches.

[sorry we've moved to a different topic]
[adding Thomas Gleixner]
You mean the driver in arch/arm/plat-orion/gpio.c or the generic
one in drivers/gpio/gpio-mvebu.c?

Because the first one looks like it's using generic irq chip already.
For the second one I don't understand how you can handle the per-CPU 
registers which are peculiar to MV78200/ArmadaXP.
Unless there's already patches on top of Thomas's rework for the per-CPU 
registers.

Thank you,
Gerlando

  reply	other threads:[~2013-06-05  9:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 10:18 DT version of kirkwood_ge0x_init() Gerlando Falauto
     [not found] ` <51ADBEE0.5040500-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-06-04 10:34   ` Sebastian Hesselbarth
     [not found]     ` <51ADC2C2.6010106-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-04 10:43       ` Jason Cooper
2013-06-04 11:59         ` Simon Guinot
     [not found]           ` <20130604115927.GJ7626-tZfvYpCFA3RN6yImKYG91Q@public.gmane.org>
2013-06-04 12:05             ` Jason Cooper
2013-06-04 12:18               ` Simon Guinot
     [not found]               ` <20130604120500.GZ3803-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2013-06-04 13:10                 ` Jason Cooper
2013-06-04 20:53     ` Gerlando Falauto
     [not found]       ` <51AE53D4.5070208-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-06-05  9:04         ` Sebastian Hesselbarth
2013-06-05  9:37           ` Gerlando Falauto [this message]
     [not found]             ` <51AF06E0.6040103-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2013-06-05  9:45               ` Gregory CLEMENT
2013-06-05  9:49               ` Sebastian Hesselbarth
2013-06-05  9:55                 ` Gerlando Falauto
     [not found]           ` <51AEFF26.8080004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-05 13:23             ` Jason Cooper

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=51AF06E0.6040103@keymile.com \
    --to=gerlando.falauto@keymile.com \
    --cc=Holger.Brunck@keymile.com \
    --cc=Valentin.Longchamp@keymile.com \
    --cc=andrew@lunn.ch \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=simon@sequanux.org \
    --cc=tglx@linutronix.de \
    /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