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: <CAKohpo=8PKk0VF3tpZLNYseHMv7dF-qg9iwKcC+VmPtb_8kzjg@mail.gmail.com>
Date:	Thu, 10 Jan 2013 14:04:53 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	Vinod Koul <vinod.koul@...el.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, 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 9 January 2013 21:08, Vinod Koul <vinod.koul@...el.com> wrote:
>> >>  subsys_initcall(dw_init);
> Viresh, Linus
>
> We had this discussion sometime back. pl022 use dma and we need DMA before SPI.
> So if we have pl022 as late_init and dma as device_init. If we have one  more
> dependency then moving dw_dmac to fs_init should help too. But arch/subsys seems
> overkill here?

We probably can't make spi late_init as they may be others waiting for
it to be in. And
so did subsys_init for dma. fs is for filesystem? then that may not be
logically correct too.

What's the problem you are seeing here with subsys_init?
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ