From: Arend van Spriel <arend@broadcom.com>
To: Steeve Morin <steeve.morin@gmail.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: brcmfmac + AP6120 (brcm43362) doesn't connect to WPA2 AP (unprotected ok)
Date: Tue, 10 Feb 2015 22:42:52 +0100 [thread overview]
Message-ID: <54DA7B5C.5040604@broadcom.com> (raw)
In-Reply-To: <CAEZVCP6FzA8c95hxoBm_cDjT8MuoxaijsA1Wx69dO1z8eBoZuQ@mail.gmail.com>
On 02/10/15 21:03, Steeve Morin wrote:
> Okay I've managed to fix it, it was due to a faulty mmc setting in the
> kernel driver from the chip maker.
>
> Basically it was setting a wrong max_blk_count and max_blk_size for
> the MMC host.
>
> Basically, max_blk_count was set wrong, causing a BUG_ON assertion,
> and when patched, because the max_blk_size was wrong, it was
> overflowing the MMC buffer (this is 128k according to the device
> tree).
>
> Thank you for your time, actually talking about it and laying it out
> made me look in the right direction.
Glad to help. Did not expect I would get off that easy ;-)
Regards,
Arend
> Here is the fix.
>
> From 6c92e578748e039dfcfd8e737efdead6cd3e7568 Mon Sep 17 00:00:00 2001
> From: Steeve Morin<steeve.morin@gmail.com>
> Date: Mon, 9 Feb 2015 16:25:49 +0100
> Subject: [PATCH 4/4] Properly set max_blk_count and max_blk_size for the host
> mmc
>
> Signed-off-by: Steeve Morin<steeve.morin@gmail.com>
> ---
> drivers/amlogic/mmc/aml_sdio.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/amlogic/mmc/aml_sdio.c b/drivers/amlogic/mmc/aml_sdio.c
> index 680b95a..8b42f0e 100755
> --- a/drivers/amlogic/mmc/aml_sdio.c
> +++ b/drivers/amlogic/mmc/aml_sdio.c
> @@ -1322,10 +1322,10 @@ static int aml_sdio_probe(struct platform_device *pdev)
> mmc->alldev_claim =&aml_sdio_claim;
> mmc->ios.clock = 400000;
> mmc->ios.bus_width = MMC_BUS_WIDTH_1;
> - mmc->max_blk_count = 4095;
> - mmc->max_blk_size = 4095;
> + mmc->max_blk_count = 256;
> mmc->max_req_size = pdata->max_req_size;
> mmc->max_seg_size = mmc->max_req_size;
> + mmc->max_blk_size = mmc->max_req_size / mmc->max_blk_count;
> mmc->max_segs = 1024;
> mmc->ocr_avail = pdata->ocr_avail;
> mmc->ocr = pdata->ocr_avail;
prev parent reply other threads:[~2015-02-10 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 17:57 brcmfmac + AP6120 (brcm43362) doesn't connect to WPA2 AP (unprotected ok) Steeve Morin
2015-02-09 22:00 ` Arend van Spriel
2015-02-09 22:17 ` Steeve Morin
2015-02-09 23:06 ` Steeve Morin
2015-02-10 0:34 ` Steeve Morin
2015-02-10 1:37 ` Steeve Morin
2015-02-10 17:31 ` Arend van Spriel
2015-02-10 20:03 ` Steeve Morin
2015-02-10 21:42 ` Arend van Spriel [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=54DA7B5C.5040604@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=steeve.morin@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).