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 119B6CA5FE3 for ; Sat, 3 Oct 2026 09:04:23 +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=exKliyTuEkxk91Ff20nmzl/d1bmscdTYUsYluoyCd+Q=; b=tJI5nmhucKdXGG 2PPCE5OqHw83/+QoIfjQP/+pxfwqTKRCXhLuzFNkUF3VrT07qfq/yReDuEcuyqgWFUyyAbZRZ6GZ9 wWsHsuSnAsDdyKZb2t7t0TbH5o8n6xs19znB+T4nKLvzLUfakNsv4AA2HX3JqqTpdKnfnCaCIqfac 5UaqVm4ojMEYoykYqWeQ99OBvEeZr8IMj1uQ1Vp4t7yDUo9zda4SaZoM51j+NxEIXskV322BEMqtd Z+KJISwWUJfK7KzkGcMMTf+qC/ffOrhNgMQwMi6Fvj3v3ULPf+yISM8hr3QvOiyoURKAqK7XecopE FyIN+el6sJKXtN7pFfLQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xCvfG-0000000DEWU-3oRM; Sat, 03 Oct 2026 09:04:18 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xCvfF-0000000DEVt-3m7J; Sat, 03 Oct 2026 09:04:17 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 56CAA60534; Sat, 3 Oct 2026 09:04:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 432F81F0089C; Sat, 3 Oct 2026 09:04:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791018257; bh=r7Cqps3I7ChVDkfGpYIwv5W5QyZBtV/wchFikLgUd30=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ifsv1HpTllRjuu7fRpQtXxhQXDdrFcHAzARMmhx+d0R+gZ6eAYie2pV4O1aXnLYOY vcZGUlC2cwlJOCpajrRIorSilCW1DUSoHoNzVh4IjzXfttEYPC1lcrmHYlmHNCEfmN sB4ziC3sjmt/onjTlQUba1XPFTYQpeX/65W3ivSDa9DWoNETMRLMf7ksu0Ii1TFhOr YiBszfZok4J5UWgbDyHqJhYfpcw3dcPFjIzGSa2tPD6UNa1RG1T8ON4zenRDVfscgH qXc44TtRs8L5/6mxVvELB0rVqEE2ltB5etHgXfPHBKvszaQU2GF7oPWaCe2hEFPvwX 5jQl56+Y07PTg== Date: Sat, 3 Oct 2026 11:04:13 +0200 From: Vinod Koul To: Sebastian Reichel Cc: Thinh Nguyen , Greg Kroah-Hartman , Heiko Stuebner , Neil Armstrong , Manivannan Sadhasivam , Igor Paunovic , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-phy@lists.infradead.org, kernel@collabora.com Subject: Re: [PATCH v16 1/6] phy: core: add notifier infrastructure Message-ID: References: <20260924-b4-rockchip-dwc3-rockchip-glue-v16-0-126a2e9133c3@collabora.com> <20260924-b4-rockchip-dwc3-rockchip-glue-v16-1-126a2e9133c3@collabora.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20260924-b4-rockchip-dwc3-rockchip-glue-v16-1-126a2e9133c3@collabora.com> X-BeenThere: linux-rockchip@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Upstream kernel work for Rockchip platforms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+linux-rockchip=archiver.kernel.org@lists.infradead.org Hello Sebastian, On 24-09-26, 19:25, 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. > > Note that this uses -ENOSYS instead of the more sensible -ENOTSUP for > the stub functions when GENERIC_PHY is disabled to stay consistent with > the existing ones. I dont think this series has the usage of this. I think I am still not convinced why a phy should notify as I dont feel we have any mechanism to notifying. Checking status and letting people know if not really a notification mechanism... Maybe add a status call instead? -- ~Vinod _______________________________________________ Linux-rockchip mailing list Linux-rockchip@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-rockchip