Re: [PATCH 1/3] Clocklib: add generic framework for managingclocks.

[Haavard Skinnemoen]

Pavel Machek <pavel@xxxxxx> wrote:
> > Hmm...this is exactly twice as big as the struct I'm currently using,
> > it doesn't contain all the fields I need, and it's undocumented.  
> 
> Like unifying 15-or-so versions of clock framework that are out there?

I'm not complaining about the goal of this patchset, I'm just arguing
about the price. And I do think we managed to come to an agreement
later in the thread (which is actually cheaper than what I currently
have!)

> > I have quite a few clocks, so the increased memory consumption is quite
> > significant. What are the advantages of this?  
> 
> How many clocks do you have?

55 currently, and there are still a few clocks that haven't been wired
up yet. So shaving off a few bytes can make a big difference, and other
platforms have even more clocks.

Haavard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/