linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: alex@digriz.org.uk (Alexander Clouter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [ARM] kirkwood: combine support for openrd base/client ?support
Date: Tue, 13 Oct 2009 15:41:01 +0100	[thread overview]
Message-ID: <t4geq6-pm4.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: ad9478410910120746g2ce82af1t71a84ea02e9eecb7@mail.gmail.com

Joel Stanley <joel@jms.id.au> wrote:
>
> On Mon, Oct 12, 2009 at 18:16, Dieter Kiermaier <dk-arm-linux@gmx.de> wrote:
>>> If you can point out where I should be looking, I will have a look and
>>> if I can find it I will enable it.
>>
>> I'm sorry, but I haven't an openrd-client board :(
>> Maybe someone else can help us?
> 
> I have tested Alexander's patch on my openrd-client board, applied to
> Linus' tree.  It boots and networking works fine.
> 
> I also added calls to initialise i2c and pcie based on the patch by
> Simon Kagstrom, and both devices appear to work.  The diff I added is
> attached.
> 
Hmmm, seems to now be working for me too, I have updated from 32-rc2 to 
rc4 so that probably fixed something along the way I suppose.

> Author: Joel Stanley <joel@jms.id.au>
> Date:   Tue Oct 13 00:02:04 2009 +1030
> 
>    Add pcie and i2c initalisation
> 
> diff --git a/arch/arm/mach-kirkwood/openrd-setup.c
> b/arch/arm/mach-kirkwood/openrd-setup.c
> index 6bdeeab..d5504e2 100644
> --- a/arch/arm/mach-kirkwood/openrd-setup.c
> +++ b/arch/arm/mach-kirkwood/openrd-setup.c
> @@ -80,6 +80,10 @@ static void __init openrd_init(void)
> #endif
>        kirkwood_sata_init(&openrd_sata_data);
>        kirkwood_sdio_init(&openrd_mvsdio_data);
> +
> +       kirkwood_i2c_init();
> +
> +       kirkwood_pcie_init();
> }
> 
> #ifdef CONFIG_MACH_OPENRD_BASE
>
I think to match the coding style of the other kirkwood boards this 
should go in a seperate pci_init function:
----
static int __init openrd_base_pci_init(void)
{
        kirkwood_pcie_init();

        return 0;
}
subsys_initcall(openrd_base_pci_init);
----

Well, included is my 'new' version with Nico's recommendation to remove 
the unnecessary ifdef's.

Cheers

-- 
Alexander Clouter
.sigmonster says: Pie are not square.  Pie are round.  Cornbread are square.

      reply	other threads:[~2009-10-13 14:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 12:39 [PATCH] [ARM] kirkwood: combine support for openrd base/client support Alexander Clouter
2009-10-09 12:41 ` Alexander Clouter
2009-10-09 14:00 ` Dieter Kiermaier
2009-10-09 14:03   ` Dhaval Vasa
2009-10-09 14:03   ` Dhaval Vasa
2009-10-09 14:05   ` Alexander Clouter
2009-10-09 14:24     ` Dieter Kiermaier
2009-10-13  3:20     ` Nicolas Pitre
2009-10-13 14:28       ` [PATCH] [ARM] kirkwood: combine support for openrd base/client?support Alexander Clouter
2009-10-09 15:24   ` [PATCH] [ARM] kirkwood: combine support for openrd base/client support Alexander Clouter
2009-10-12  6:36     ` Dieter Kiermaier
2009-10-12  7:31       ` Alexander Clouter
2009-10-12  7:46         ` Dieter Kiermaier
2009-10-12 14:46           ` Joel Stanley
2009-10-13 14:41             ` Alexander Clouter [this message]

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=t4geq6-pm4.ln1@chipmunk.wormnet.eu \
    --to=alex@digriz.org.uk \
    --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).