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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id F0F06CCD193 for ; Sat, 18 Oct 2025 05:07:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:Message-ID:References:In-Reply-To:Subject:CC:To: From:Date:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=CtsC/atolH54CouemLXs+ZgGBejOAx0p6Dbv/PgCFF0=; b=FBSvBsESw8/KmHuvNPCQRaGj7l 3RWRv6ViZbr/7D2zDM7rdlAPfdSgXxjI7ZNomgB3PsFkG0Ixd6e/HnBrh6WZglHaJhCfRBd0U78rz omF0S5gUoyx/WjEvl7CKusH3VzGUldK8gotGmMVoBLrMUR0i7nkfaQFcGdgeIhb8ypHGaVDDBu0d7 y3H/+pyArKbyA+UKA2OZvLomMW1XL/pX5fkO9BHsho3r3Yw7KaK2OGR4CTTTHMAgftA8BgP85V60i axJJaITg3vMj7nlaysWYkPAkUV0cKmL8g/7vPnL0bu9xfSRdGh3REfLKNKyWnxSwYj5aNrJwrazWh 6zVcL9Rw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1v9zAM-00000009Xz9-0Dpx; Sat, 18 Oct 2025 05:07:42 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1v9zAL-00000009Xyw-0Axk; Sat, 18 Oct 2025 05:07:41 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by tor.source.kernel.org (Postfix) with ESMTP id DBDDE605E5; Sat, 18 Oct 2025 05:07:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 591CFC4CEF8; Sat, 18 Oct 2025 05:07:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1760764059; bh=7HQHgRhKu2K+O3M8/DReLJ1cTm/7JJq+iftVZzfodks=; h=Date:From:To:CC:Subject:In-Reply-To:References:From; b=jcEHkju89gP9MlVd3XBTlA+BScjCk+KCEnMgkB4zIPwOOC0l/A5XDJPg5jj/NflSA Z7ysfdXwfMUqMTe5iGk+EQWG7ZtpW4kvZNGnOARN+E7motMWAkmFFkMPhEqPCtwmra 1tk+HuLpFxzT4CzhyKXN8Dy5TWW/tkz40UmdVW8ZARYMhjVLnBySZw+vaY0R2G+zjC TUPKDLDxcJINO6nvFyaTLMKTo/GjKXoGiNwQ9LhAM0eukm9VX8f3GMkYldjruOPyse 6rgf4ZX7k8VksAgHMcXyCBhEywUPHV3Rjl9q83Q46IcDI5Tp6OsgE4+c881I3IYC5C X89baa+iOWsAw== Date: Sat, 18 Oct 2025 07:07:35 +0200 From: Niklas Cassel To: Bjorn Helgaas CC: Lorenzo Pieralisi , =?UTF-8?Q?Krzysztof_Wilczy=C5=84ski?= , Manivannan Sadhasivam , Rob Herring , Bjorn Helgaas , Heiko Stuebner , Shawn Lin , Kever Yang , Simon Xue , Damien Le Moal , Dragan Simic , FUKAUMI Naoki , Diederik de Haas , stable@vger.kernel.org, Manivannan Sadhasivam , linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org Subject: =?US-ASCII?Q?Re=3A_=5BPATCH_v3=5D_PCI=3A_dw-rockchip=3A_Pre?= =?US-ASCII?Q?vent_advertising_L1_Substates_support?= User-Agent: Thunderbird for Android In-Reply-To: <20251017164558.GA1034609@bhelgaas> References: <20251017164558.GA1034609@bhelgaas> Message-ID: <54FD6159-AE45-432B-8F0E-4654721D16A6@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 17 October 2025 18:45:58 CEST, Bjorn Helgaas wrot= e: (snip) >>=20 >> Thus, prevent advertising L1 Substates support until proper driver supp= ort >> is added=2E > >I think Mani is planning a change so we don't try to enable L1 >Substates by default, which should avoid the regression even without a >patch like this=2E Sounds good, I suggested the same: https://lore=2Ekernel=2Eorg/linux-pci/aO9tWjgHnkATroNa@ryzen/ > >That will still leave the existing CONFIG_PCIEASPM_POWER_SUPERSAVE=3Dy >and sysfs l1_1_aspm problems=2E Indeed, which is why I think that this patch is v6=2E18 material=2E > >And we'll need to figure out a way to allow L1=2Ex to be enabled based >on 'supports-clkreq' and possibly other info=2E That would likely be >v6=2E19 material since it's new functionality=2E I agree=2E Kind regards, Niklas