[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5BycGHNocULcScDczRoEvbQqjnRZTDrNAw7=+zpadSOSA@mail.gmail.com>
Date: Tue, 18 Jul 2017 09:52:51 -0300
From: Fabio Estevam <festevam@...il.com>
To: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Fabio Estevam <fabio.estevam@....com>
Subject: Re: [PATCH net-next] mdio_bus: Remove unneeded gpiod NULL check
On Tue, Jul 18, 2017 at 9:48 AM, Sergei Shtylyov
<sergei.shtylyov@...entembedded.com> wrote:
> On 07/18/2017 03:39 PM, Fabio Estevam wrote:
>
>>> Won't this result in kernel WARNING when GPIO is disabled?
>
>
> GPIO support, I was going to type...
>
>> Not sure if I understood your point, but gpiod_set_value_cansleep() is
>> a no-op when the gpiod is NULL.
>
>
> Look at the stub in <linux/gpio/consumer.h>, it has WARN_ON(1).
This patch does not alter the behavior of the driver with respect to
GPIO being disabled, so I still do not understand your concern.
Please be more specific.
Powered by blists - more mailing lists