From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA00BC433E0 for ; Tue, 2 Jun 2020 17:50:40 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 82F5020823 for ; Tue, 2 Jun 2020 17:50:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1591120240; bh=d6pgAEgTTtNx6bhHqA0A4yu/Wbiv7kUU0mDs7Lpv/Ow=; h=Subject:To:Cc:References:From:Date:In-Reply-To:List-ID:From; b=Er/XixVTicOLjxdCXJYjEJJWHtMGkeve97aDaDdY7VciXfBiBotzuH3yN9JDOckWV xdaS7zO5Ep1REpFQFYv8RL6Kx2m7CuEuPKUjegcTDf7Bmo+dJsEkEyC+FGnu1/Fvyl kTXcC1mz/Z1z/zn23tc0wKsZ4LVDA+OJWNLGgTaA= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726162AbgFBRuk (ORCPT ); Tue, 2 Jun 2020 13:50:40 -0400 Received: from mail.kernel.org ([198.145.29.99]:60846 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726037AbgFBRuj (ORCPT ); Tue, 2 Jun 2020 13:50:39 -0400 Received: from [192.168.68.109] (75-58-59-55.lightspeed.rlghnc.sbcglobal.net [75.58.59.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5867F206C3; Tue, 2 Jun 2020 17:50:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1591120239; bh=d6pgAEgTTtNx6bhHqA0A4yu/Wbiv7kUU0mDs7Lpv/Ow=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=WLhZ4BcxBeRYfDYNEiCpOZc/AtdsCfDdwJMKfWFyd++/DYflng9sIUm6VQCz8/2u+ rdukxA6eOvSAxsoWyou39uDFavRSDetcLjcCva8p0bzyOQTb1MMF430+6Cqd027nSb kM8tZS0A4MIhH7NC4a6CylGczoPt37TDPdFLYKAA= Subject: Re: [PATCH] PCI/ASPM: Print correct ASPM status when _OSC failed To: Yicong Yang , "Rafael J. Wysocki" , Bjorn Helgaas Cc: "Rafael J. Wysocki" , Bjorn Helgaas , Linux PCI , ACPI Devel Maling List , Linuxarm References: <1590655125-23949-1-git-send-email-yangyicong@hisilicon.com> <6f6aa87f-7c4d-61f6-f8c2-42ad05b5c845@kernel.org> <1908398.Rfmu1g3mcC@kreacher> <60d31995-1511-4d82-b026-e7119d88a891@hisilicon.com> From: Sinan Kaya Autocrypt: addr=okaya@kernel.org; keydata= mQENBFrnOrUBCADGOL0kF21B6ogpOkuYvz6bUjO7NU99PKhXx1MfK/AzK+SFgxJF7dMluoF6 uT47bU7zb7HqACH6itTgSSiJeSoq86jYoq5s4JOyaj0/18Hf3/YBah7AOuwk6LtV3EftQIhw 9vXqCnBwP/nID6PQ685zl3vH68yzF6FVNwbDagxUz/gMiQh7scHvVCjiqkJ+qu/36JgtTYYw 8lGWRcto6gr0eTF8Wd8f81wspmUHGsFdN/xPsZPKMw6/on9oOj3AidcR3P9EdLY4qQyjvcNC V9cL9b5I/Ud9ghPwW4QkM7uhYqQDyh3SwgEFudc+/RsDuxjVlg9CFnGhS0nPXR89SaQZABEB AAG0HVNpbmFuIEtheWEgPG9rYXlhQGtlcm5lbC5vcmc+iQFOBBMBCAA4FiEEYdOlMSE+a7/c ckrQvGF4I+4LAFcFAlztcAoCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQvGF4I+4L AFfidAf/VKHInxep0Z96iYkIq42432HTZUrxNzG9IWk4HN7c3vTJKv2W+b9pgvBF1SmkyQSy 8SJ3Zd98CO6FOHA1FigFyZahVsme+T0GsS3/OF1kjrtMktoREr8t0rK0yKpCTYVdlkHadxmR Qs5xLzW1RqKlrNigKHI2yhgpMwrpzS+67F1biT41227sqFzW9urEl/jqGJXaB6GV+SRKSHN+ ubWXgE1NkmfAMeyJPKojNT7ReL6eh3BNB/Xh1vQJew+AE50EP7o36UXghoUktnx6cTkge0ZS qgxuhN33cCOU36pWQhPqVSlLTZQJVxuCmlaHbYWvye7bBOhmiuNKhOzb3FcgT7kBDQRa5zq1 AQgAyRq/7JZKOyB8wRx6fHE0nb31P75kCnL3oE+smKW/sOcIQDV3C7mZKLf472MWB1xdr4Tm eXeL/wT0QHapLn5M5wWghC80YvjjdolHnlq9QlYVtvl1ocAC28y43tKJfklhHiwMNDJfdZbw 9lQ2h+7nccFWASNUu9cqZOABLvJcgLnfdDpnSzOye09VVlKr3NHgRyRZa7me/oFJCxrJlKAl 2hllRLt0yV08o7i14+qmvxI2EKLX9zJfJ2rGWLTVe3EJBnCsQPDzAUVYSnTtqELu2AGzvDiM gatRaosnzhvvEK+kCuXuCuZlRWP7pWSHqFFuYq596RRG5hNGLbmVFZrCxQARAQABiQEfBBgB CAAJBQJa5zq1AhsMAAoJELxheCPuCwBX2UYH/2kkMC4mImvoClrmcMsNGijcZHdDlz8NFfCI gSb3NHkarnA7uAg8KJuaHUwBMk3kBhv2BGPLcmAknzBIehbZ284W7u3DT9o1Y5g+LDyx8RIi e7pnMcC+bE2IJExCVf2p3PB1tDBBdLEYJoyFz/XpdDjZ8aVls/pIyrq+mqo5LuuhWfZzPPec 9EiM2eXpJw+Rz+vKjSt1YIhg46YbdZrDM2FGrt9ve3YaM5H0lzJgq/JQPKFdbd5MB0X37Qc+ 2m/A9u9SFnOovA42DgXUyC2cSbIJdPWOK9PnzfXqF3sX9Aol2eLUmQuLpThJtq5EHu6FzJ7Y L+s0nPaNMKwv/Xhhm6Y= Message-ID: Date: Tue, 2 Jun 2020 13:50:37 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <60d31995-1511-4d82-b026-e7119d88a891@hisilicon.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org Bjorn, On 6/1/2020 9:57 PM, Yicong Yang wrote: > well, Sinan's words make sense to me. But I'm still confused that, the message > says we're "disabling ASPM" but ASPM maybe enabled if we designate > pcie_aspm=force as I mentioned in the commit message. Will it be possible if > we replace "disabling" to "disabled" or we can do something else to make > the message reflect the real status of ASPM? What do you think? Sinan