From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RFC] USB: fsl_udc_core: fix build-failure for ARM
Date: Fri, 6 May 2011 19:47:47 +0100 [thread overview]
Message-ID: <20110506184747.GA3390@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110506100310.GT11574@pengutronix.de>
On Fri, May 06, 2011 at 12:03:10PM +0200, Uwe Kleine-K?nig wrote:
> Hi Russell,
>
> On Fri, May 06, 2011 at 10:04:49AM +0100, Russell King - ARM Linux wrote:
> > On Fri, May 06, 2011 at 11:00:05AM +0200, Uwe Kleine-K?nig wrote:
> > > I'm unsure about getting rid of the flush_dcache_range. If powerpc needs
> > > a flush ARM probably does, too, no?
> > > If so, what it the right thing to do? Implement flush_dcache_range for
> > > ARM (just wrapping flush_dcache_page?)?
> >
> > On ARM, we assume all new pages have dirty dcache, which allows us to
> > neatly end the ever-increasing quantity of drivers which need to be
> > patched to work on ARM. PowerPC doesn't do this.
> Unless I'm missing something the cache flushed here isn't necessarily
> for a new page. (And even if the flush isn't needed here for ARM, not
> having flush_dcache_range results in #ifdefs for each user of it. So a
> definition would be nice, wouldn't it?)
Well, the folk introducing it should have added it to cachetlb.txt so
that other folk know what the intentions of it are. At the moment it
seems to be an unofficial extension with unknown semantics. Maybe the
PPC folk can clear it up and fix other arches if they wish to make it
an official arch cachetlb extension.
next prev parent reply other threads:[~2011-05-06 18:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110505135029.0c068b8e@wker>
2011-05-06 9:00 ` [PATCH] [RFC] USB: fsl_udc_core: fix build-failure for ARM Uwe Kleine-König
2011-05-06 9:04 ` Russell King - ARM Linux
2011-05-06 10:03 ` Uwe Kleine-König
2011-05-06 18:47 ` Russell King - ARM Linux [this message]
2011-05-11 6:39 ` Uwe Kleine-König
2011-05-11 15:54 ` Greg KH
2011-05-11 16:29 ` Russell King - ARM Linux
2011-05-22 7:20 ` Uwe Kleine-König
2011-06-21 9:32 ` Eric Miao
2011-06-21 9:48 ` Russell King - ARM Linux
2011-06-21 9:53 ` Russell King - ARM Linux
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=20110506184747.GA3390@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.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;
as well as URLs for NNTP newsgroup(s).