From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751630Ab0AARHb (ORCPT ); Fri, 1 Jan 2010 12:07:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751342Ab0AARHb (ORCPT ); Fri, 1 Jan 2010 12:07:31 -0500 Received: from rhlx01.hs-esslingen.de ([129.143.116.10]:37482 "EHLO rhlx01.hs-esslingen.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751148Ab0AARHa (ORCPT ); Fri, 1 Jan 2010 12:07:30 -0500 Date: Fri, 1 Jan 2010 18:07:29 +0100 From: Andreas Mohr To: "Rafael J. Wysocki" Cc: Jesse Barnes , LKML , Linux PCI , pm list , Stephen Hemminger , "Maciej J. Woloszyk" Subject: Re: [PATCH] PCI / PM: Use per-device D3 delays Message-ID: <20100101170729.GA22252@rhlx01.hs-esslingen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Priority: none User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, While the bug report mentions "So it's just quirky hardware.", the implementation of your patch makes it seem like this delay attribute is totally "norm"al behaviour - I'm missing some more aggressive wording. Perhaps rename d3_delay to d3_delay__quirk or add something to the comment, like "D3->D0 transition time in ms (out-of-spec PCI device quirk)"? Or maybe something like "custom D3->D0 transition time in ms (for quirky hardware violating the PCI spec's <= 100ms)". Thanks for your ongoing great PCI efforts, Andreas Mohr