From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: DT version of kirkwood_ge0x_init()
Date: Wed, 05 Jun 2013 11:45:07 +0200 [thread overview]
Message-ID: <51AF08A3.6030407@free-electrons.com> (raw)
In-Reply-To: <51AF06E0.6040103@keymile.com>
Hi Geraldo,
On 06/05/2013 11:37 AM, Gerlando Falauto wrote:
> 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.
>
Currently we don't use the per-CPU register for Armada XP (I am not sure for
MV78200). it was the cause of bugs and we didn't find how to properly fix
them, so the solution was to not use the per-cpu part.
> Thank you,
> Gerlando
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Gregory CLEMENT <gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Gerlando Falauto
<gerlando.falauto-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Cc: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
"Longchamp,
Valentin"
<Valentin.Longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"Brunck,
Holger" <Holger.Brunck-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
Simon Guinot <simon-jKBdWWKqtFpg9hUCZPvPmw@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: DT version of kirkwood_ge0x_init()
Date: Wed, 05 Jun 2013 11:45:07 +0200 [thread overview]
Message-ID: <51AF08A3.6030407@free-electrons.com> (raw)
In-Reply-To: <51AF06E0.6040103-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Hi Geraldo,
On 06/05/2013 11:37 AM, Gerlando Falauto wrote:
> 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.
>
Currently we don't use the per-CPU register for Armada XP (I am not sure for
MV78200). it was the cause of bugs and we didn't find how to properly fix
them, so the solution was to not use the per-cpu part.
> Thank you,
> Gerlando
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-06-05 9:45 UTC|newest]
Thread overview: 28+ 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:18 ` Gerlando Falauto
2013-06-04 10:34 ` Sebastian Hesselbarth
2013-06-04 10:34 ` Sebastian Hesselbarth
2013-06-04 10:43 ` Jason Cooper
2013-06-04 10:43 ` Jason Cooper
2013-06-04 11:59 ` Simon Guinot
2013-06-04 11:59 ` Simon Guinot
2013-06-04 12:05 ` Jason Cooper
2013-06-04 12:05 ` Jason Cooper
2013-06-04 12:18 ` Simon Guinot
2013-06-04 12:18 ` Simon Guinot
2013-06-04 13:10 ` Jason Cooper
2013-06-04 13:10 ` Jason Cooper
2013-06-04 20:53 ` Gerlando Falauto
2013-06-04 20:53 ` Gerlando Falauto
2013-06-05 9:04 ` Sebastian Hesselbarth
2013-06-05 9:04 ` Sebastian Hesselbarth
2013-06-05 9:37 ` Gerlando Falauto
2013-06-05 9:37 ` Gerlando Falauto
2013-06-05 9:45 ` Gregory CLEMENT [this message]
2013-06-05 9:45 ` Gregory CLEMENT
2013-06-05 9:49 ` Sebastian Hesselbarth
2013-06-05 9:49 ` Sebastian Hesselbarth
2013-06-05 9:55 ` Gerlando Falauto
2013-06-05 9:55 ` Gerlando Falauto
2013-06-05 13:23 ` Jason Cooper
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=51AF08A3.6030407@free-electrons.com \
--to=gregory.clement@free-electrons.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.