From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: David Brownell <david-b@pacbell.net>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
linux-ide@vger.kernel.org,
DaVinci <davinci-linux-open-source@linux.davincidsp.com>
Subject: Re: [patch 2.6.30-rc2 2/2] palm_bk3710: UDMA performance fix
Date: Thu, 23 Apr 2009 22:48:26 +0200 [thread overview]
Message-ID: <200904232248.26284.bzolnier@gmail.com> (raw)
In-Reply-To: <200904221529.23427.david-b@pacbell.net>
On Thursday 23 April 2009 00:29:23 David Brownell wrote:
> On Wednesday 22 April 2009, Bartlomiej Zolnierkiewicz wrote:
> >
> > > By the way ... what about the first patch,
> > > which removed accesses to all those non-existent
> > > registers and bitfields?
> >
> > I didn't see any discussion on it and it looked less urgent / more risky
> > (it is not uncommon for documentation to lack some data) than patch #2.
>
> It's uncommon for TI's documentation to be that far off,
> for that long, though. "Lacking" docs for 50% of the
> registers, for several years ... doesn't make sense.
>
> The current reset handling is clearly broken: the docs
> are quite explicit that the controller doesn't drive the
> reset signal, it's got to be done through a GPIO. The
> board designs match that part of the docs. The code is
> thus contrary to *all* other documentation.
>
> Early DaVinci drivers sometimes exhibited a flagrant
> disregard for chip documentation. This driver is from
> about that era. Maybe it started from prototypes using
> the a different controller design, for example.
>
>
> > Should it also go upstream for 2.6.30?
>
> I can't say either patch would be urgent for 2.6.30,
> but of course it's good that bugfixes merge ASAP.
>
> Since we're only at RC3, I'd be inclined to push both
> up right now. If we were at RC6 or so, I'd hold off
> till the next merge window.
Thanks for the detailed explanation.
I applied the patch to ide-2.6.git/for-linus.
prev parent reply other threads:[~2009-04-23 20:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 1:41 [patch 2.6.30-rc2 2/2] palm_bk3710: UDMA performance fix David Brownell
2009-04-21 10:02 ` Sergei Shtylyov
[not found] ` <49ED99AE.3020100-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2009-04-21 10:28 ` David Brownell
2009-04-22 18:26 ` Bartlomiej Zolnierkiewicz
2009-04-22 20:32 ` David Brownell
[not found] ` <200904222026.11495.bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-04-22 20:43 ` David Brownell
2009-04-22 21:05 ` Bartlomiej Zolnierkiewicz
[not found] ` <200904222305.54820.bzolnier-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-04-22 22:29 ` David Brownell
2009-04-23 20:48 ` Bartlomiej Zolnierkiewicz [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=200904232248.26284.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=david-b@pacbell.net \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.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).