linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Alessandro Rubini <rubini-list@gnudd.com>,
	linux-input@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH] ads7846: allocate separate cache lines for tx and rx data
Date: Thu, 16 Jul 2009 00:56:33 -0700	[thread overview]
Message-ID: <200907160056.33302.david-b@pacbell.net> (raw)
In-Reply-To: <20090716072226.GA8113@n2100.arm.linux.org.uk>

On Thursday 16 July 2009, Russell King - ARM Linux wrote:
> ... and until that happens, I suggest you remove the ADS7846 chip from
> your hardware; as that DMA stuff in the driver currently stands, it
> can NEVER work on ARM or any other DMA cache incoherent CPU which uses
> DMA for SPI transfers.

Wrong again.  There's a localized issue, easily enough fixed.
As noted by Alessandro, earlier:  the touchscreen logic does
not have this issue.  Only the ADC logic.

- Dave

p.s. Note by the way that L-A-K is only getting Russell's
     flamage, not the responses disproving his claims.

  reply	other threads:[~2009-07-16  7:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  9:33 [PATCH] ads7846: allocate separate cache lines for tx and rx data Alessandro Rubini
2009-07-15 18:06 ` David Brownell
2009-07-15 19:33 ` Alessandro Rubini
2009-07-16  7:15   ` Russell King - ARM Linux
2009-07-16  7:22     ` Russell King - ARM Linux
2009-07-16  7:56       ` David Brownell [this message]
2009-07-16  7:28     ` David Brownell
2009-07-16 10:00       ` Marek Vasut
2009-07-16 15:35         ` David Brownell
2009-07-16 20:06         ` Russell King - ARM Linux
2009-07-16  7:51   ` David Brownell
2009-07-16  8:15   ` Alessandro Rubini
2009-07-16  8:35     ` David Brownell

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=200907160056.33302.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-input@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rubini-list@gnudd.com \
    /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).