From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755331AbbDUPba (ORCPT ); Tue, 21 Apr 2015 11:31:30 -0400 Received: from mail-qk0-f169.google.com ([209.85.220.169]:36423 "EHLO mail-qk0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751322AbbDUPb0 (ORCPT ); Tue, 21 Apr 2015 11:31:26 -0400 Date: Tue, 21 Apr 2015 11:31:21 -0400 From: Tejun Heo To: Gabriele Mazzotta Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org, stripathi@apm.com Subject: Re: SATA link power management issues Message-ID: <20150421153121.GD9455@htj.duckdns.org> References: <3352987.ugV1Ipy7Z5@xps13> <2526428.uJaEqCTeIa@xps13> <9895435.0ZSsstcbFA@xps13> <2356903.cA2H5W8V2D@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2356903.cA2H5W8V2D@xps13> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 20, 2015 at 10:02:12PM +0200, Gabriele Mazzotta wrote: > On Sunday 22 February 2015 21:53:35 Gabriele Mazzotta wrote: > > It seems that the following patch prevents errors when the policy is > > changed. Could anybody explain why? The device is generating a spurious PHY event after LPM state change and the patch is ignoring the event once after state change. It's a bit too specific. Maybe we should do this timeout-based - e.g. ignore phy events for 1s after LPM state change. Gabriele, would be interested in making such changes? Thanks. -- tejun