From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/17] SA11x0 cleanups (mainly assabet/neponset)
Date: Fri, 3 Feb 2012 20:53:46 +0000 [thread overview]
Message-ID: <20120203205346.GL14129@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.02.1202031533030.2759@xanadu.home>
On Fri, Feb 03, 2012 at 03:43:43PM -0500, Nicolas Pitre wrote:
> I've quickly looked through this series and this all looks sensible.
>
> Acked-by: Nicolas Pitre <nico@linaro.org>
Thanks.
> My knowledge of the SA1111 chip was never extensive, and the little I
> had did fade away at this point. So it might not be relevant for me to
> give any comment on the other series. Except that I thought that DMA
> was terminally broken on that chip, hence I'm surprized to see OHCI
> support for it.
It is rather badly broken, but the hack to move the kernel 1MB into
SDRAM and dmabounce continues to do their jobs, making it work.
And let's also not forget that the errata documentation was (probably)
one of the worst - I have this comment from years back in the code...
/*
* Don't believe the specs! Take them, throw them outside. Leave them
* there for a week. Spit on them. Walk on them. Stamp on them.
* Pour gasoline over them and finally burn them. Now think about coding.
* - The October 1999 errata (278260-007) says its bit 13, 1 to enable.
* - The Feb 2001 errata (278260-010) says that the previous errata
* (278260-009) is wrong, and its bit actually 12, fixed in spec
* 278242-003.
* - The SA1111 manual (278242) says bit 12, but 0 to enable.
* - Reality is bit 13, 1 to enable.
* -- rmk
*/
#define SKCR_OE_EN (1<<13)
In those days, we had specifications on paper!
prev parent reply other threads:[~2012-02-03 20:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 19:30 [PATCH 00/17] SA11x0 cleanups (mainly assabet/neponset) Russell King - ARM Linux
2012-02-03 19:31 ` [PATCH 01/17] ARM: sa11x0: convert to use DEFINE_RES_xxx macros Russell King - ARM Linux
2012-02-03 19:31 ` [PATCH 02/17] ARM: sa11x0: assabet: deassert QMUTE to codec while codec is unpowered Russell King - ARM Linux
2012-02-03 19:32 ` [PATCH 03/17] ARM: sa11x0: assabet: avoid glitching GPIOs when setting outputs Russell King - ARM Linux
2012-02-03 19:32 ` [PATCH 04/17] ARM: sa11x0: assabet: ensure that GPIO27 is driven Russell King - ARM Linux
2012-02-03 19:32 ` [PATCH 05/17] ARM: sa11x0: neponset: fix interrupt setup Russell King - ARM Linux
2012-02-03 19:33 ` [PATCH 06/17] ARM: sa11x0: neponset: provide function to manipulate NCR_0 Russell King - ARM Linux
2012-02-03 19:33 ` [PATCH 07/17] ARM: sa11x0: neponset: shuffle some code around Russell King - ARM Linux
2012-02-03 19:33 ` [PATCH 08/17] ARM: sa11x0: neponset: add driver .owner initializer Russell King - ARM Linux
2012-02-03 19:34 ` [PATCH 09/17] ARM: sa11x0: neponset: save and restore MDM_CTL_0 Russell King - ARM Linux
2012-02-03 19:34 ` [PATCH 10/17] ARM: sa11x0: neponset: dynamically create neponset child devices Russell King - ARM Linux
2012-02-03 19:34 ` [PATCH 11/17] ARM: sa11x0: neponset: implement support for sparse IRQs Russell King - ARM Linux
2012-02-03 19:35 ` [PATCH 12/17] ARM: sa11x0: neponset: get parent IRQ from neponset device resource Russell King - ARM Linux
2012-02-03 19:35 ` [PATCH 13/17] ARM: sa11x0: neponset: place smc91x and sa1111 resources in neponset device Russell King - ARM Linux
2012-02-03 19:35 ` [PATCH 14/17] ARM: sa11x0: neponset: suspend/resume in _noirq state Russell King - ARM Linux
2012-02-03 19:36 ` [PATCH 15/17] ARM: sa11x0: assabet/neponest: create neponset device in assabet.c Russell King - ARM Linux
2012-02-03 19:36 ` [PATCH 16/17] ARM: sa11x0: neponset: move register definitions to neponset.c Russell King - ARM Linux
2012-02-03 19:36 ` [PATCH 17/17] ARM: sa11x0: neponset: don't static map neponset registers Russell King - ARM Linux
2012-02-03 20:43 ` [PATCH 00/17] SA11x0 cleanups (mainly assabet/neponset) Nicolas Pitre
2012-02-03 20:53 ` Russell King - ARM Linux [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=20120203205346.GL14129@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).