Re: [PATCH v4 0/4] ARM: OMAP2+: AM33XX: VDD CORE OPP50 support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Tue, Sep 3, 2013 at 11:55 AM, Russ Dill <Russ.Dill@xxxxxx> wrote:
> On Fri, Aug 30, 2013 at 9:06 AM, Kevin Hilman <khilman@xxxxxxxxxx> wrote:
>> Well, I was thinking of something much dumber.
>>
>> I was thinking about just _carefully_ writing a single, self-contained C
>> function, with all of its data on the stack (and consts as #defines).
>> Think of it is a step up in readability from straight assembly (which
>> was the stated reason for moving the code to the M3 in the first place.)
>>
>> Kevin
>
> That can only give you your suspend function. You need a resume
> function to undo everything before calling cpu_resume, and the resume
> function needs access to the data that was in the suspend function.

Well, it can be done (and I've seen it done) with various hacks, but I
agree it's not pretty, but it is at least slightly prettier than piles
of asm.  That being said, I saw you posted a more generic solution
that looks like a real solution that can scale.  I'll have a closer
look at that.  Thanks for working on it.

Kevin
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux