linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	"Michael Buesch" <m@bues.ch>, "Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: [PATCH] ssb: fix init regression with SoCs
Date: Mon, 05 Dec 2011 17:44:14 -0600	[thread overview]
Message-ID: <4EDD574E.9090801@lwfinger.net> (raw)
In-Reply-To: <1323123591-11982-1-git-send-email-hauke@hauke-m.de>

On 12/05/2011 04:19 PM, Hauke Mehrtens wrote:
> This fixes a Data bus error on some SoCs. The first fix for this
> problem did not solve it on all devices.
>      commit 6ae8ec27868bfdbb815287bee8146acbefaee867
>      Author: Rafał Miłecki<zajec5@gmail.com>
>      Date:   Tue Jul 5 17:25:32 2011 +0200
>          ssb: fix init regression of hostmode PCI core
>
> In ssb_pcicore_fix_sprom_core_index() the sprom on the PCI core is
> accessed, but the sprom only exists when the ssb bus is connected over
> a PCI bus to the rest of the system and not when the SSB Bus is the
> main system bus. SoCs sometimes have a PCI host controller and there
> this code will not be executed, but there are some old SoCs with an PCI
> controller in client mode around and ssb_pcicore_fix_sprom_core_index()
> should not be called on these devices too. The PCI controller on these
> devices are unused, but without this fix it results in an Data bus
> error when it gets initialized.
>
> CC: Michael Buesch<m@bues.ch>
> CC: Rafał Miłecki<zajec5@gmail.com>
> Signed-off-by: Hauke Mehrtens<hauke@hauke-m.de>
> ---
>   drivers/ssb/driver_pcicore.c |    8 ++++++--
>   1 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/ssb/driver_pcicore.c b/drivers/ssb/driver_pcicore.c
> index 84c934c..520e828 100644
> --- a/drivers/ssb/driver_pcicore.c
> +++ b/drivers/ssb/driver_pcicore.c
> @@ -517,10 +517,14 @@ static void ssb_pcicore_pcie_setup_workarounds(struct ssb_pcicore *pc)
>
>   static void __devinit ssb_pcicore_init_clientmode(struct ssb_pcicore *pc)
>   {
> -	ssb_pcicore_fix_sprom_core_index(pc);
> +	struct ssb_device *pdev = pc->dev;
> +	struct ssb_bus *bus = pdev->bus;
> +
> +	if (bus->bustype == SSB_BUSTYPE_PCI)
> +		ssb_pcicore_fix_sprom_core_index(pc);
>
>   	/* Disable PCI interrupts. */
> -	ssb_write32(pc->dev, SSB_INTVEC, 0);
> +	ssb_write32(pdev, SSB_INTVEC, 0);

As bus == pc->dev->bus is only used once, why bother to create it? If you were 
to change that, then pdev == pc->dev is only used once. Any real reason to 
change the lines above?

Larry



  reply	other threads:[~2011-12-05 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05 22:19 [PATCH] ssb: fix init regression with SoCs Hauke Mehrtens
2011-12-05 23:44 ` Larry Finger [this message]
2011-12-08 22:37   ` Hauke Mehrtens
2011-12-06 19:56 ` John W. Linville

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=4EDD574E.9090801@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=hauke@hauke-m.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=m@bues.ch \
    --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).