| Message ID | 1358341572-8154-1-git-send-email-ldewangan@nvidia.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
On 01/16/2013 06:06 AM, Laxman Dewangan wrote:
> Enable high speed serial driver for tegra platform.
Thanks, I've applied patch 1 to Tegra's for-3.9/defconfig branch and
patch 2 to Tegra's for-3.9/dt branch.
Just as an FYI, the dt branch is merged into my for-next branch, and
sent upstream, before the defconfig branch, so your patch order was
reversed relative to that, but it's not an issue here.
Question: How do I test this; do I just fire up bluez(?) and point it at
the UARTC serial port, or is there more to it?
On Wednesday 16 January 2013 11:27 PM, Stephen Warren wrote: > On 01/16/2013 06:06 AM, Laxman Dewangan wrote: >> Enable high speed serial driver for tegra platform. > Thanks, I've applied patch 1 to Tegra's for-3.9/defconfig branch and > patch 2 to Tegra's for-3.9/dt branch. > > Just as an FYI, the dt branch is merged into my for-next branch, and > sent upstream, before the defconfig branch, so your patch order was > reversed relative to that, but it's not an issue here. Thanks for applying it. There is no issue on the reversing the sequence. > Question: How do I test this; do I just fire up bluez(?) and point it at > the UARTC serial port, or is there more to it? I tested this in may pieces, not with the bluez. I tested this in downstream with linux-next dma, this new serial driver, some hacks in the board files with bluetooth. Then I tested this again on linux-next with some hacks in board-dt filew with invoking the driver from cardhu dts file. In this I tested driver registration, basic write is wokring or not with some register dump/interrupt, Not checked data integrity as not connected the serial sniffer. The idea is that nothing should be crash in linux-next. The basic driver code is already tested with bluetooth.
On 01/16/2013 09:38 PM, Laxman Dewangan wrote: > On Wednesday 16 January 2013 11:27 PM, Stephen Warren wrote: >> On 01/16/2013 06:06 AM, Laxman Dewangan wrote: >>> Enable high speed serial driver for tegra platform. >> Thanks, I've applied patch 1 to Tegra's for-3.9/defconfig branch and >> patch 2 to Tegra's for-3.9/dt branch. >> >> Just as an FYI, the dt branch is merged into my for-next branch, and >> sent upstream, before the defconfig branch, so your patch order was >> reversed relative to that, but it's not an issue here. > > Thanks for applying it. There is no issue on the reversing the sequence. > > >> Question: How do I test this; do I just fire up bluez(?) and point it at >> the UARTC serial port, or is there more to it? > > I tested this in may pieces, not with the bluez. > I tested this in downstream with linux-next dma, this new serial driver, > some hacks in the board files with bluetooth. > > Then I tested this again on linux-next with some hacks in board-dt filew > with invoking the driver from cardhu dts file. In this I tested driver > registration, basic write is wokring or not with some register > dump/interrupt, Not checked data integrity as not connected the serial > sniffer. The idea is that nothing should be crash in linux-next. The > basic driver code is already tested with bluetooth. Well, my question was more about what user-space tools/configuration/... do I need to bring up Bluetooth to test this? I assume that now both the driver and DT patches are in linux-next, I shouldn't have to touch the kernel at all to make this work?
diff --git a/arch/arm/configs/tegra_defconfig b/arch/arm/configs/tegra_defconfig index a7827fd..4c5cc08 100644 --- a/arch/arm/configs/tegra_defconfig +++ b/arch/arm/configs/tegra_defconfig @@ -112,6 +112,7 @@ CONFIG_INPUT_MPU3050=y # CONFIG_DEVKMEM is not set CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y +CONFIG_SERIAL_TEGRA=y CONFIG_SERIAL_OF_PLATFORM=y # CONFIG_HW_RANDOM is not set CONFIG_I2C=y
Enable high speed serial driver for tegra platform. Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> --- arch/arm/configs/tegra_defconfig | 1 + 1 files changed, 1 insertions(+), 0 deletions(-)