Date: Wed, 8 Oct 2014 11:10:28 -0700
From: Tony Lindgren <tony@atomide.com>
To: He YunLei <heyunlei@huawei.com>
Cc: linux-kernel@vger.kernel.org, grant.likely@linaro.org, robh+dt@kernel.org,
        wangbintian@huawei.com, liguozhu@hisilicon.com,
        kong.kongxinwei@hisilicon.com
Subject: Re: [RFC PATCH] pinctrl: pinctrl-single.c:  init pinctrl single at
 arch_initcall time
Message-ID: <20141008181027.GE10014@atomide.com>
References: <542934F4.10303@huawei.com>
 <20140929175427.GE3122@atomide.com>
 <54349671.6090008@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54349671.6090008@huawei.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org

* He YunLei <heyunlei@huawei.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/