From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Tony Lindgren <tony@atomide.com>
Cc: George Cherian <george.cherian@ti.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux@arm.linux.org.uk,
galak@codeaurora.org, ijc+devicetree@hellion.org.uk,
mark.rutland@arm.com, pawel.moll@arm.com, robh+dt@kernel.org,
bcousson@baylibre.com, bigeasy@linutronix.de,
yegorslists@googlemail.com, balbi@ti.com
Subject: Re: [RFC PATCH] ARM: dts: am33xx: Re-arrange the USB dt to reflect the h/w configuration
Date: Sat, 17 May 2014 21:09:08 -0300 [thread overview]
Message-ID: <20140518000908.GA2092@arch.cereza> (raw)
In-Reply-To: <20140514215034.GL27426@atomide.com>
Hello Tony,
On 14 May 02:50 PM, Tony Lindgren wrote:
> * George Cherian <george.cherian@ti.com> [140508 23:34]:
> > Re arrange the USB dt for AM33xx to take it a bit closer
> > to the hardware configuration.
> >
[..]
>
> Is this just a cosmetic change or is this trying to workaround
> some edma related init order issue?
>
This was an attempt from George to workaround an that happens when
the musb_am335x module is removed. However, we've agreed to prevent
the removal instead. I've just (re)sent a patch for it:
See: [PATCH for v3.15] usb: musb: Fix panic upon musb_am335x module removal
AFAIK, this fixes a serious problem so I've marked it for stable.
For the DMA init order issue, I've done a new patch that forces the
probe order in the driver. I'll post that soon.
--
Ezequiel Garcia, VanguardiaSur
www.vanguardiasur.com.ar
prev parent reply other threads:[~2014-05-18 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 6:31 [RFC PATCH] ARM: dts: am33xx: Re-arrange the USB dt to reflect the h/w configuration George Cherian
[not found] ` <1399617068-19826-1-git-send-email-george.cherian-l0cyMroinI0@public.gmane.org>
2014-05-14 21:50 ` Tony Lindgren
2014-05-15 6:08 ` George Cherian
2014-05-18 0:09 ` Ezequiel Garcia [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140518000908.GA2092@arch.cereza \
--to=ezequiel@vanguardiasur.com.ar \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=bigeasy@linutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=george.cherian@ti.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
--cc=yegorslists@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).