[PATCH 0/5 V3] pch_uart: Cleanups, board quirks, and user uartclk parameter

[Darren Hart]

This series does some minor clean-up to the pch_uart driver, adds support
for the Fish River Island II UART clock quirks, and introduces a user_uartclk
parameter to aid in developing for early and changing hardware.

In order to support an early serial console, we cannot rely on the pch_phub
probe function to setup the CFGCLK register. This series relies on the board
quirks and does not force the setting of the CLKREG in the pch_phub code.
Instead, it aligns with what is the default configuration (defined by firmware)
for a given board. The user_uartclk parameter provides a mechanism to force a
specific uartclk if necessary.

V2: Incorporates Alan Cox's feedback into 2/4: Add Fish River Island II uart
    clock quirks, refactoring the clock quirks into a new function and using
    a more appropriate name for a reused string variable.
    Add support for the two firmware variants for the FRI2.

V3: Rebase on linux-next.git/master rather than linux-2.6.git.
    Add module parameter descriptions.

The following changes since commit d5ba8c14a256799efb1048151fe3490f9cb989b9:

  Add linux-next specific files for 20120309 (2012-03-09 19:04:19 +1100)

are available in the git repository at:
  git://git.infradead.org/users/dvhart/linux-next.git pch_uart_v3
  http://git.infradead.org/users/dvhart/linux-next.git/shortlog/refs/heads/pch_uart_v3

Darren Hart (5):
  pch_uart: Use uartclk instead of base_baud
  pch_uart: Add Fish River Island II uart clock quirks
  pch_uart: Add user_uartclk parameter
  pch_uart: Use existing default_baud in setup_console
  pch_uart: Add module parameter descriptions

 drivers/tty/serial/pch_uart.c |   59 ++++++++++++++++++++++++++++------------
 1 files changed, 41 insertions(+), 18 deletions(-)

-- 
1.7.6.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/