Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp730243pxm; Fri, 25 Feb 2022 18:33:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJzykufySXdAJ0T7nbDDrp2FRDmCHYjHRnu61ke+IdaAslR5KtJD5lyiMOe4eevLwssJ8lJ2 X-Received: by 2002:a65:64d1:0:b0:374:9f3f:d8f5 with SMTP id t17-20020a6564d1000000b003749f3fd8f5mr8503278pgv.186.1645842802974; Fri, 25 Feb 2022 18:33:22 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645842802; cv=none; d=google.com; s=arc-20160816; b=SRx5oeXdO+svQJNZohkIR96yNdLV46v4y5+ou+TcKFW3WhB8B4MCaVN0S1FlR9Onox xUjj0THImHPISxCPO9GD7XVXZqeBz1f+S/TvgJOSOPXfuf5wA1bZjW7jsm9VaofUoRnL xDwVdlBJoQQl/723NfiHlt9muWHW6RomNtpzhNc7w0XP2sbkmMx3/H24WiEV9TIXjIkA VJAGjSH7XRFtcIuZDqYkulpPUmOHnKMyr4V+f8iEi2OVvmPumFVa+/LosjR1MO7xF0Ea 4HqttPRw2f0ieAA5liAgxEMIXRcjkDo3+NuO4DHaya55+gfDNktVe0eIp3pJ/8Z7wBpA kcfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=zI9wn4BtljeUuCguoajUrByeUdLXOXPUY7IPTYywuQ4=; b=yWPJzbOTRPgLqMywdrDmgepB/kcPbZ61TOXhx7/ysUc3Ccwm2i/WWsLR1l8RBs7uY8 ZEzdhwIb7x8qU16X7wOQGZMPA/kG81gkPCUayJQ6FfRJec7MiuJZ7c2nbUDKoBMiji1h MCAqd9B51As4fGDmSh+ct1w3vjBgghK/cun0S4r5SZ0UnvX/y1qMMmvq3VuovO0vXa8U yRZW5RuWu/fLu2/pd1BC9NmYK2+F1rsgbGPokNcrXOeKCjRUootBzFlr55Tnm3jT1NNB MPBEgBsr6qSxtoRr94JGOfKuOGUjSKPPVLwr4Q2LNldohXmTVqQ+dC7nhZ5A3LN13sE9 SObQ== ARC-Authentication-Results: i=1; mx.google.com; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id q16-20020a63f950000000b003745d716f9asi3370637pgk.343.2022.02.25.18.33.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Feb 2022 18:33:22 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 5BE552EFA1E; Fri, 25 Feb 2022 17:59:48 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242909AbiBYQWB (ORCPT + 99 others); Fri, 25 Feb 2022 11:22:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56530 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242901AbiBYQV6 (ORCPT ); Fri, 25 Feb 2022 11:21:58 -0500 Received: from mx1.molgen.mpg.de (mx3.molgen.mpg.de [141.14.17.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C57756F4B6; Fri, 25 Feb 2022 08:21:25 -0800 (PST) Received: from [192.168.0.2] (ip5f5aee37.dynamic.kabel-deutschland.de [95.90.238.55]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id 9C2D261EA1928; Fri, 25 Feb 2022 17:21:22 +0100 (CET) Message-ID: Date: Fri, 25 Feb 2022 17:21:22 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Subject: Re: [PATCH v2 1/3] ata: ahci: Rename board_ahci_mobile Content-Language: en-US To: Hans de Goede , Christoph Hellwig Cc: Mario Limonciello , Damien Le Moal , linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org References: <20220225061113.223920-1-mario.limonciello@amd.com> From: Paul Menzel In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Hans, dear Christoph, Am 25.02.22 um 17:16 schrieb Hans de Goede: > Hi, > > On 2/25/22 17:04, Limonciello, Mario wrote: >> [Public] >> >>> On Fri, Feb 25, 2022 at 12:11:11AM -0600, Mario Limonciello wrote: >>>> This board definition was originally created for mobile devices to >>>> designate default link power managmeent policy to influence runtime >>>> power consumption. >>>> >>>> As this is interesting for more than just mobile designs, rename the >>>> board to `board_ahci_low_power` to make it clear it is about default >>>> policy. >>> >>> Is there any good reason to not just apply the policy to all devices >>> by default? >> >> That sure would make this all cleaner. >> >> I think Hans knows more of the history here than anyone else. I had >> presumed there was some data loss scenarios with some of the older >> chipsets. > > When I first introduced this change there were reports of crashes and > data corruption caused by setting the policy to min_power, these were > tied to some motherboards and/or to some drives. > > This is the whole reason why I only enabled this on a subset of all the > AHCI chipsets. > > At least on devices with a chipset which is currently marked as > mobile, the motherboard specific issues could be fixed with a BIOS > update. But I doubt that similar BIOS fixes have also been rolled > out to all desktop boards (and have been applied by all users), > and I also don't know about older boards. > > So enabling this on all chipsets is definitely not without risks. Exactly, even requiring to update the firmware would go against Linux’ no regression rule. When new chipset are added from now on, we should ask the submitter to test with LPM first though. Mario’s patches look fine to me, and other changes should be done in follow-up patches. All are: Reviewed-by: Paul Menzel Kind regards, Paul