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 3FB48C61DC4 for ; Thu, 27 Aug 2026 16:16:45 +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:References: 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: List-Owner; bh=oJmyafS11iNFx8Z8svwQL6OKMBoxu9rnsQLj6nSMoo0=; b=g7tSfP+0zIEbI+ qsDVqHNX0Ksk7R9sukafm/HvsU9BLYz9dcYZg2C7aM4MuaxG/ib5x14AON9FtH26FNRa+0pQGc943 jNoZMBVWCVNcTrIvBlEG0dDVzK4v8D69/37cOkyKtYTlruQFLN/1viUgWTIsePYPgQxJTtnadHXus jAneOaS+PIZ3GyoybCGSpthAJ3jbLXHpd8jKFyarbwLjQ1DKA5KLSq3UXQRIyIGdNSwO6riMitfp0 AEEEvVbnGMR+oAiw+qePkJnhmN4lbNPAU6oe7hseMAoCRv78lQwJ9ah/t3EqF17ppUhKd/XDIqp1p 1vRO0ic9j8LGfN1PEyPA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wzcmS-00000004IxE-3jBT; Thu, 27 Aug 2026 16:16:44 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wzcmQ-00000004Iwb-3xhP; Thu, 27 Aug 2026 16:16:42 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id 4922E407EC; Thu, 27 Aug 2026 16:16:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 588A41F000E9; Thu, 27 Aug 2026 16:16:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1787847402; bh=ICFnTYRS7s0OrNF+UlxpgEZVwggu1x23aonWDAOIy30=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=oZLTvTKVh0ryslM2uHLc5UUJ+i+wFQHdBHG3enmsirsX00mIRPMPcG1HcmmJDPfh6 324w7+u0jLRPTBsZO7OApM+CRZKOGJjZPRQsCKh3O/tC18cc0FNnL/az59Kd2DjebX pXriDpMt885numb9rjthDKIamxtaooUxAKhMqYqNKmtuB8ZblUcPiQIi6baG0USE+L QfCk/FnayvhDokIe3Nfj1z67okVoY5xfnoy1fSfDAmTcgmBIK2mOaThNEPZkjUvV5j JoOQQTfGzQu/+JHIr1ji8pGyesamRN5K1Ny2F5l1tsWTpDJZBkL6oImlDF90iIgKAm J2G+KVt1xgzpQ== Date: Thu, 27 Aug 2026 21:46:38 +0530 From: Vinod Koul To: Sebastian Reichel Cc: Manivannan Sadhasivam , Neil Armstrong , Heiko Stuebner , Frank Wang , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Thinh Nguyen , Greg Kroah-Hartman , Philipp Zabel , Andy Yan , Dmitry Baryshkov , Yubing Zhang , Alexey Charkov , Igor Paunovic , linux-phy@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, kernel@collabora.com, devicetree@vger.kernel.org, linux-usb@vger.kernel.org Subject: Re: [PATCH v14 28/38] phy: core: add notifier infrastructure Message-ID: References: <20260813-rockchip-usbdp-cleanup-v14-0-b5ad9c68fa11@collabora.com> <20260813-rockchip-usbdp-cleanup-v14-28-b5ad9c68fa11@collabora.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20260813-rockchip-usbdp-cleanup-v14-28-b5ad9c68fa11@collabora.com> X-BeenThere: linux-phy@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux Phy Mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-phy" Errors-To: linux-phy-bounces+linux-phy=archiver.kernel.org@lists.infradead.org On 13-08-26, 22:52, Sebastian Reichel wrote: > Some PHY devices with multiple ports (e.g. USB3 and DP) require a reset > if the configuration changes or cable orientation changes. This is a > problem, as the consumer device will run into undefined behavior. > > With the new PHY notifier API introduced in this patch, the consumer > driver can hook into reset events coming from a PHY device to handle the > PHY going down gracefully. Hmmm how will phy get notified for these events. Typically there is a separate hotplug mechanism to take care of cable changes. Looking at implementation of this, It seems to me there is checked on power-on, so maybe notifier maynot be right one... ? -- ~Vinod -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy