From: Kevin Hilman <khilman@deeprootsystems.com>
To: linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/2] twl4030 power support for 3430SDP
Date: Fri, 02 Oct 2009 07:13:43 -0700 [thread overview]
Message-ID: <87zl89anoo.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20091002051742.GZ32041@smtp.gmail.com> (Amit Kucheria's message of "Fri\, 2 Oct 2009 08\:17\:42 +0300")
Amit Kucheria <amit.kucheria@verdurent.com> writes:
> On 09 Oct 01, Kevin Hilman wrote:
>> Amit Kucheria <amit.kucheria@canonical.com> writes:
>>
>> > On 09 Oct 01, Kevin Hilman wrote:
>> >> I've been carrying these in the PM branch, but now that twl4030 power
>> >> support is in mainline, these can be queued for 2.6.33.
>> >>
>> >> Kevin Hilman (1):
>> >> OMAP3: PM: 3430SDP: add initial twl4030 power scripts
>> >>
>> >> Rajendra Nayak (1):
>> >> OMAP3: PM: 3430SDP: Update twl4030 power scripts and device groups
>> >>
>> >> arch/arm/mach-omap2/board-3430sdp.c | 93 ++++++++++++++++++++++++++++++++++-
>> >> 1 files changed, 91 insertions(+), 2 deletions(-)
>> >>
>> >
>> > Hi Kevin,
>> >
>> > Do you want to wait until I push patches that modify the way the scripts are
>> > loaded in memory? (they now allow overlapping scripts to work around space
>> > constraints)
>> >
>> > Also we now have very simplified scripts that use broadcast messages. These
>> > might still need to be tweaked for the various boards though. It works on the
>> > RX51.
>>
>> Well, I don't *want* to wait because that means I would have to rework
>> these patches. :)
>>
>> But it sounds waiting is the right thing. How close are you to having
>> the new scripting stuff ready? Should we put it into the PM branch in
>> the meantime so it can get some testing on other boards than RX51?
>
> I haven't started looking at it yet. It will have to wait until w42 though.
>
> I guess you can push your patches to the PM branch and revert them at a later
> time when I have the changes ready?
This series is already in the PM branch, and has been for a while.
I've been waiting for the twl4030 power code to hit mainline before
submitting them.
If you think you'll get the new script stuff done in the next few
weeks, I'll wait.
Kevin
next prev parent reply other threads:[~2009-10-02 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 18:54 [PATCH 0/2] twl4030 power support for 3430SDP Kevin Hilman
2009-10-01 18:54 ` [PATCH 1/2] OMAP3: PM: 3430SDP: add initial twl4030 power scripts Kevin Hilman
2009-10-01 18:54 ` [PATCH 2/2] OMAP3: PM: 3430SDP: Update twl4030 power scripts and device groups Kevin Hilman
2009-10-01 19:24 ` [PATCH 0/2] twl4030 power support for 3430SDP Amit Kucheria
2009-10-01 23:19 ` Kevin Hilman
2009-10-02 5:17 ` Amit Kucheria
2009-10-02 14:13 ` Kevin Hilman [this message]
2009-10-02 14:24 ` Amit Kucheria
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=87zl89anoo.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
/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