Path: csiph.com!news.mixmin.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod From: Sinan Kaya Newsgroups: linux.kernel Subject: Re: [PATCH V3] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT Date: Mon, 13 Mar 2017 22:10:04 +0100 Message-ID: References: Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1489439208; bh=HADZEgAtqQIViJNdCAzNnOeG23zP+UfNMmyzKnWh+mI=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=ctL9ITUAu/iz8l1/1JqEnw0ffvMv50fxvBB/R8LqlQAE2zd+ekTena2PTGm1/ATNZ 6jvNGWxAI7jlAkMcSVXE1FFNW352SEXjKbHSG+R3//opHQVpBZcGhExpT4v1cltYUQ ym6QQUROoyp2TXSzi1SmwHpe81sYqATjpmbSeM+M= Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1489439208; bh=HADZEgAtqQIViJNdCAzNnOeG23zP+UfNMmyzKnWh+mI=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=ctL9ITUAu/iz8l1/1JqEnw0ffvMv50fxvBB/R8LqlQAE2zd+ekTena2PTGm1/ATNZ 6jvNGWxAI7jlAkMcSVXE1FFNW352SEXjKbHSG+R3//opHQVpBZcGhExpT4v1cltYUQ ym6QQUROoyp2TXSzi1SmwHpe81sYqATjpmbSeM+M= Dmarc-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org CD8E360132 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=okaya@codeaurora.org User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: robomod@news.nic.it List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Approved: robomod@news.nic.it Lines: 36 Organization: linux.* mail to news gateway X-Original-Cc: linux-pci@vger.kernel.org, timur@codeaurora.org, linux-arm-msm@vger.kernel.org, Mayurkumar Patel , open list , linux-arm-kernel@lists.infradead.org X-Original-Date: Mon, 13 Mar 2017 17:06:46 -0400 X-Original-Message-ID: <48b14a37-3b5c-e128-aa96-b924d05b7636@codeaurora.org> X-Original-References: <1489005551-23598-1-git-send-email-okaya@codeaurora.org> <20170309222751.GD19517@bhelgaas-glaptop.roam.corp.google.com> X-Original-Sender: linux-kernel-owner@vger.kernel.org Xref: csiph.com linux.kernel:1599828 Hi Bjorn, On 3/9/2017 5:27 PM, Bjorn Helgaas wrote: > This is an aspect of the ASPM design that I don't like: > > - pcie_aspm_init_link_state() is called on a *bridge* after we've > enumerated any devices below the bridge, and we allocate the > link_state. > > - pcie_aspm_exit_link_state() is called on an *endpoint*, and if > we're removing the last endpoint below a bridge, we release the > *parent's* link_state. I just posted V4 a minute ago. I divided ASPM init into two so that the ASPM registers are captured in device_add path. There is a section of the ASPM init code that needs to walk all the devices under the bridge. This section of the code is not working in device_add path as the link list for child devices has not been set up yet. Unless you tell me there is a better way to handle this, I don't see how we can remove the call from scan_slot. After further review, I think I can split PATCH V4 3/3 into two. Before diving into too much clean up, I wanted to get some feedback as it is obvious from the messed up cover letter. Sinan -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.