From: Christoph Hellwig <hch@infradead.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] ahci: Add Intel Emmitsburg PCH RAID PCI IDs
Date: Mon, 23 Nov 2020 10:09:17 +0000 [thread overview]
Message-ID: <20201123100917.GA26718@infradead.org> (raw)
In-Reply-To: <20201120105309.GR2495@lahna.fi.intel.com>
On Fri, Nov 20, 2020 at 12:53:09PM +0200, Mika Westerberg wrote:
> On Thu, Nov 19, 2020 at 04:50:22PM +0000, Christoph Hellwig wrote:
> > On Thu, Nov 19, 2020 at 01:43:18PM +0300, Mika Westerberg wrote:
> > > Add Intel Emmitsburg PCH RAID PCI IDs to the list of supported
> > > controllers.
> >
> > Stupid question: what would it to get Intel to finally report the
> > correct classcode after all the time? The amount of IDs we need to list
> > is getting ridiculous.
>
> What is the correct class code in this case that it works with the AHCI
> driver?
>
> I think (not 100% sure) it reports standard AHCI class code when it is
> not in RAID mode but these PCI IDs are for the RAID mode.
The right class code is the AHCI one. The so called RAID mode doesn't
change the operation of the device at all (except for sometimes hiding
NVMe devices that are a different PCIe function to start with).
next prev parent reply other threads:[~2020-11-23 10:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 10:43 [PATCH] ahci: Add Intel Emmitsburg PCH RAID PCI IDs Mika Westerberg
2020-11-19 16:50 ` Christoph Hellwig
2020-11-20 10:53 ` Mika Westerberg
2020-11-23 10:09 ` Christoph Hellwig [this message]
2020-11-23 11:26 ` Mika Westerberg
2020-11-23 11:38 ` Christoph Hellwig
2020-11-23 12:28 ` Mika Westerberg
2020-11-23 12:51 ` Christoph Hellwig
2020-11-25 14:44 ` Mika Westerberg
2022-04-02 0:43 ` Williams, Dan J
2020-12-16 12:34 ` Mika Westerberg
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=20201123100917.GA26718@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-ide@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.