From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Cc: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 2/2] bcma: use separated function to initialize bus on SoC
Date: Wed, 03 Sep 2014 21:54:38 +0200 [thread overview]
Message-ID: <540771FE.5040600@hauke-m.de> (raw)
In-Reply-To: <1409605867-30051-2-git-send-email-zajec5@gmail.com>
On 09/01/2014 11:11 PM, 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>
Acked-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
> 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(-)
>
next prev parent reply other threads:[~2014-09-03 19:54 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 [this message]
2014-09-04 17:38 ` John W. Linville
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=540771FE.5040600@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).