From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hannes Reinecke Subject: Re: [PATCH 6/8] pm80xx: Add PORT RECOVERY TIMEOUT support Date: Wed, 29 Jul 2015 10:57:55 +0200 Message-ID: <55B89593.6010407@suse.de> References: <1438151240-4097-1-git-send-email-Viswas.G@pmcs.com> <1438151240-4097-7-git-send-email-Viswas.G@pmcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mx2.suse.de ([195.135.220.15]:59943 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751206AbbG2I55 (ORCPT ); Wed, 29 Jul 2015 04:57:57 -0400 In-Reply-To: <1438151240-4097-7-git-send-email-Viswas.G@pmcs.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Viswas.G@pmcs.com, linux-scsi@vger.kernel.org Cc: xjtuwjp@gmail.com, JBottomley@parallels.com, Tomas Henzl , Suresh.Thiagarajan@pmcs.com On 07/29/2015 08:27 AM, Viswas.G@pmcs.com wrote: > From: Viswas G >=20 > PORT RECOVERY TIMEOUT is the maximum time between the controller's > detection of the PHY down until the receipt of the ID_Frame (from the > same remote SAS port). If the time expires before the ID_FRAME is > received, the port is considered INVALID and can be removed. The > IOP_EVENT_PORT_RECOVERY_TIMER_TMO event is reported following the > IOP_EVENT_ PHY_DOWN event when the PHY/port does not recover after > Port Recovery Time. >=20 > Signed-off-by: Viswas G > Signed-off-by: Suresh Thiagarajan =20 > --- Ah. Here is the link down handling. Maybe you should indicate this in the previous patch. Reviewed-by: Hannes Reinecke Cheers, Hannes --=20 Dr. Hannes Reinecke zSeries & Storage hare@suse.de +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N=FCrnberg GF: F. Imend=F6rffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG N=FCrnberg) -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html