linux-kernel - Re: [RFC PATCH] pinctrl: pinctrl-single.c: init pinctrl single at arch

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: <20141008181027.GE10014@atomide.com>
Date:	Wed, 8 Oct 2014 11:10:28 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	He YunLei <heyunlei@...wei.com>
Cc:	linux-kernel@...r.kernel.org, grant.likely@...aro.org,
	robh+dt@...nel.org, wangbintian@...wei.com, liguozhu@...ilicon.com,
	kong.kongxinwei@...ilicon.com
Subject: Re: [RFC PATCH] pinctrl: pinctrl-single.c:  init pinctrl single at
 arch_initcall time

* He YunLei <heyunlei@...wei.com> [141007 18:43]:
> 
> Thanks for your review and I am really appreciated it, but in our arm
> platform, we haven't custom initcall levels for other drivers. Although
> deferred probe helps other drivers to register well, we are also confused
> for the issues of lots of pin request errors debug output while booting the
> kernel. Besides, if the number is bigger than the limited number, whether
> deferred probe can solve this problem.

OK. Care to provide some examples where this happens on your
platform?

Note that we already have pinctrl very early in drivers/Makefile.
What are the early users for pinctrl-single in your setup?

Regards,

Tony
--
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/