Messages in this thread | | | Date | Tue, 22 Nov 2011 11:13:47 -0800 | From | Greg KH <> | Subject | Re: [PATCH v3 5/5] clk: export tree topology and clk data via sysfs |
| |
On Tue, Nov 22, 2011 at 09:57:41AM -0800, Mike Turquette wrote: > > Ah, comments like this warm my heart. > > > > Come on, no abusing the kobject code please, if have problems with how > > the kernel core works, and it doesn't do things you want it to, then why > > not change it to work properly for you, or at the least, ASK ME!!! > > Ok, I'm asking you now. There are two ways to solve this problem: > > 1) have kobject core create the lists linking the objects but defer > allocations and any interactions with sysfs until later in the boot > sequence, OR > > 2) my code can create a list of clks (the same way that clkdev does) > and defer kobject/sysfs stuff until later, which walks the list made > during early-boot > > #1 is most closely aligned with the code I have here, #2 presents > challenges that I haven't really though through. I know that OMAP > uses the clk framework VERY early in it's boot sequence, but as long > as the per-clk data is properly initialized then it should be OK. > > What do you think?
#3 - use debugfs and don't try to create a sysfs interface for the clock structures :)
thanks,
greg k-h
| |