linux-kernel - Re: [PATCH] w1-gpio: handle of_get_gpio() returning -EPROBE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <380901392686780@web3m.yandex.ru>
Date:	Tue, 18 Feb 2014 05:26:20 +0400
From:	zbr@...emap.net
To:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
Cc:	"kernel@...gutronix.de" <kernel@...gutronix.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] w1-gpio: handle of_get_gpio() returning -EPROBE_DEFER better

Hi

14.02.2014, 02:05, "Uwe Kleine-König" <u.kleine-koenig@...gutronix.de>:
> of_get_gpio() might return -EPROBE_DEFER meaning that the driver
> providing the gpio isn't ready yet. If that happens for the first gpio
> the resulting kernel output without this patch is:
>
>         w1-gpio somename: Failed to parse DT
>         platform somename: Driver w1-gpio requests probe deferral
>
> The first message is misleading and so is suppressed with this patch.
>
> Further if determining the gpio to switch the external pullup yields
> -EPROBE_DEFER this error should be passed back to the caller instead of
> just continuing without pullup.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>

I'm ok with this patch, but I virtually do not understand what it does :)
Since I know nothing about device trees.

But yet it looks innocent enough to merge.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/