[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5691f9a6-07f0-4295-a25d-cb5bc572e824@omp.ru>
Date: Wed, 19 Mar 2025 18:35:47 +0300
From: Sergey Shtylyov <s.shtylyov@....ru>
To: Geert Uytterhoeven <geert+renesas@...der.be>, Rob Herring
<robh@...nel.org>, Marc Kleine-Budde <mkl@...gutronix.de>, Vincent Mailhol
<mailhol.vincent@...adoo.fr>, Vinod Koul <vkoul@...nel.org>, Kishon Vijay
Abraham I <kishon@...nel.org>, Peter Rosin <peda@...ntia.se>, Aswath
Govindraju <a-govindraju@...com>
CC: <linux-can@...r.kernel.org>, <linux-phy@...ts.infradead.org>,
<linux-renesas-soc@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] phy: can-transceiver: Re-instate "mux-states" property
presence check
On 3/19/25 4:27 PM, Geert Uytterhoeven wrote:
> On the Renesas Gray Hawk Single development board:
>
> can-transceiver-phy can-phy0: /can-phy0: failed to get mux-state (0)
>
> "mux-states" is an optional property for CAN transceivers. However,
> mux_get() always prints an error message in case of an error, including
> when the property is not present, confusing the user.
>
> Fix this by re-instating the property presence check.
>
> This is bascially a revert of commit d02dfd4ceb2e9f34 ("phy:
Basically. :-)
> can-transceiver: Drop unnecessary "mux-states" property presence
> check"), with two changes:
> 1. Use the proper API for checking whether a property is present,
> 2. Do not print an error message, as the mux core already takes care
> of that.
>
> Fixes: d02dfd4ceb2e9f34 ("phy: can-transceiver: Drop unnecessary "mux-states" property presence check")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> ---
> Alternatively, the multiplexer subsystem needs to gain support for
> getting an optional mux...
[...]
MBR, Sergey
Powered by blists - more mailing lists