Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
kristianpaul has quit [Quit: leaving]
ChanServ has quit [*.net *.split]
ChanServ has joined #qi-hardware
kristianpaul has joined #qi-hardware
kristianpaul has quit [Changing host]
kristianpaul has joined #qi-hardware
LunaVorax has quit [Ping timeout: 268 seconds]
urandom__ has quit [Quit: Konversation terminated!]
Textmode has joined #qi-hardware
emeb has left #qi-hardware [#qi-hardware]
nikescar has quit [Read error: Connection reset by peer]
nikescar has joined #qi-hardware
<mth> larsc: the battery driver uses its parent's (mfd) platform data as its own platform data
<mth> however, that approach becomes problematic if more than one subdriver needs platform data
jow_laptop has joined #qi-hardware
freakazoid0223 has quit [Ping timeout: 246 seconds]
xdpirate has joined #qi-hardware
xdpirate has quit [Client Quit]
xdpirate has joined #qi-hardware
xdpirate has quit [Quit: http://gamelauncher.pvpsucks.com/]
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
scientes has joined #qi-hardware
scientes has quit [Ping timeout: 244 seconds]
jekhor has joined #qi-hardware
ChanServ has quit [*.net *.split]
newcup has quit [*.net *.split]
DocScrutinizer05 has quit [*.net *.split]
uwe_ has quit [*.net *.split]
pabs3 has quit [*.net *.split]
kyak has quit [*.net *.split]
DocScrutinizer05 has joined #qi-hardware
uwe_ has joined #qi-hardware
newcup has joined #qi-hardware
pabs3 has joined #qi-hardware
kyak has joined #qi-hardware
<larsc> mth: yes
<Ayla> morning larsc
<larsc> hi Ayla
<Ayla> I'm back from night club, I'm going to sleep now ;)
<Ayla> ciao
<larsc> hehe
Ayla has quit [Quit: dodo]
<larsc> mth: And to be honest I don't like that approach of using the parents platform_data anymore, because it does not allow you to reuse a mfd cell for different mfd devices
kristoffer has joined #qi-hardware
Textmode has quit [Ping timeout: 255 seconds]
Textmode has joined #qi-hardware
Textmode has quit [Ping timeout: 255 seconds]
Textmode has joined #qi-hardware
Textmode has quit [Ping timeout: 255 seconds]
jekhor has quit [Ping timeout: 272 seconds]
ChanServ has joined #qi-hardware
dandon has quit [Quit: i'm so going]
LunaVorax has joined #qi-hardware
LunaVorax has quit [Remote host closed the connection]
jekhor has joined #qi-hardware
urandom__ has joined #qi-hardware
LunaVorax has joined #qi-hardware
<LunaVorax> hi!
freakazoid0223 has joined #qi-hardware
<mth> larsc: is there a way though to provide platform_data directly to an mfd subdevice?
<larsc> should be possible
<mth> I wouldn't know where to attach it
<larsc> well you'd have to split the platform data up in the mfd driver and pass it to the child devies
<mth> what would be a clean way of doing that? as in, without having the mfd driver know which child devices exist
<mth> I've got an analog joystick connected to the touch screen pins
<mth> so that demonstrates that there can be more than one driver for the same cell
<mth> (since there could be an ordinary touch screen driver as well)
<larsc> yea that case it is a bit tricky
<larsc> how does the analog joystick driver work?
<mth> I'm not sure if driver selection should be done at configure time (one driver per cell for each board) or even at runtime (loading and unloading modules)
<mth> the x and y axis both provide a voltage, which is read from the touch screen regs in the SADC
<mth> the driver doesn't work yet, I'm still writing it ;)
<mth> I think I'll just have to poll it at a fixed interval to start a read and when the read completes, inject the input events
<larsc> I wrote a TS driver back than. Take a look at commit d21ad639b3d42a2124432fa1ea7e7ea2b38e0a8d
<larsc> I think you can program the core to report new values when they change
<larsc> generate an interrupt, when the values cahnge
Aylax has joined #qi-hardware
<mth> larsc: thanks; the probe looks very similar to what I have so far, the rest might be useful when adding the actual reading
Aylax has quit [Read error: Connection reset by peer]
<mth> I'll add is_open to my driver as well, since it's useful for doing suspend properly
jekhor has quit [Ping timeout: 244 seconds]
Ayla has joined #qi-hardware
guanucoluis1 has joined #qi-hardware
LunaVorax has quit [Quit: Quitte]
<larsc> mth: Have you seen commit 95ceafd46 ("cpufreq: Add a generic cpufreq-cpu0 driver")
<larsc> basically a cpufreq driver which uses the clk API
<larsc> could replace the jz4740 cpufreq driver
<Ayla> awesome
<larsc> at least I think it could
porchao has joined #qi-hardware
porchaso0 has quit [Ping timeout: 248 seconds]
<mth> larsc: I haven't seen it yet
<mth> replacing the driver would be good if possible
<mth> the most problematic part though is that derived clocks have to be shut down during the PLL reconfiguration
<Ayla> it's not a problem
<mth> no?
<Ayla> just move the code that reinits the PLL to the clock driver
<mth> it's already there
<Ayla> no, it's on the cpufreq driver
<mth> it's not; the cpufreq driver calls the clock driver
<mth> you can't just disable the other clocks at an arbitrary moment, you have to give the respective drivers a chance to stop their work at a point where that is possible
<larsc> the current approach is to use the cpufreq notifiers, isn't it?
<Ayla> readl / writel are deprecated?
<mth> larsc: yes, but it's only implemented for mmc at the moment
<larsc> Ayla: sort of, but nobody cares
<Ayla> I'll just use iowrite32/ioread32
<Ayla> I don't know what header to include for readl/writel :)
<larsc> io.h
emeb has joined #qi-hardware
Ayla is now known as AwAyla
porchao has quit [Read error: Connection reset by peer]
jekhor has joined #qi-hardware
heberth has joined #qi-hardware
porchao has joined #qi-hardware
dandon has joined #qi-hardware
heberth has quit [Quit: leaving]
Textmode has joined #qi-hardware
xdpirate has joined #qi-hardware
Textmode has quit [Max SendQ exceeded]
Textmode has joined #qi-hardware
guanucoluis1 has quit [Ping timeout: 272 seconds]
heberth has joined #qi-hardware
guanucoluis1 has joined #qi-hardware
guanucoluis1 has quit [Ping timeout: 272 seconds]
Textmode has quit [Ping timeout: 255 seconds]
Textmode has joined #qi-hardware
LunaVorax has joined #qi-hardware
kristoffer has quit [Quit: Leaving]
kuribas has joined #qi-hardware
heberth has quit [Quit: leaving]
GNUtoo|laptop has joined #qi-hardware
aisa has quit [Quit: leaving]
jekhor has quit [Ping timeout: 264 seconds]
kuribas has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
guanucoluis1 has joined #qi-hardware
guanucoluis1 has quit [Ping timeout: 272 seconds]
GNUtoo|laptop has quit [Quit: Program received signal SIGSEGV, Segmentation fault.]
emeb has left #qi-hardware [#qi-hardware]
valhalla_ has quit [Ping timeout: 272 seconds]