linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Sylver Bruneau <sylver.bruneau@googlemail.com>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: sata_mv errata function
Date: Mon, 21 Apr 2008 09:35:03 -0400	[thread overview]
Message-ID: <480C9807.3070404@rtr.ca> (raw)
In-Reply-To: <3908ea640804210542s4e1e8403tfec4a99816b5d148@mail.gmail.com>

Sylver Bruneau wrote:
> Hello,
> during my analysis of some recent patches [1] from Marvell for several
> ARM based (88f5182 & 88f5281) NAS devices, i've found that some
> errata stuff are a little bit different from what is done in sata_mv.c
>  mainline code.
> 
> I don't know if there is a reason for the code not to be the same, but
> I think that it could be useful to bring that to you.
> 
> Here are the facts ...
> First, the fix value for phyMode 3 is a little bit different :
>  while sata_mv.c is applying a
>         tmp &= ~0x7F800000;
> the patch from Marvell (check _fixPhyParams function in
> arch/arm/mach-feroceon/Board
> /SATA/CoreDriver/mvSata.c file) is applying a
>         regVal &= ~0x7F900000;
> 
> The fix value for phyMode 4 is also different for GEN IIE (6042 &
> 7042) devices :
> in Marvell patch, there is an additional fix for this case (where nothing
> seems to be done for this in sata_mv.c) :
>         /* phy mode 4 register of Gen IIE devices has some restriction */
>          if (pAdapter->sataAdapterGeneration >= MV_SATA_GEN_IIE)
>         {
>             phyMode4Value &= ~0x5DE3FFFC;
>             phyMode4Value |= MV_BIT2;
>         }
> 
> I understand that what is done in this function is not well documented,
>  but as it's what is done by Marvell in their patches, do you think that it
> should be merged in sata_mv.c ?
> 
> If so, I will post a proper patch to add this !
..

Thanks, Sylver.

I am currently working on sata_mv on behalf of Marvell,
and a full errata overhaul is in the works for the next
2-3 weeks here.  So those bits will get fixed by me as
part of this effort.

But I will keep your description above in my inbox as a reminder
to double-check those specific items, just in case it differs from
the detailed errata information Marvell has provided to me (under NDA).

Thanks again.

Mark

      parent reply	other threads:[~2008-04-21 13:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 12:42 sata_mv errata function Sylver Bruneau
2008-04-21 13:20 ` Morrison, Tom
2008-04-21 13:41   ` Mark Lord
2008-04-21 13:51     ` Morrison, Tom
2008-05-07 16:02       ` Grant Grundler
2008-04-21 13:35 ` Mark Lord [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=480C9807.3070404@rtr.ca \
    --to=liml@rtr.ca \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=sylver.bruneau@googlemail.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).