From: Tejun Heo <htejun@gmail.com>
To: "Huang, Shane" <Shane.Huang@amd.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Withdraw IGN_SERR_INTERNAL for SB800 SATA
Date: Wed, 19 Nov 2008 11:48:51 +0900 [thread overview]
Message-ID: <49237E93.2060303@gmail.com> (raw)
In-Reply-To: <C8E4BD7D001E44499280E0884BD9DB300EA1A9@sshaexmb1.amd.com>
Huang, Shane wrote:
> Hi Tejun,
>
>
>> -----Original Message-----
>> From: Tejun Heo [mailto:htejun@gmail.com]
>>>
>>> + /* SB800 does NOT need the workaround to ignore SERR_INTERNAL */
>>> + if (board_id == board_ahci_sb700 && pdev->revision >= 0x40)
>>> + hpriv->flags &= ~AHCI_HFLAG_IGN_SERR_INTERNAL;
>>> +
>>> if ((hpriv->flags & AHCI_HFLAG_NO_MSI) || pci_enable_msi(pdev))
>>> pci_intx(pdev, 1);
>> Great, but please use separate board_ahci_* entry. ie.
>> board_ahci_sb700_ign_serr for the ones with the problem and
>> board_ahci_sb700 for other sb700s and sb800s.
>
> Thanks for your suggestion.
>
> Different SATA controller revisions with/without the problem have SAME
> PCI device ID,
> so it's difficult to distinguish them with board_ahci_sb700_ign_serr and
> board_ahci_sb700 at the beginning.
>
> Although we can distinguish them in ahci_init_one() and reevaluate
> board_id
> as well as ent->driver_data, I still suggest we keep my submitted patch
> because it seems to be neater. :-)
>
> And I also added some comments for better maintainance like
> /* board_ahci_sb700, for SB700 and SB800 */
> /* SB800 does NOT need the workaround to ignore SERR_INTERNAL */
> It should be much clear to us now...
Ah.. right, can't match revision. Yeap, then,
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2008-11-19 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 9:27 [PATCH] Withdraw IGN_SERR_INTERNAL for SB800 SATA Shane Huang
2008-11-18 16:09 ` Tejun Heo
2008-11-19 2:41 ` Huang, Shane
2008-11-19 2:48 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-30 2:53 Shane Huang
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=49237E93.2060303@gmail.com \
--to=htejun@gmail.com \
--cc=Shane.Huang@amd.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.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).