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 92231C4332F for ; Thu, 9 Nov 2023 22:32:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:References: List-Owner; bh=7ZLPwhwyqK/u1dq56m5CkNM7ManuE3ybXNsXbS2QrSE=; b=n0Nav9SHBV7U1G YEhyxqMLQ0OiYCnDxAuEFWQncW7zb9SwKzPwMSqBEUR0fuQwWSK+26ucp7ztkCBcuTjqF4gzDvExZ YcIwfX0EIjhyItJ/hMoEVgFOP/WNJyJrlsvJfrt5/soWrw3dPqKPIztE43u2SScpRKuILVP64HVu5 B8W6TDVtuDb7iYDB1Gh5U68HIKbjKY+D/caAbQ6t50WfrJ0dvYDneX20mh6AndYKN05QPxbX96K6T hBrVSP9wdjKuWZQ5Gc7QCSkKf9KJG+4EQ8YX8f/VhkrxFp0ob9yziHddL3J7McW7EVJOAbdmLDhQu OmUZrSbKVqBxyVHgU3nw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1r1DZ1-007M0r-2E; Thu, 09 Nov 2023 22:31:51 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1r1DYy-007Lzw-0C; Thu, 09 Nov 2023 22:31:49 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 0E7FACE12A6; Thu, 9 Nov 2023 22:31:44 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 16E5DC433C7; Thu, 9 Nov 2023 22:31:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1699569103; bh=eQIy8OzgMGafbmuvUdri4QU/WFfrf6FPeSAilMINH0w=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=q8glFZzn6SgDHtlfhq4O6xZ0G/5GX0BOJrQpDVDffzybJ4BrRMTKYRlIJsMj5xwjT CvRd9e3A1krvDsPehYjyPzdoMlNcNaOvmHJrDn3zeV2vSqcRjlBw46e4uHr9G27k50 0Wy8oWhT3vJ36hdmPRGhX8hDqP6Ez/vWN4x4AApNY5EpVbkY1XFRzeCwZcgQn67h42 pMd+egpzqoAiIIq3Xn9qtCmG4Jj9kg+PqxzeN8jVgqj5mZS/QxFD7SRp2MvQHJ9Dzk /YqFRx9R5hstLYKjdc8rH6ItctwdvVWY6jaJBPDYy55IpPR4C/GiENrQ9OLW+lZ6sC 3TsCS4An9a0YQ== Date: Thu, 9 Nov 2023 16:31:40 -0600 From: Bjorn Helgaas To: Jim Quinlan Cc: linux-pci@vger.kernel.org, Nicolas Saenz Julienne , Bjorn Helgaas , Lorenzo Pieralisi , Cyril Brulebois , Phil Elwell , bcm-kernel-feedback-list@broadcom.com, Jim Quinlan , Florian Fainelli , Lorenzo Pieralisi , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Rob Herring , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , open list Subject: Re: [PATCH v7 2/3] PCI: brcmstb: Configure HW CLKREQ# mode appropriate for downstream device Message-ID: <20231109223140.GA494906@bhelgaas> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231109_143148_281849_B0342993 X-CRM114-Status: GOOD ( 17.18 ) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Nov 09, 2023 at 05:06:15PM -0500, Jim Quinlan wrote: > ... > BTW, besides the RPi4, I haven't been able to find a Linux platform > where I can do > > echo $POLICY > /sys/module/pcie_aspm/parameters/policy This sounds like something we should fix. What exactly happens? I think this should be handled at pcie_aspm_set_policy(), so: /sys/module/pcie_aspm/parameters/policy doesn't exist (seems unlikely)? Returns -EPERM (would indicate aspm_disabled)? Returns -EINVAL (would indicate $POLICY doesn't match anything in policy_str[])? Returns 0 with no action (would indicate $POLICY is the same as the current aspm_policy)? > It seems that the FW/ACPI typically locks this down. I did see a > comment somewhere that > said that the reason it was locked down is because too many devices > cannot handle it. Do you have any details about FW/ACPI locking this down? aspm_disabled is set by the kernel "pcie_aspm=off" parameter (I assume you're not referring to this), if the FADT has ACPI_FADT_NO_ASPM set, or if a host bridge's _OSC is missing or failed (maybe [1] is the comment you saw?) These all *should* be unusual cases, so I'd be surprised if you're tripping over one of these. I would NOT be surprised if we had some issue in pcie_config_aspm_link() or pcie_set_clkpm() that meant the policy change didn't work as intended, though. Bjorn [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/acpi/pci_root.c?id=v6.6#n617 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel