Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
	"Anders Roxell" <anders.roxell@linaro.org>,
	"Naresh Kamboju" <naresh.kamboju@linaro.org>,
	Sergey.Semin@baikalelectronics.ru
Cc: "open list" <linux-kernel@vger.kernel.org>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	regressions@lists.linux.dev,
	"open list:LIBATA SUBSYSTEM (Serial and Parallel ATA drivers)" 
	<linux-ide@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
	"Niklas Cassel" <niklas.cassel@wdc.com>
Subject: Re: TI: X15 the connected SSD is not detected on Linux next 20221006 tag
Date: Fri, 14 Oct 2022 09:31:55 +0200	[thread overview]
Message-ID: <7ee4a1bd-0674-42d8-8980-8b029ca09e71@app.fastmail.com> (raw)
In-Reply-To: <ca8d3fff-0365-24d9-fd53-5799ac34f336@opensource.wdc.com>

On Fri, Oct 14, 2022, at 2:22 AM, Damien Le Moal wrote:
> On 10/14/22 07:07, Anders Roxell wrote:
> [...]
>>> 8)
>>>> If reverting these patches restores the eSATA port on this board, then you need
>>>> to fix the defconfig for that board.
>>>
>>> OTOH,
>>> Anders, enabled the new config CONFIG_AHCI_DWC=y  and tried but the
>>> device failed to boot.
>> 
>> I thought it would work with enabling CONFIG_AHCI_DWC=y, but it didn't...
>
> As mentioned in my previous reply to Naresh, this is a new driver added in
> 6.1. Your board was working before so this should not be the driver needed
> for it.
>
>> However, reverting patch 33629d35090f ("ata: ahci: Add DWC AHCI SATA
>> controller support")
>> from next-20221013 was a success, kernel booted  and the 'mkfs.ext4' cmd was
>> successful.
>
> Which is very strange... There is only one hunk in that commit that could
> be considered suspicious:
>
> diff --git a/drivers/ata/ahci_platform.c b/drivers/ata/ahci_platform.c
> index 9b56490ecbc3..8f5572a9f8f1 100644
> --- a/drivers/ata/ahci_platform.c
> +++ b/drivers/ata/ahci_platform.c
> @@ -80,9 +80,7 @@ static SIMPLE_DEV_PM_OPS(ahci_pm_ops, ahci_platform_suspend,
>  static const struct of_device_id ahci_of_match[] = {
>         { .compatible = "generic-ahci", },
>         /* Keep the following compatibles for device tree compatibility */
> -       { .compatible = "snps,spear-ahci", },
>         { .compatible = "ibm,476gtr-ahci", },
> -       { .compatible = "snps,dwc-ahci", },
>         { .compatible = "hisilicon,hisi-ahci", },
>         { .compatible = "cavium,octeon-7130-ahci", },
>         { /* sentinel */ }
>
> Is your board using one of these compatible string ?

The x15 uses "snps,dwc-ahci". I would expect it to detect the device
with the new driver if that is loaded, but it's possible that the
driver does not work on all versions of the dwc-ahci hardware.

Anders, can you provide the boot log from a boot with the new driver
built in? There should be some messages from dwc-ahci about finding
the device, but then not ultimately working.

Depending on which way it goes wrong, the safest fallback for 6.1 is
probably to move the "snps,spear-ahci" and "snps,dwc-ahci" compatible
strings back into the old driver, and leave the new one only for 
the "baikal,bt1-ahci" implementation of it, until it has been
successfully verified on TI am5/dra7, spear13xx and exynos.

     Arnd

  reply	other threads:[~2022-10-14  7:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12  7:24 TI: X15 the connected SSD is not detected on Linux next 20221006 tag Naresh Kamboju
2022-10-13  7:11 ` Damien Le Moal
2022-10-13 12:39   ` Naresh Kamboju
2022-10-13 22:07     ` Anders Roxell
2022-10-14  0:22       ` Damien Le Moal
2022-10-14  7:31         ` Arnd Bergmann [this message]
2022-10-14  7:53           ` Damien Le Moal
2022-10-14  9:22             ` Anders Roxell
2022-10-14  9:37               ` Arnd Bergmann
2022-10-14  9:47                 ` Damien Le Moal
2022-10-14 14:06               ` Serge Semin
2022-10-17  7:43                 ` Anders Roxell
2022-10-17 15:52                   ` Serge Semin
2022-11-30  9:40                     ` Naresh Kamboju
2022-11-30 10:03                       ` Niklas Cassel
2022-12-01 11:48                         ` Anders Roxell
2022-12-05  1:11                           ` Serge Semin
2022-12-05 10:08                             ` Arnd Bergmann
2022-12-05 13:24                               ` Damien Le Moal
2022-12-06  8:46                                 ` Serge Semin
2022-12-06  9:12                                   ` Damien Le Moal
2022-12-06 21:04                                     ` Serge Semin
2022-12-01 13:02                       ` TI: X15 the connected SSD is not detected on Linux next 20221006 tag #forregzbot Thorsten Leemhuis
2022-12-07  5:40                         ` Thorsten Leemhuis
2022-10-14 13:38           ` TI: X15 the connected SSD is not detected on Linux next 20221006 tag Serge Semin
2022-10-14 13:36         ` Serge Semin
2022-10-14  0:17     ` Damien Le Moal

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=7ee4a1bd-0674-42d8-8980-8b029ca09e71@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=Sergey.Semin@baikalelectronics.ru \
    --cc=anders.roxell@linaro.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=niklas.cassel@wdc.com \
    --cc=regressions@lists.linux.dev \
    /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