From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B1F4247A0C8 for ; Wed, 21 Jan 2026 08:52:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768985537; cv=none; b=EGBoUTmegCXOcfpn6iRyPrr/0+4bCdkLBk6C05W5hf7phGT2xJD6QdgoTVNOnAXOWn2IynN7zXHiMvSYCq6c1mOeBdsEQsao+BhFYcOrvEauoC1PCEdyt8vrkAtuSmsa/X5+oEnmq8JlIiYk9pOJjY8Yp32cXGZOgwJU/8EB6BE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768985537; c=relaxed/simple; bh=ejSWbgcSgj468U7DhaSQJWhfKNnh2RPnryiHSVZbLx0=; h=From:To:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=lR6VdSmUMvjFmPHHWNDsMmWz5OJwZZMZXZqjo1lizRxmJZNufxrmQaMdA6NoFAwO+2srM6YUSmA6WUCvHFVY/lbzvu/i/1r/lXidawy9dxSLN+TjxPS1FWzkmz4QYt04cknRkeEe+r6ir2ucUNX5kLbNcpgGFn5rjoANUy4nNDw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=PbNoWkMM; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="PbNoWkMM" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7731DC116D0; Wed, 21 Jan 2026 08:52:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768985537; bh=ejSWbgcSgj468U7DhaSQJWhfKNnh2RPnryiHSVZbLx0=; h=From:To:In-Reply-To:References:Subject:Date:From; b=PbNoWkMMLhqZYQb0Bg0tceVeHLqTAqr628eLdKP5JkboyJMEw+hdZYuCcybVt/1+h VXD7YKIsk3Xh/BeL2tDGoGuw2llcChQbz3r9wxoSZa5hPzlMfsIJ4Nl8OnDplWX/b+ votQH+E/VoaQWv+R2eMnn3ekUrRI/hNFZKaveoQLNm4asjOONEhQJJmEDeHmSMIqwM vEobu2hZsj8Bx/O6Lx8RIaqgZu09wxl7xEjKj5Z2krUFdXObWaC+OoPYLl6dPjJG4/ LEbWS2NNHUG23e0XWJCF07TnNmG1c54WtnEdtDQ8fqS08dSU+wy9ql6MGOOIPcpEF6 yN0j/F8XQ7a7g== From: Vinod Koul To: linux-kernel@vger.kernel.org, kishon@kernel.org, Aleksandar Gerasimovski In-Reply-To: <20260106150643.922110-1-aleksandar.gerasimovski@belden.com> References: <20260106150643.922110-1-aleksandar.gerasimovski@belden.com> Subject: Re: [PATCH] phy/marvell/phy-mvebu-cp110-utmi: fix dr_mode property read from dts Message-Id: <176898553494.1268719.2606750668583538596.b4-ty@kernel.org> Date: Wed, 21 Jan 2026 14:22:14 +0530 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.13.0 On Tue, 06 Jan 2026 15:06:43 +0000, Aleksandar Gerasimovski wrote: > The problem with the current implementation is that it does not consider > that the USB controller can have multiple PHY handles with different > arguments count, as for example we have in our cn9131 based platform: > "phys = <&cp0_comphy1 0>, <&cp0_utmi0>;". > > In such case calling "of_usb_get_dr_mode_by_phy" with -1 (no phy-cells) > leads to not proper phy detection, taking the "marvell,cp110-utmi-phy" > dts definition we can call the "of_usb_get_dr_mode_by_phy" with 0 > (#phy-cells = <0>) and safely look for that phy. > > [...] Applied, thanks! [1/1] phy/marvell/phy-mvebu-cp110-utmi: fix dr_mode property read from dts commit: e2ce913452ab56b3330539cc443b97b7ea8c3a1a Best regards, -- ~Vinod