> Ok, how about 'sparse16550'? Otherwise identical to ns16550, but with > the reg-shift property. I'll send a patch shortly, and I'll reorder > the > match table -- if something claims compatibility with both 8250 and > 16550, shouldn't we drive it as the latter? > > Can we add properties to indicate the common high-speed modes too? The > Natsemi baud-base thing could be autodetected by 8250.c if you'd > let it, > but the SMSC trick just has to be set as a UPF_MAGIC_MULTIPLIER flag.
So just use "compatible" = "smsc,blablabla". Your device has extra features over a 16550, namely that extra multiplier or whatever; so just match those new features from the device name (i.e., "compatible" property), don't try to retrofit those features onto an existing driver. And don't make up names for devices (like "sparse16550") unless you really really have to, it definitely isn't needed here. For your new device name, you can either have the register spacing an implicit property of the device, or you can put it in a "reg-shift" property if you want. Segher _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
