On Mon, Jan 11, 2010 at 1:43 PM, Wolfgang Denk <w...@denx.de> wrote: > Dear Grant, > > In message <fa686aa41001111115g3451c9b9h4d6c551afd569...@mail.gmail.com> you > wrote: >> >> Please don't. I know that a lot of other 5200 code uses register map >> structures in this way, but I consider it bad practice. I coded this > > May I ask _why_ you consider this bad practice?
Many reasons. First off, while C structures somewhat represent the layout of a hardware register set, I still find them a poor fit. Registers do not data structures, and trying to describe them as such causes problems. Not all devices get mapped onto the bus in the same way. ie. a single device can get wired up with 8-bit wide addressing on one system and 32 wide on another. A struct cannot encode this. I also find I often need to access registers at "none-native" widths due to implementation details of the device which is made messy when the layout is encoded in a C struct. Finally, we're talking about a hardware interface here. Driver authors must understand exactly what they are doing when writing to registers and it is my opinion (though others may disagree with me) that using structs to describe register maps encourages a glosses over details that are best left explicit. I used to prefer C structs for register definitions, but my opinion changed as I gained more experience. > Is a structure not the most natural way to encode the specifics of a > hardware interface (address offet, bus width, etc.) in C? > > What do you recommend instead? Using lists of register offsets > (without any type information) as for example ARM is doing? Yes, that is what I prefer. That and, when needed, device-specific accessor functions that can be adapted for different bus attachements. >> driver without a structure for a reason. The reason I haven't removed > > Could you please explain this reason? As described above. > I'm trying to understand if this is a MPC52xx specific reasoning, or > if you apply this to all of PowerPC, or generally to all kernel code? I've stated what I prefer. I don't think I've rejected any code that uses structs over register offsets, but I do apply friction on any patch that changes a current driver from one to the other without need. > And: is this just your personal preferences, or generally agreed on? Others will need to answer that. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
