All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Sourav <sourav.poddar@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, Felipe Balbi <balbi@ti.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	gregkh@linuxfoundation.org, tony@atomide.com,
	linux-kernel@vger.kernel.org, santosh.shilimkar@ti.com,
	linux-serial@vger.kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, alan@linux.intel.com
Subject: Re: [RFT/PATCH] serial: omap: prevent resume if device is not suspended.
Date: Fri, 12 Oct 2012 09:35:54 -0700	[thread overview]
Message-ID: <877gqv7imt.fsf@deeprootsystems.com> (raw)
In-Reply-To: <50784458.9080806@ti.com> (Sourav's message of "Fri, 12 Oct 2012 21:54:56 +0530")

Sourav <sourav.poddar@ti.com> writes:

> Hi Paul,
>
> There are
> On Thursday 11 October 2012 11:58 PM, Paul Walmsley wrote:
>> Hi Sourav, Felipe,
>>
>> any progress on fixing the N800 problem?  Would be good to keep it booting
>> since we use it as our primary 2420 test platform.
>>
>>
>> - Paul
> The patch sent inlined below might help us to get rid of the serial
> init issue.
> Unfortunately, I dont have a N800 board with me to test it and will require
> your help to do so.
> -----------
> From: Sourav Poddar <sourav.poddar@ti.com>
> Date: Wed, 1 Aug 2012 15:44:12 +0530
> Subject: [RFT/PATCH] serial: omap: Fix N800 serial init issue.
>
>
> This patch might solve the N800 serial init issue.
>
> This patch will also give pointers if there is any mux settings issue
> with N800 OR
> a mismatch between the initial harware state, runtime PM state and
> omap hwmod state.

> I don't have a N800 schematics to check about the mux settings getting used.
>
> The observation on beagle board XM with this patch on different boards
> looks flaky,
> so your feedback on beagle board will also be very helpful.
>
> Cc: Felipe Balbi <balbi@ti.com>
> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
> ---
>  drivers/tty/serial/omap-serial.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/tty/serial/omap-serial.c
> b/drivers/tty/serial/omap-serial.c
> index 6ede6fd..3fbc7f7 100644
> --- a/drivers/tty/serial/omap-serial.c
> +++ b/drivers/tty/serial/omap-serial.c
> @@ -1414,6 +1414,7 @@ static int __devinit serial_omap_probe(struct
> platform_device *pdev)
>         INIT_WORK(&up->qos_work, serial_omap_uart_qos_work);
>
>         platform_set_drvdata(pdev, up);
> +       pm_runtime_set_active(&pdev->dev);

NAK.

This will obviously break platforms where the UARTs are not active
before driver loads.

Kevin

>         pm_runtime_enable(&pdev->dev);
>         pm_runtime_use_autosuspend(&pdev->dev);
>         pm_runtime_set_autosuspend_delay(&pdev->dev,

WARNING: multiple messages have this Message-ID (diff)
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFT/PATCH] serial: omap: prevent resume if device is not suspended.
Date: Fri, 12 Oct 2012 09:35:54 -0700	[thread overview]
Message-ID: <877gqv7imt.fsf@deeprootsystems.com> (raw)
In-Reply-To: <50784458.9080806@ti.com> (Sourav's message of "Fri, 12 Oct 2012 21:54:56 +0530")

Sourav <sourav.poddar@ti.com> writes:

> Hi Paul,
>
> There are
> On Thursday 11 October 2012 11:58 PM, Paul Walmsley wrote:
>> Hi Sourav, Felipe,
>>
>> any progress on fixing the N800 problem?  Would be good to keep it booting
>> since we use it as our primary 2420 test platform.
>>
>>
>> - Paul
> The patch sent inlined below might help us to get rid of the serial
> init issue.
> Unfortunately, I dont have a N800 board with me to test it and will require
> your help to do so.
> -----------
> From: Sourav Poddar <sourav.poddar@ti.com>
> Date: Wed, 1 Aug 2012 15:44:12 +0530
> Subject: [RFT/PATCH] serial: omap: Fix N800 serial init issue.
>
>
> This patch might solve the N800 serial init issue.
>
> This patch will also give pointers if there is any mux settings issue
> with N800 OR
> a mismatch between the initial harware state, runtime PM state and
> omap hwmod state.

> I don't have a N800 schematics to check about the mux settings getting used.
>
> The observation on beagle board XM with this patch on different boards
> looks flaky,
> so your feedback on beagle board will also be very helpful.
>
> Cc: Felipe Balbi <balbi@ti.com>
> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
> ---
>  drivers/tty/serial/omap-serial.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/tty/serial/omap-serial.c
> b/drivers/tty/serial/omap-serial.c
> index 6ede6fd..3fbc7f7 100644
> --- a/drivers/tty/serial/omap-serial.c
> +++ b/drivers/tty/serial/omap-serial.c
> @@ -1414,6 +1414,7 @@ static int __devinit serial_omap_probe(struct
> platform_device *pdev)
>         INIT_WORK(&up->qos_work, serial_omap_uart_qos_work);
>
>         platform_set_drvdata(pdev, up);
> +       pm_runtime_set_active(&pdev->dev);

NAK.

This will obviously break platforms where the UARTs are not active
before driver loads.

Kevin

>         pm_runtime_enable(&pdev->dev);
>         pm_runtime_use_autosuspend(&pdev->dev);
>         pm_runtime_set_autosuspend_delay(&pdev->dev,

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Sourav <sourav.poddar@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, Felipe Balbi <balbi@ti.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	<gregkh@linuxfoundation.org>, <tony@atomide.com>,
	<linux-kernel@vger.kernel.org>, <santosh.shilimkar@ti.com>,
	<linux-serial@vger.kernel.org>, <linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <alan@linux.intel.com>
Subject: Re: [RFT/PATCH] serial: omap: prevent resume if device is not suspended.
Date: Fri, 12 Oct 2012 09:35:54 -0700	[thread overview]
Message-ID: <877gqv7imt.fsf@deeprootsystems.com> (raw)
In-Reply-To: <50784458.9080806@ti.com> (Sourav's message of "Fri, 12 Oct 2012 21:54:56 +0530")

Sourav <sourav.poddar@ti.com> writes:

> Hi Paul,
>
> There are
> On Thursday 11 October 2012 11:58 PM, Paul Walmsley wrote:
>> Hi Sourav, Felipe,
>>
>> any progress on fixing the N800 problem?  Would be good to keep it booting
>> since we use it as our primary 2420 test platform.
>>
>>
>> - Paul
> The patch sent inlined below might help us to get rid of the serial
> init issue.
> Unfortunately, I dont have a N800 board with me to test it and will require
> your help to do so.
> -----------
> From: Sourav Poddar <sourav.poddar@ti.com>
> Date: Wed, 1 Aug 2012 15:44:12 +0530
> Subject: [RFT/PATCH] serial: omap: Fix N800 serial init issue.
>
>
> This patch might solve the N800 serial init issue.
>
> This patch will also give pointers if there is any mux settings issue
> with N800 OR
> a mismatch between the initial harware state, runtime PM state and
> omap hwmod state.

> I don't have a N800 schematics to check about the mux settings getting used.
>
> The observation on beagle board XM with this patch on different boards
> looks flaky,
> so your feedback on beagle board will also be very helpful.
>
> Cc: Felipe Balbi <balbi@ti.com>
> Signed-off-by: Sourav Poddar <sourav.poddar@ti.com>
> ---
>  drivers/tty/serial/omap-serial.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/tty/serial/omap-serial.c
> b/drivers/tty/serial/omap-serial.c
> index 6ede6fd..3fbc7f7 100644
> --- a/drivers/tty/serial/omap-serial.c
> +++ b/drivers/tty/serial/omap-serial.c
> @@ -1414,6 +1414,7 @@ static int __devinit serial_omap_probe(struct
> platform_device *pdev)
>         INIT_WORK(&up->qos_work, serial_omap_uart_qos_work);
>
>         platform_set_drvdata(pdev, up);
> +       pm_runtime_set_active(&pdev->dev);

NAK.

This will obviously break platforms where the UARTs are not active
before driver loads.

Kevin

>         pm_runtime_enable(&pdev->dev);
>         pm_runtime_use_autosuspend(&pdev->dev);
>         pm_runtime_set_autosuspend_delay(&pdev->dev,

  reply	other threads:[~2012-10-12 16:35 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18 12:40 [RFT/PATCH] serial: omap: prevent resume if device is not suspended Sourav Poddar
2012-09-18 12:40 ` Sourav Poddar
2012-09-18 12:40 ` Sourav Poddar
2012-09-18 14:02 ` Felipe Balbi
2012-09-18 14:02   ` Felipe Balbi
2012-09-18 22:57   ` Paul Walmsley
2012-09-18 22:57     ` Paul Walmsley
2012-09-19 11:52   ` Grazvydas Ignotas
2012-09-19 11:52     ` Grazvydas Ignotas
2012-09-19 11:52     ` Grazvydas Ignotas
2012-09-19 11:59     ` Felipe Balbi
2012-09-19 11:59       ` Felipe Balbi
2012-09-25 12:29       ` Jassi Brar
2012-09-25 12:29         ` Jassi Brar
2012-09-25  8:22 ` Poddar, Sourav
2012-09-25  8:22   ` Poddar, Sourav
2012-09-25  8:30   ` Russell King - ARM Linux
2012-09-25  8:30     ` Russell King - ARM Linux
2012-09-25  8:31     ` Felipe Balbi
2012-09-25  8:31       ` Felipe Balbi
2012-09-25  9:12       ` Russell King - ARM Linux
2012-09-25  9:12         ` Russell King - ARM Linux
2012-09-25  9:11         ` Felipe Balbi
2012-09-25  9:11           ` Felipe Balbi
2012-09-25  9:21           ` Russell King - ARM Linux
2012-09-25  9:21             ` Russell King - ARM Linux
2012-09-25  9:48             ` Felipe Balbi
2012-09-25  9:48               ` Felipe Balbi
2012-09-25 10:29               ` Russell King - ARM Linux
2012-09-25 10:29                 ` Russell King - ARM Linux
2012-09-25 10:37                 ` Felipe Balbi
2012-09-25 10:37                   ` Felipe Balbi
2012-09-25 11:07                   ` Russell King - ARM Linux
2012-09-25 11:07                     ` Russell King - ARM Linux
2012-09-25 11:12                     ` Felipe Balbi
2012-09-25 11:12                       ` Felipe Balbi
2012-09-25 11:32                       ` Russell King - ARM Linux
2012-09-25 11:32                         ` Russell King - ARM Linux
2012-09-25  9:56             ` Poddar, Sourav
2012-09-25  9:56               ` Poddar, Sourav
2012-09-25 10:59               ` Russell King - ARM Linux
2012-09-25 10:59                 ` Russell King - ARM Linux
2012-10-03  0:33               ` Kevin Hilman
2012-10-03  0:33                 ` Kevin Hilman
2012-10-03  0:33                 ` Kevin Hilman
2012-10-11 18:28                 ` Paul Walmsley
2012-10-11 18:28                   ` Paul Walmsley
2012-10-12 16:24                   ` Sourav
2012-10-12 16:24                     ` Sourav
2012-10-12 16:24                     ` Sourav
2012-10-12 16:35                     ` Kevin Hilman [this message]
2012-10-12 16:35                       ` Kevin Hilman
2012-10-12 16:35                       ` Kevin Hilman
2012-10-12 16:42                       ` Russell King - ARM Linux
2012-10-12 16:42                         ` Russell King - ARM Linux
2012-10-12 17:29                         ` Poddar, Sourav
2012-10-12 17:29                           ` Poddar, Sourav
2012-10-12 18:49                           ` Russell King - ARM Linux
2012-10-12 18:49                             ` Russell King - ARM Linux
2012-10-12 17:59                         ` Kevin Hilman
2012-10-12 17:59                           ` Kevin Hilman
2012-10-12 18:54                           ` Russell King - ARM Linux
2012-10-12 18:54                             ` Russell King - ARM Linux
2012-10-12 20:32                             ` Kevin Hilman
2012-10-12 20:32                               ` Kevin Hilman
2012-10-12 21:51                               ` Tony Lindgren
2012-10-12 21:51                                 ` Tony Lindgren
2012-10-15 22:37                                 ` Kevin Hilman
2012-10-15 22:37                                   ` Kevin Hilman
2012-09-25 11:15           ` Russell King - ARM Linux
2012-09-25 11:15             ` Russell King - ARM Linux
2012-09-26 20:30   ` Greg KH
2012-09-26 20:30     ` Greg KH

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=877gqv7imt.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=alan@linux.intel.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=paul@pwsan.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=sourav.poddar@ti.com \
    --cc=tony@atomide.com \
    /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.