On 02 Jul 02:08 PM, Dave Airlie wrote:
On 2 July 2014 12:31, Darren Etheridge detheri...@ti.com wrote:
On 07/01/2014 06:39 PM, Guido Martínez wrote:
On Fri, Jun 27, 2014 at 05:08:51PM -0500, Darren Etheridge wrote:
[snip]
Otherwise I think this is a good and useful patch series.
deferal messages. Have you tried building
everything as a module or moving the DMA devicetree node so it's
probed earlier?
But I'm not sure it's related to the problem you are seeing.
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
--
To unsubscribe from this list: send the line
bad for not putting proper patch v1, v2 information somewhere.
Sorry about that,
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On 26 Jun 12:02 PM, Guido Martínez wrote:
Currently, child nodes of the gpmc node are iterated and probed
regardless of their 'status' property. This means adding 'status =
disabled;' has no effect.
This patch changes the iteration to only probe nodes marked as
available.
Signed-off-by:
(Ccing Guido back)
Hello Russell, Darren,
On 25 Jun 02:00 PM, Russell King - ARM Linux wrote:
On Tue, Jun 24, 2014 at 05:04:36PM -0500, Darren Etheridge wrote:
On 06/17/2014 09:17 AM, Guido Martínez wrote:
Use module_init instead of late_initcall, as is the norm for modular
drivers.
On 24 Jun 05:06 PM, Darren Etheridge wrote:
On 06/17/2014 09:17 AM, Guido Martínez wrote:
The TI tilcdc driver is designed with a notion of submodules. Currently,
at unload time, these submodules are iterated and destroyed.
Now that the tilcdc remove order is fixed, this can be handled
Hi Russell,
On 25 Jun 03:46 PM, Russell King - ARM Linux wrote:
That doesn't make any sense. Using late_initcall for the tilcdc DRM
driver would make the tilcdc DRM get probed before any other regular
module_init driver, including the tda998x encoder.
A module_init() is a
the problem and, frankly, there's no other way to fix
this. Just resend with linux-usb in Cc.
Ouch, forgot about linux-usb on this one! I'm resending on top of
v3.16-rc1 (although I think this one already applies).
Thanks for the feedback,
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
On 09 May 09:25 AM, Sebastian Andrzej Siewior wrote:
On 05/09/2014 08:22 AM, George Cherian wrote:
Just by remodelling the dt the whole problem can be solved.
I am still not convinced why we should not be doing it?
Because neither ways its not the exact representation of the H/W.
Ha. Now
:-(
I've been debugging this and I think we simply cannot support removal
of the musb_am335x
module.
Had this ever worked before?
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord
and
remove the childs so the DMA is probed first and the removed last.
We can always get rid of such workaround, once we can remove the DMA controller
out of the USB - as it should be.
--
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar
--
To unsubscribe from this list: send the line unsubscribe
11 matches
Mail list logo
