public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ruslan Valiyev <linuxoid@gmail.com>
To: cassel@kernel.org
Cc: dlemoal@kernel.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, Ruslan Valiyev <linuxoid@gmail.com>
Subject: Re: [PATCH] ata: ahci: Add AMD 600 Series Chipset SATA Controller (0x43f6)
Date: Tue, 10 Mar 2026 18:29:09 +0000	[thread overview]
Message-ID: <20260310182700.reply-val13@gmail.com> (raw)
In-Reply-To: <abBUdlxKa4DpVsPI@ryzen>

On Tue, Mar 10, 2026 at 05:27:PM +0000, Niklas Cassel wrote:
> If the ahci driver fails to bind, that means that the class code for
> this AMD AHCI controller is not PCI_CLASS_STORAGE_RAID and is not
> PCI_CLASS_STORAGE_SATA_AHCI. I am honestly curious... what is the PCI
> class code of this controller then? :)

That is exactly the right question, and I should have asked it before
sending this patch.

I based this on a bugzilla report where the user confirmed the new_id
workaround works, but I did not ask for lspci -nnvs output first. I
do not have the class code from the affected system, which means I cannot
justify the patch as-is.

I will go back to the reporter and get the full lspci output. If the
prog-if differs from yours (e.g. 0x00 instead of 0x01), I will resubmit
with proper justification. If not, I will drop it.

Sorry for the noise.

Ruslan

      reply	other threads:[~2026-03-10 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 15:49 [PATCH] ata: ahci: Add AMD 600 Series Chipset SATA Controller (0x43f6) Ruslan Valiyev
2026-03-10 17:27 ` Niklas Cassel
2026-03-10 18:29   ` Ruslan Valiyev [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=20260310182700.reply-val13@gmail.com \
    --to=linuxoid@gmail.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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