Device tree: bind to alternate driver, or dummy entry?

I have an alternate driver (xeno_16550A) that I would like to try to use for one UART while using the regular omap3-serial for all the others.

Is there a way to specify in the device tree which driver to use?

Alternately, could I have some kind of dummy entry in the device tree which just handles the ti,hwmods and pinmux parts without binding a driver to that device’s address? It seems like the ti,hwmods part is what gets the OS to call the write to the CM_PER_xx register to enable clocking to each peripheral’s registers… Am I correct on that?

With that fixed I can just modprobe the driver I want which is perfectly acceptable.