All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org"
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/2] ARM: tegra: config: enable SERIAL_TEGRA
Date: Thu, 17 Jan 2013 10:08:08 +0530	[thread overview]
Message-ID: <50F78030.6080305@nvidia.com> (raw)
In-Reply-To: <50F6EA0A.4080904-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

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.

WARNING: multiple messages have this Message-ID (diff)
From: ldewangan@nvidia.com (Laxman Dewangan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: tegra: config: enable SERIAL_TEGRA
Date: Thu, 17 Jan 2013 10:08:08 +0530	[thread overview]
Message-ID: <50F78030.6080305@nvidia.com> (raw)
In-Reply-To: <50F6EA0A.4080904@wwwdotorg.org>

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.

WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: tegra: config: enable SERIAL_TEGRA
Date: Thu, 17 Jan 2013 10:08:08 +0530	[thread overview]
Message-ID: <50F78030.6080305@nvidia.com> (raw)
In-Reply-To: <50F6EA0A.4080904@wwwdotorg.org>

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.





  parent reply	other threads:[~2013-01-17  4:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 13:06 [PATCH 1/2] ARM: tegra: config: enable SERIAL_TEGRA Laxman Dewangan
2013-01-16 13:06 ` Laxman Dewangan
2013-01-16 13:06 ` Laxman Dewangan
     [not found] ` <1358341572-8154-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-16 13:06   ` [PATCH 2/2] ARM: tegra: DTS: cardhu: register UARTC Laxman Dewangan
2013-01-16 13:06     ` Laxman Dewangan
2013-01-16 13:06     ` Laxman Dewangan
2013-01-16 17:57   ` [PATCH 1/2] ARM: tegra: config: enable SERIAL_TEGRA Stephen Warren
2013-01-16 17:57     ` Stephen Warren
2013-01-16 17:57     ` Stephen Warren
     [not found]     ` <50F6EA0A.4080904-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-17  4:38       ` Laxman Dewangan [this message]
2013-01-17  4:38         ` Laxman Dewangan
2013-01-17  4:38         ` Laxman Dewangan
     [not found]         ` <50F78030.6080305-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-01-17 16:27           ` Stephen Warren
2013-01-17 16:27             ` Stephen Warren
2013-01-17 16:27             ` Stephen Warren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50F78030.6080305@nvidia.com \
    --to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.