Hello,

While I review the dm6467 and dm355 patches, and prepare for an update
to newer kernels, I've created a temporary staging branch[1] where
I've applied the dm646x and dm355 patches.

On top of that, I've added a small series of rework patches where I've
reworked how and where base addresses are defined, init functions are
declared.  I'm very interested in your comments on this layout.

Basically, what I've done is got rid of most of the base address
definitions as global defines.  The remaining ones that need to global
and that are common to ALL chips in the family will live in
hardware.h.  Ones that need to be global and are chip specific should
live in <chipname>.h

Note that I said "need to be global".  Most base address defines do
not need to be in a global header.  They are only ever used in
chip/board specific init code to fill in platform_data which is then
passed to the driver.  Drivers should _never_ be using base address
defines directly.

I've compile and boot tested this kernel on dm6446, dm6467 and dm355.

Kevin

[1] See the 'tmp/staging branch in DaVinci git.

http://source.mvista.com/git/?p=linux-davinci-2.6.git;a=shortlog;h=refs/heads/tmp/ti-staging

_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to