lvds-encoder... why not lvds-bridge?

Hi gang! I was wondering why lvds-encoder.c is named like that. (https://github.com/torvalds/linux/commit/67cc3e22b00f9027eaa0902ecf52ac5f4f5cac97) The driver is clearly a drm_bridge, nested in the drm/bridge subdir... so why not "lvds-bridge.c"? Also, the associated bindings document is named "

lvds-encoder... why not lvds-bridge

Bonjour Laurent! I was wondering why you choose to name the lvds-encoder.c driver like so. (https://github.com/torvalds/linux/commit/67cc3e22b00f9027eaa0902ecf52ac5f4f5cac97) The driver is clearly a drm_bridge, nested in the drm/bridge subdir... so why not "lvds-bridge.c"? Also, the associated b