From: gerlando.falauto@keymile.com (Gerlando Falauto)
To: linux-arm-kernel@lists.infradead.org
Subject: DT version of kirkwood_ge0x_init()
Date: Wed, 05 Jun 2013 11:55:10 +0200 [thread overview]
Message-ID: <51AF0AFE.1000503@keymile.com> (raw)
In-Reply-To: <51AF0990.7090406@gmail.com>
On 06/05/2013 11:49 AM, Sebastian Hesselbarth wrote:
> On 06/05/13 11:37, Gerlando Falauto wrote:
>> 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?
>
> For Kirkwood and Dove, DT kernels use gpio-mvebu. And that is there
> from a time when there was no irqdomain support in generic chip. That
> should be updated.
I know, that's why I was wondering how it is possible to update this
driver and yet support per-cpu registers.
But I am admittedly not 100% sure I know what I'm talking about.
Anyway, could you please Cc: me when you post those patches?
Thank you,
Gerlando
next prev parent reply other threads:[~2013-06-05 9:55 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
2013-06-04 10:34 ` Sebastian Hesselbarth
2013-06-04 10:43 ` Jason Cooper
2013-06-04 11:59 ` Simon Guinot
2013-06-04 12:05 ` Jason Cooper
2013-06-04 12:18 ` Simon Guinot
2013-06-04 13:10 ` Jason Cooper
2013-06-04 20:53 ` Gerlando Falauto
2013-06-05 9:04 ` Sebastian Hesselbarth
2013-06-05 9:37 ` Gerlando Falauto
2013-06-05 9:45 ` Gregory CLEMENT
2013-06-05 9:49 ` Sebastian Hesselbarth
2013-06-05 9:55 ` Gerlando Falauto [this message]
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=51AF0AFE.1000503@keymile.com \
--to=gerlando.falauto@keymile.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 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).