From: Dan Williams <dcbw@redhat.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Mike Rapoport <mike@compulab.co.il>,
rusty@rustcorp.com.au, linux-wireless@vger.kernel.org,
libertas-dev@lists.infradead.org
Subject: Re: [PATCH] libertas: if_sdio: fix buffer alignment in struct if_sdio_card
Date: Wed, 25 Aug 2010 16:59:00 -0500 [thread overview]
Message-ID: <1282773540.28250.29.camel@dcbw.foobar.com> (raw)
In-Reply-To: <201008221557.44607.marek.vasut@gmail.com>
On Sun, 2010-08-22 at 15:57 +0200, Marek Vasut wrote:
> Dne Ne 22. srpna 2010 15:22:08 Mike Rapoport napsal(a):
> > Marek Vasut wrote:
> > > Dne Ne 22. srpna 2010 13:22:40 Mike Rapoport napsal(a):
> > >> The commit 886275ce41a9751117367fb387ed171049eb6148 (param: lock
> > >> if_sdio's lbs_helper_name and lbs_fw_name against sysfs changes)
> > >> introduced new fields into the if_sdio_card structure. It caused
> > >> missalignment of the if_sdio_card.buffer field and failure at driver
> > >>
> > >> load time:
> > >> ~# modprobe libertas_sdio
> > >> [ 62.315124] libertas_sdio: Libertas SDIO driver
> > >> [ 62.319976] libertas_sdio: Copyright Pierre Ossman
> > >> [ 63.020629] DMA misaligned error with device 48
> > >> [ 63.025207] mmci-omap-hs mmci-omap-hs.1: unexpected dma status 800
> > >> [ 66.005035] libertas: command 0x0003 timed out
> > >> [ 66.009826] libertas: Timeout submitting command 0x0003
> > >> [ 66.016296] libertas: PREP_CMD: command 0x0003 failed: -110
> > >>
> > >> Adding explicit alignment attribute for the if_sdio_card.buffer field
> > >> fixes this problem.
> > >>
> > >> Signed-off-by: Mike Rapoport <mike@compulab.co.il>
> > >> ---
> > >>
> > >> drivers/net/wireless/libertas/if_sdio.c | 2 +-
> > >> 1 files changed, 1 insertions(+), 1 deletions(-)
> > >>
> > >> diff --git a/drivers/net/wireless/libertas/if_sdio.c
> > >> b/drivers/net/wireless/libertas/if_sdio.c index ba854c7..87b6349 100644
> > >> --- a/drivers/net/wireless/libertas/if_sdio.c
> > >> +++ b/drivers/net/wireless/libertas/if_sdio.c
> > >> @@ -128,7 +128,7 @@ struct if_sdio_card {
> > >>
> > >> bool helper_allocated;
> > >> bool firmware_allocated;
> > >>
> > >> - u8 buffer[65536];
> > >> + u8 buffer[65536] __attribute__((aligned(4)));
> > >>
> > >> spinlock_t lock;
> > >> struct if_sdio_packet *packets;
> > >
> > > Will this work even on platforms that need some weird DMA destination
> > > address alignment ? I might be totally off with this question though ;-)
> >
> > I've tested it on PXA and OMAP and it works on both.
> > I think that on platforms with weird DMA destination address alignment
> > libertas_sdio will fail anyway because of if_sdio_packet alignment.
>
> You're right ... thanks for clearing this.
>
> Acked-by: Marek Vasut <marek.vasut@gmail.com>
Acked-by: Dan Williams <dcbw@redhat.com>
prev parent reply other threads:[~2010-08-25 21:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 11:22 [PATCH] libertas: if_sdio: fix buffer alignment in struct if_sdio_card Mike Rapoport
2010-08-22 12:59 ` Marek Vasut
2010-08-22 13:22 ` Mike Rapoport
2010-08-22 13:57 ` Marek Vasut
2010-08-25 21:59 ` Dan Williams [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=1282773540.28250.29.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=mike@compulab.co.il \
--cc=rusty@rustcorp.com.au \
/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).