From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] smsc95xx: align buffers to cache line size
Date: Tue, 10 Jul 2012 11:34:09 +0200 [thread overview]
Message-ID: <201207101134.09540.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAA3CPjXiekVdR=XMy84KMiaXKLW1h9+aSPfSFn+gR8oXiLqxDA@mail.gmail.com>
Dear Ilya Yanok,
> Hi Marek,
>
> On Tue, Jul 10, 2012 at 6:17 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> > > Well, of course we need proper alignment for cache stuff (well,
> > > actually
> >
> > we
> >
> > > can skip this alignment thing for the buffer we will flush as long as
> > > all buffers we are going to invalidate are properly aligned/sized...
> > > but
> >
> > that's
> >
> > > too tricky, personally I'd prefer every DMAed buffer to be cache-line
> > > aligned/sized).
> > >
> > > And this patch actually adds the alignment for the smsc95xx driver's
> > > buffers. In your initial reply you said it will be broken on systems
> > > with ARCH_DMA_MINALIGN < 32, so I'm asking what makes you think so?
> >
> > ALLOC_CACHE_ALIGN_BUFFER(u32, tmpbuf, 1); this stuff maybe? It'll be
> > aligned to
> > 16 bytes for arch with 16 byte cachelines.
>
> Yes, and this is exactly what we need.
It isn't, EHCI needs it aligned on 32 byte boundary.
> Regards, Ilya.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-10 9:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 13:53 [U-Boot] [PATCH] smsc95xx: align buffers to cache line size Ilya Yanok
2012-07-08 18:59 ` Marek Vasut
2012-07-08 19:35 ` Ilya Yanok
2012-07-08 21:31 ` Marek Vasut
2012-07-08 22:32 ` Ilya Yanok
2012-07-09 0:45 ` Marek Vasut
2012-07-09 18:33 ` Ilya Yanok
2012-07-10 2:17 ` Marek Vasut
2012-07-10 8:48 ` Ilya Yanok
2012-07-10 9:34 ` Marek Vasut [this message]
2012-07-10 11:25 ` Ilya Yanok
2012-07-10 15:53 ` Marek Vasut
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=201207101134.09540.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.