Hi,
On Thu, Feb 14 2013, Balaji T K wrote:
On Thursday 14 February 2013 04:13 PM, Jan Lübbe wrote:
On Wed, 2013-01-30 at 10:07 +0100, Jan Luebbe wrote:
If the CD/WP-GPIOs are not provided by the SoC's GPIO controller,
we need to handle the case where omap_hsmmc is probed earlier than
the
On Thu, 2013-02-14 at 19:23 +0530, Balaji T K wrote:
On Thursday 14 February 2013 04:13 PM, Jan Lübbe wrote:
On Wed, 2013-01-30 at 10:07 +0100, Jan Luebbe wrote:
If the CD/WP-GPIOs are not provided by the SoC's GPIO controller,
we need to handle the case where omap_hsmmc is probed earlier
On Wed, 2013-01-30 at 10:07 +0100, Jan Luebbe wrote:
If the CD/WP-GPIOs are not provided by the SoC's GPIO controller,
we need to handle the case where omap_hsmmc is probed earlier than
the GPIO controller chosen in the device tree.
Fix this by checking the return value of of_get_named_gpio
On Thursday 14 February 2013 04:13 PM, Jan Lübbe wrote:
On Wed, 2013-01-30 at 10:07 +0100, Jan Luebbe wrote:
If the CD/WP-GPIOs are not provided by the SoC's GPIO controller,
we need to handle the case where omap_hsmmc is probed earlier than
the GPIO controller chosen in the device tree.
Fix
If the CD/WP-GPIOs are not provided by the SoC's GPIO controller,
we need to handle the case where omap_hsmmc is probed earlier than
the GPIO controller chosen in the device tree.
Fix this by checking the return value of of_get_named_gpio against
-EPROBE_DEFER and passing it through to the probe
