From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Steve Deiters <SteveDeiters@basler.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] arch/powerpc/lib/copy_32.S: Use alternate memcpy for MPC512x and MPC52xx
Date: Thu, 08 Jul 2010 22:09:51 +0200 [thread overview]
Message-ID: <1278619791.1801.4@antares> (raw)
In-Reply-To: <DC489835-1F97-49DA-A00C-7D73D0EC0900@kernel.crashing.org> (from segher@kernel.crashing.org on Thu Jul 8 21:30:33 2010)
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Am 08.07.10 21:30 schrieb(en) Segher Boessenkool:
>> Actually, this is something which might need closer attention - and maybe some support in the device tree indicating which read or write width a device can accept?
>
> There already is "device-width"; the drivers never should use any other access width unless they *know* that will work.
Hmm, unfortunately, it's usage is not clearly documented in mtd-physmap.txt, so I never thought of this parameter. And IMHO the problem goes further - basically *any* chip which is attached to the LPB can be affected by this problem, so it might be better to have a more general approach like a "chip select property".
Cheers, Albrecht.
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2010-07-08 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 16:04 [PATCH] arch/powerpc/lib/copy_32.S: Use alternate memcpy for MPC512x and MPC52xx Steve Deiters
2010-06-29 16:58 ` Segher Boessenkool
2010-07-08 5:10 ` Benjamin Herrenschmidt
2010-07-08 5:38 ` Grant Likely
2010-07-08 14:38 ` Steve Deiters
2010-07-08 15:22 ` Grant Likely
2010-07-08 18:40 ` Albrecht Dreß
2010-07-08 19:30 ` Segher Boessenkool
2010-07-08 20:09 ` Scott Wood
2010-07-09 12:59 ` Segher Boessenkool
2010-07-09 16:18 ` Scott Wood
2010-07-08 20:09 ` Albrecht Dreß [this message]
2010-07-09 13:03 ` Segher Boessenkool
2010-07-11 7:40 ` Milton Miller
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=1278619791.1801.4@antares \
--to=albrecht.dress@arcor.de \
--cc=SteveDeiters@basler.com \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.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).