Skip to contentSkip to conversation

ordering of suspend/resume for devices. any clues, anyone?

DISCUSSION Luke Kenneth Casson Leighton 3 participants 5 messages Dec 15, 2005 – Dec 21, 2005

lore
Share & tools
lore
#0 lore raw

[hi, please kindly cc me direct as i am deliberately subscribed with settings to not receive posts from this list, but if that is inconvenient for you to cc me, don't worry i can always look up the archives to keep track of replies, thank you.]

http://handhelds.org/moin/moin.cgi/BlueAngel

works.

am seeking some advice regarding power management - specifically the ordering of devices "resume" functions being called.

we have an LCD, and an ATI chip. switching on the LCD powers up the ATI chip.

unfortunately, resume calls the ATI device initialisation _before_ the LCD resume initialisation. the ATI chip's initialisation fails - naturally - because it's not even powered up.

of course - this can't be taken care of in userspace as an apm event because the framebuffer device cannot be a module [without terminating all running x-applications].

so.

possible solutions, as i see them:

1) have some awfulness in the LCD driver and the ATI driver with some shared resume initialisation callbacks.

2) work out where the initialisation of the LCD driver is called from, and somehow get that inserted into the initialisation order in the reverse way from what it is now, such that the linked list of device drivers is inverted, such that the resume event will end up calling the LCD resume _after_ the ATI resume.

3) some lovely "dependency" work gets done in the linux kernel where you can register priorities on the resume order.

this would mirror the way that the old apm "event.d" thing would have worked.

4) other - that i don't know about, but would love to hear from someone if there already exists a solution.

any clues, anyone?

Signature · 3 lines
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
#1 lore raw
Quoted 20 lines · Luke Kenneth Casson Leighton

[hi, please kindly cc me direct as i am deliberately subscribed with settings to not receive posts from this list, but if that is inconvenient for you to cc me, don't worry i can always look up the archives to keep track of replies, thank you.]

http://handhelds.org/moin/moin.cgi/BlueAngel

works.

am seeking some advice regarding power management - specifically the ordering of devices "resume" functions being called.

we have an LCD, and an ATI chip. switching on the LCD powers up the ATI chip.

unfortunately, resume calls the ATI device initialisation _before_ the LCD resume initialisation. the ATI chip's initialisation fails - naturally - because it's not even powered up.

Quoted 7 lines

of course - this can't be taken care of in userspace as an apm event because the framebuffer device cannot be a module [without terminating all running x-applications].

so.

possible solutions, as i see them:

<snip>

Known issue, I'd take this to the linux-pm mailing list instead, as the people there are working on stuff for this.

thanks,

greg k-h

#2 lore raw
Quoted 11 lines · Greg KH
Quoted 6 lines

am seeking some advice regarding power management - specifically the ordering of devices "resume" functions being called.

<snip>

possible solutions, as i see them:

<snip>

Known issue, I'd take this to the linux-pm mailing list instead, as the people there are working on stuff for this.

thanks greg.

l.

#3 lore raw
In reply to Luke Kenneth Casson Leighton

Hi!

Quoted 12 lines

[hi, please kindly cc me direct as i am deliberately subscribed with settings to not receive posts from this list, but if that is inconvenient for you to cc me, don't worry i can always look up the archives to keep track of replies, thank you.]

http://handhelds.org/moin/moin.cgi/BlueAngel

works.

am seeking some advice regarding power management - specifically the ordering of devices "resume" functions being called.

Quoted 7 lines

we have an LCD, and an ATI chip. switching on the LCD powers up the ATI chip.

unfortunately, resume calls the ATI device initialisation _before_ the LCD resume initialisation. the ATI chip's initialisation fails - naturally - because it's not even powered up.

I'd say "make LCD system/platform device". That will init it first, shut it down last.
Pavel

Signature · 1 line
Thanks, Sharp!
#4 lore raw

heya pavel,

thanks for the tip. as it turns out, a function table was hacked-n that back-link from the w100fb framebuffer resume function into the LCD code.

in this way, it is possible to call functions in the LCD module doing GPIO to start the power-up sequence required for the LCD and backlight, wait a few ms, initialise the video chip (in the w100fb code), then call _another_ set of functions in the LCD module to finish off the initialisation.

not pretty, but there you go.

l.

Quoted 28 lines · Pavel Machek

Hi!

Quoted 12 lines

[hi, please kindly cc me direct as i am deliberately subscribed with settings to not receive posts from this list, but if that is inconvenient for you to cc me, don't worry i can always look up the archives to keep track of replies, thank you.]

http://handhelds.org/moin/moin.cgi/BlueAngel

works.

am seeking some advice regarding power management - specifically the ordering of devices "resume" functions being called.

Quoted 7 lines

we have an LCD, and an ATI chip. switching on the LCD powers up the ATI chip.

unfortunately, resume calls the ATI device initialisation _before_ the LCD resume initialisation. the ATI chip's initialisation fails - naturally - because it's not even powered up.

I'd say "make LCD system/platform device". That will init it first, shut it down last.
Pavel

Signature · 1 line
Thanks, Sharp!
Signature · 3 lines
--
<a href="http://lkcl.net">http://lkcl.net</a>
--