From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, Hauke Mehrtens <hauke@hauke-m.de>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 2/2] bcma: use separated function to initialize bus on SoC
Date: Thu, 4 Sep 2014 13:38:34 -0400 [thread overview]
Message-ID: <20140904173833.GG3467@tuxdriver.com> (raw)
In-Reply-To: <1409605867-30051-2-git-send-email-zajec5@gmail.com>
On Mon, Sep 01, 2014 at 11:11:07PM +0200, Rafał Miłecki wrote:
> This is required to split SoC bus init into two phases. The later one
> (which includes scanning) should be called when kalloc is available.
>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> ---
> John: please note this patch touches arch/mips/bcm47xx/setup.c
>
> This patches is a first step of simplifying MIPS booting process on
> Broadcom SoCs. My research described in:
> > Booting bcm47xx (bcma & stuff), sharing code with bcm53xx
> e-mail thread explained how we could get rid of all these early scanning
> tricks. The main idea is to postpone bus initialization a bit and use
> all standard calls then. So far we were doing it so early we had to
> avoid kalloc.
> ---
> arch/mips/bcm47xx/setup.c | 4 ++++
> drivers/bcma/host_soc.c | 11 +++++++++--
> include/linux/bcma/bcma_soc.h | 1 +
> 3 files changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/bcm47xx/setup.c b/arch/mips/bcm47xx/setup.c
> index 2b63e7e..fff6ed4 100644
> --- a/arch/mips/bcm47xx/setup.c
> +++ b/arch/mips/bcm47xx/setup.c
> @@ -202,6 +202,10 @@ static void __init bcm47xx_register_bcma(void)
>
> err = bcma_host_soc_register(&bcm47xx_bus.bcma);
> if (err)
> + panic("Failed to register BCMA bus (err %d)", err);
> +
> + err = bcma_host_soc_init(&bcm47xx_bus.bcma);
> + if (err)
> panic("Failed to initialize BCMA bus (err %d)", err);
>
> bcm47xx_fill_bcma_boardinfo(&bcm47xx_bus.bcma.bus.boardinfo, NULL);
This hunk looks wrong. Is it missing indentation? Or should a line
be removed at the top?
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-09-04 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 21:11 [PATCH 1/2] bcma: move bus struct setup into early part of host specific code Rafał Miłecki
2014-09-01 21:11 ` [PATCH 2/2] bcma: use separated function to initialize bus on SoC Rafał Miłecki
2014-09-03 19:54 ` Hauke Mehrtens
2014-09-04 17:38 ` John W. Linville [this message]
2014-09-04 18:04 ` Rafał Miłecki
2014-09-04 18:07 ` John W. Linville
2014-09-03 19:48 ` [PATCH 1/2] bcma: move bus struct setup into early part of host specific code Hauke Mehrtens
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=20140904173833.GG3467@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=zajec5@gmail.com \
/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.