From: Vinod Koul <vinod.koul@intel.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
nsekhar@ti.com, olof@lixom.net,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
tony@atomide.com, t-kristo@ti.com
Subject: Re: [PATCH] dmaengine: edma: Add dummy driver skeleton for edma3-tptc
Date: Wed, 4 Nov 2015 22:11:20 +0530 [thread overview]
Message-ID: <20151104164120.GO12910@localhost> (raw)
In-Reply-To: <87egg54td4.fsf@saruman.tx.rr.com>
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
On Wed, Nov 04, 2015 at 10:33:27AM -0600, Felipe Balbi wrote:
> Peter Ujfalusi <peter.ujfalusi@ti.com> writes:
>
> > The eDMA3 TPTC does not need any software configuration, but it is a
> > separate IP block in the SoC. In order the omap hwmod core to be able to
> > handle the TPTC resources correctly in regards of PM we need to have a
> > driver loaded for it.
> > This patch will add a dummy driver skeleton without probe or remove
> > callbacks provided.
> >
> > Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> > Reported-by: Olof Johansson <olof@lixom.net>
>
> This fixes the problem I also reported on linux-omap [1]
>
> Tested-by: Felipe Balbi <balbi@ti.com>
>
> [1] http://marc.info/?l=linux-omap&m=144665429032014&w=2
Great, I was about to point you to this series, I will push this in -next
now
Thanks
--
~Vinod
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-04 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 13:21 [PATCH] dmaengine: edma: Add dummy driver skeleton for edma3-tptc Peter Ujfalusi
2015-11-04 16:33 ` Felipe Balbi
2015-11-04 16:41 ` Vinod Koul [this message]
2015-11-13 14:54 ` Tony Lindgren
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=20151104164120.GO12910@localhost \
--to=vinod.koul@intel.com \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=olof@lixom.net \
--cc=peter.ujfalusi@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).