From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] adding back some features
Date: Mon, 15 Jun 2009 07:55:30 -0700 [thread overview]
Message-ID: <87ski1a6n1.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20090615080001.GC4474@atomide.com> (Tony Lindgren's message of "Mon\, 15 Jun 2009 01\:00\:02 -0700")
Tony Lindgren <tony@atomide.com> writes:
> Hi,
>
> * Kevin Hilman <khilman@deeprootsystems.com> [090612 15:13]:
>> Here's a couple patches to add-back some feature dropped in the
>> mainline sync. These are needed for the PM branch among other things.
>>
>> Applies to linux-omap master.
>>
>> Kevin
>>
>> Kalle Jokiniemi (1): OMAP3: DMA: Enable idlemodes for DMA OCP
>
> This we could justify getting into mainline as a fix, as otherwise
> some PM features won't work. Will add into omap-fixes.
Thanks.
>> Kevin Hilman (1):
>> OMAP2/3: SoC IDs: add omap_type() for determining GP/EMU/HS
>
> Is there any reason to get this one into mainline early?
Well, the PM branch has a dependency, but also the recenetly submitted
qwatchdog driver has a dependency.
> If not, I suggest you keep this in your pm branch for next merge
> window that I can keep merging to l-o master as needed.
>
> However, if omap_type() is by other queues earlier, then I can
> add it into my upstream queue. If this blocks several queues
> from being rebased against mainline kernel, that alone might
> already be a good enough reason to get it in early.
I think it should go via your upstream queue. I imagine some of the
other upcoming driver submissions from TI will have a dependency as
well since there is still some missing EMU/HS support ind drivers.
Kevin
>
> Regards,
>
> Tony
>
>
>> arch/arm/mach-omap2/id.c | 22 ++++++++++++++++++++++
>> arch/arm/plat-omap/dma.c | 13 +++++++++++++
>> arch/arm/plat-omap/include/mach/dma.h | 15 +++++++++++++++
>> 3 files changed, 50 insertions(+), 0 deletions(-)
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-15 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 22:11 [PATCH 0/2] adding back some features Kevin Hilman
2009-06-12 22:11 ` [PATCH 1/2] OMAP2/3: SoC IDs: add omap_type() for determining GP/EMU/HS Kevin Hilman
2009-06-12 22:11 ` [PATCH 2/2] OMAP3: DMA: Enable idlemodes for DMA OCP Kevin Hilman
2009-06-15 8:56 ` [APPLIED] " Tony Lindgren
2009-06-17 8:33 ` [APPLIED] [PATCH 1/2] OMAP2/3: SoC IDs: add omap_type() for determining Tony Lindgren
2009-06-15 8:00 ` [PATCH 0/2] adding back some features Tony Lindgren
2009-06-15 14:55 ` Kevin Hilman [this message]
2009-06-15 16:05 ` Kevin Hilman
2009-06-17 8:31 ` Tony Lindgren
2009-06-17 8:35 ` Paul Walmsley
2009-06-17 9:58 ` Tony Lindgren
2009-06-17 13:56 ` Tero.Kristo
2009-06-17 14:04 ` Kevin Hilman
2009-06-18 0:00 ` Kevin Hilman
2009-06-17 8:39 ` [APPLIED] " 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=87ski1a6n1.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--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