From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: dmaengine: ARM pl080 misidentified as Samsung pl080s
Date: Thu, 24 Mar 2016 15:16:47 +0000 [thread overview]
Message-ID: <20160324151647.GS19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160324105651.GA20489@sig21.net>
On Thu, Mar 24, 2016 at 11:56:51AM +0100, Johannes Stezenbach wrote:
> Hi,
>
> commit da1b6c05b8b5bd ("dmaengine: PL08x: Add support for PL080S variant")
> added this hunk:
>
> static struct amba_id pl08x_ids[] = {
> + /* Samsung PL080S variant */
> + {
> + .id = 0x0a141080,
> + .mask = 0xffffffff,
> + .data = &vendor_pl080s,
> + },
> /* PL080 */
>
> However, 0x0a141080 happens to be the ID of the
> ARM PL080, too:
> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0196g/I54627.html
>
> Since the PL080S has the configuration register at a different
> address the driver doesn't work for ARM PL080 anymore.
Vendors have got into serious trouble in the past over IDs claiming that
some other legal entity being the vendor. A certain buggy ARM926 clone
comes to mind, and they were forced to respin their silicon as a result.
It sounds like Samsung have made the same idiotic mistake. I suggest
reverting the offending commit. This behaviour really isn't on.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-03-24 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 10:56 dmaengine: ARM pl080 misidentified as Samsung pl080s Johannes Stezenbach
2016-03-24 15:16 ` Russell King - ARM Linux [this message]
2016-03-25 23:08 ` Tomasz Figa
2016-03-25 23:50 ` Johannes Stezenbach
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=20160324151647.GS19428@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).