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
| ||
|
Message-ID: <20130112122825.GW19691@intel.com> Date: Sat, 12 Jan 2013 04:28:26 -0800 From: Vinod Koul <vinod.koul@...el.com> To: Mika Westerberg <mika.westerberg@...ux.jf.intel.com> Cc: Andy Shevchenko <andy.shevchenko@...il.com>, Linus Walleij <linus.walleij@...aro.org>, Andy Shevchenko <andriy.shevchenko@...ux.jf.intel.com>, linux-kernel@...r.kernel.org, Viresh Kumar <viresh.kumar@...aro.org>, spear-devel <spear-devel@...t.st.com> Subject: Re: [resend][PATCH 01/16] dw_dmac: call .probe after we have a device in place On Wed, Jan 09, 2013 at 08:04:28PM +0200, Mika Westerberg wrote: > > If the platform device is not yet created (like it might be when it is > enumerated from ACPI for example), the probe fails completely. Certainly > not the situation we want. > > Calling platform_driver_register() handles both cases properly. Yes this is fix for that kind of problem. But the main issue I am concerned about is that devices should have created much before drivers started loading. Obviosuly due to SPI/DMA dependencies we have to do this. -- ~Vinod -- 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