Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Marius Dinu <marius@psihoexpert.ro>
Subject: Re: [PATCH] ata: libata: Fix sata_down_spd_limit() when no link speed is reported
Date: Mon, 30 Jan 2023 20:56:45 +0900	[thread overview]
Message-ID: <798fcc56-b841-ea7c-e169-0387f1f024c3@opensource.wdc.com> (raw)
In-Reply-To: <Y9euXc/Zdr062nJo@x1-carbon>

On 1/30/23 20:47, Niklas Cassel wrote:
> On Mon, Jan 30, 2023 at 08:07:21PM +0900, Damien Le Moal wrote:
>> Commit 2dc0b46b5ea3 ("libata: sata_down_spd_limit should return if
>> driver has not recorded sstatus speed") changed the behavior of
>> sata_down_spd_limit() to return doing nothing if a drive does not report
>> a current link speed, to avoid reducing the link speed to the lowest 1.5
>> Gbps speed.
>>
>> However, the change assumed that a speed was recorded before probing
>> (e.g. before a suspend/resume) and set in link->sata_spd. This causes
>> problems with adapters/drives combination failing to establish a link
>> speed during probe autonegotiation. One exampe reported of this problem
> 
> s/exampe/example/
> 
>> is an mvebu adapter with a 3Gbps port-multiplier box: autonegotiation
>> fails, leaving no recorded link speed and no rep@orted current link
> 
> s/rep@orted/reported/
> 
>> speed. Probe retries also fail as no action is taken by sata_set_spd()
>> after each retry.
>>
>> Fix this by returning early in sata_down_spd_limit() only if we do have
>> a recorded link speed, that is, if link->sata_spd is not 0. With this
>> fix, a failed probe not leading to a recorded link speed is retried at
>> the lower 1.5 Gbps speed, with the link speed potentially increased
>> later on the second revalidate of the device if the device reports
>> that it supports higher link speeds.
>>
>> Reported-by: Marius Dinu <marius@psihoexpert.ro>
>> Fixes: 2dc0b46b5ea3 ("libata: sata_down_spd_limit should return if driver has not recorded sstatus speed")
> 
> IIRC, checkpatch.pl with the default options should put the author on the
> commit being fixed on CC. CC:ing the original author is a good practice IMHO.

Funny that I did run checkpatch and it did not complain about the above typos :)
Thanks for the review, will fix this.


> 
>> Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
>> ---
>>  drivers/ata/libata-core.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>> index 884ae73b11ea..2ea572628b1c 100644
>> --- a/drivers/ata/libata-core.c
>> +++ b/drivers/ata/libata-core.c
>> @@ -3109,7 +3109,7 @@ int sata_down_spd_limit(struct ata_link *link, u32 spd_limit)
>>  	 */
>>  	if (spd > 1)
>>  		mask &= (1 << (spd - 1)) - 1;
>> -	else
>> +	else if (link->sata_spd)
>>  		return -EINVAL;
>>  
>>  	/* were we already at the bottom? */
>> -- 
>> 2.39.1
>>
> 
> With typos fixed:
> Reviewed-by: Niklas Cassel <niklas.cassel@wdc.com>

-- 
Damien Le Moal
Western Digital Research


  reply	other threads:[~2023-01-30 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 11:07 [PATCH] ata: libata: Fix sata_down_spd_limit() when no link speed is reported Damien Le Moal
2023-01-30 11:47 ` Niklas Cassel
2023-01-30 11:56   ` Damien Le Moal [this message]
2023-01-30 12:01     ` Niklas Cassel

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=798fcc56-b841-ea7c-e169-0387f1f024c3@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=Niklas.Cassel@wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=marius@psihoexpert.ro \
    /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