public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: neil@fatboyfat.co.uk (Neil Greatorex)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 for 3.10] Introduce a Marvell EBU MBus driver
Date: Thu, 28 Mar 2013 22:31:45 +0000 (GMT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1303282228350.28248@vroombuntu> (raw)
In-Reply-To: <CABx3TkVgNEZZBKyWzz=oEbnsqk6uCST78b05H6HnNX0XWYEyWQ@mail.gmail.com>

Ryan,

On Wed, 27 Mar 2013, Ryan Press wrote:

> Hi Neil,
>
> On Wed, Mar 27, 2013 at 6:32 PM, Neil Greatorex <neil@fatboyfat.co.uk> wrote:
>> Thomas,
>>
>> This set of patches seems to break the mvsdio driver (and hence
>> mwifiex_sdio) on the Globalscale Mirabox. I believe this is because
>> mvsdio.c contains a function mv_conf_mbus_windows that seems to
>> conflict with the new mbus driver. I don't understand enough about the
>> hardware (without the datasheets anyway) to be able to understand the
>> exact problem, but I hope that this is enough to point you (or someone
>> else) to it!
>
> I've been working on getting my Mirabox running with the mainline
> kernel.  There seems to be a problem with DMA and the mvsdio driver,
> which causes the exact same dmesg for me.  Try loading the mvsdio
> driver like so: "modprobe mvsdio nodma=1" and then modprobe the
> mwifiex_sdio driver and see if it works for you too.
>
> Ryan
>

Thanks for the information. Yes that does fix the issue, because the 
mvsdio driver then no longer needs to use the SDRAM address windows to do 
DMA transfers. However, it turns out that by doing this you are masking 
the bug that what actually introduced in the mbus driver (see my earlier 
reply to Thomas). Still, this does mean that the wifi adapter actually 
works now as even with the mbus fix it's unreliable, so thanks.

Cheers,
Neil

  reply	other threads:[~2013-03-28 22:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 16:59 [PATCH v3 for 3.10] Introduce a Marvell EBU MBus driver Thomas Petazzoni
2013-03-21 16:59 ` [PATCH v3 1/7] bus: introduce an " Thomas Petazzoni
2013-03-28 19:08   ` Jason Cooper
2013-03-21 16:59 ` [PATCH v3 2/7] arm: mach-mvebu: convert to use mvebu-mbus driver Thomas Petazzoni
2013-03-21 16:59 ` [PATCH v3 3/7] arm: mach-kirkwood: " Thomas Petazzoni
2013-03-21 16:59 ` [PATCH v3 4/7] arm: mach-dove: " Thomas Petazzoni
2013-03-21 16:59 ` [PATCH v3 5/7] arm: mach-orion5x: " Thomas Petazzoni
2013-03-21 16:59 ` [PATCH v3 6/7] arm: mach-mv78xx0: convert to use the " Thomas Petazzoni
2013-03-21 16:59 ` [PATCH v3 7/7] arm: plat-orion: remove addr-map code Thomas Petazzoni
2013-03-30 21:31   ` Jason Cooper
2013-03-21 17:30 ` [PATCH v3 for 3.10] Introduce a Marvell EBU MBus driver Arnd Bergmann
2013-03-21 18:46   ` Jason Cooper
2013-03-28  1:32     ` Neil Greatorex
2013-03-28  1:49       ` Ryan Press
2013-03-28 22:31         ` Neil Greatorex [this message]
2013-03-28  7:33       ` Thomas Petazzoni
2013-03-28 22:27         ` Neil Greatorex
2013-03-29  1:00           ` Jason Cooper
2013-03-30 20:21           ` Jason Cooper
2013-03-30 20:41             ` Neil Greatorex
2013-03-30 21:14               ` 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=alpine.DEB.2.02.1303282228350.28248@vroombuntu \
    --to=neil@fatboyfat.co.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