[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbf7TwrjfT2rhqQFGc3yh_Nt117RtzQO2y6g5Ddx5Ay_w@mail.gmail.com>
Date: Tue, 29 Jan 2013 11:59:54 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: "Vishwanathrao Badarkhe, Manish" <manishv.b@...com>
Cc: devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
davinci-linux-open-source@...ux.davincidsp.com, anilkumar@...com,
tony@...mide.com, hs@...x.de, broonie@...nsource.wolfsonmicro.com,
sameo@...ux.intel.com, khilman@...prootsystems.com, nsekhar@...com,
linux@....linux.org.uk, rob@...dley.net, rob.herring@...xeda.com,
grant.likely@...retlab.ca
Subject: Re: [PATCH V2 1/6] pinctrl: pinctrl-single: use arch_initcall and module_exit
On Tue, Jan 29, 2013 at 8:38 AM, Vishwanathrao Badarkhe, Manish
<manishv.b@...com> wrote:
> Currently, I2C driver gets probed before pinctrl driver.
> To achieve I2C pin muxing via pinctrl driver before I2C
> probe get called, register pinctrl driver in arch_initcall.
> Also, add module_exit to unregister pinctrl driver.
>
> Signed-off-by: Vishwanathrao Badarkhe, Manish <manishv.b@...com>
So your I2C driver is not returning -EPROBE_DEFER
if it cannot find its pins?
Hm, well I can live with this, if Tony ACKs it.
Yours,
Linus Walleij
--
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/
Powered by blists - more mailing lists