public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Nayak, Rajendra" <rnayak@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Raja, Govindraj" <govindraj.raja@ti.com>
Subject: Re: [PATCH 2/2] OMAP: UART: omap_device converions, remove implicit 8520 assumptions
Date: Mon, 01 Mar 2010 11:26:35 -0800	[thread overview]
Message-ID: <87k4tvetck.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB031E4F22E3@dbde02.ent.ti.com> (Rajendra Nayak's message of "Sat\, 30 Jan 2010 12\:05\:50 +0530")

"Nayak, Rajendra" <rnayak@ti.com> writes:

[...]

>> +             /*
>> +              * Need to block sleep long enough for interrupt driven
>> +              * driver to start.  Console driver is in polling mode
>> +              * so device needs to be kept enabled while
>> polling driver
>> +              * is in use.
>> +              */
>> +             uart->timeout = (30 * HZ);
>> +             omap_uart_block_sleep(uart);
>> +             uart->timeout = DEFAULT_TIMEOUT;
>> +
>> +             if ((cpu_is_omap34xx() && uart->padconf) ||
>> +                 (uart->wk_en && uart->wk_mask)) {
>> +                     device_init_wakeup(&od->pdev.dev, true);
>> +                     DEV_CREATE_FILE(&od->pdev.dev,
>> &dev_attr_sleep_timeout);
>> +             }
>> +
>> +#ifdef CONFIG_SERIAL_8250_CONSOLE
>>               /* omap44xx: Never read empty UART fifo
>>                * omap3xxx: Never read empty UART fifo on UARTs
>>                * with IP rev >=0x52
>>                */
>>               if (cpu_is_omap44xx())
>> -                     uart->p->serial_in = serial_in_override;
>> -             else if ((serial_read_reg(uart->p,
>> UART_OMAP_MVER) & 0xFF)
>> +                     p->serial_in = serial_in_override;
>> +             else if ((serial_read_reg(uart, UART_OMAP_MVER) & 0xFF)
>>                               >= UART_OMAP_NO_EMPTY_FIFO_READ_IP_REV)
>> -                     uart->p->serial_in = serial_in_override;
>> +                     p->serial_in = serial_in_override;
>> +#endif
>
> I think this (overriding serial_in) needs to be done sometime before you do a
> omap_device_build() call. Else this has no affect.
>

Thanks Rajendra, you're right, good catch.

Will fix in next spin.

Thanks ,

Kevin

  reply	other threads:[~2010-03-01 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 23:58 [PATCH 0/2] OMAP: UART conversion to omap_device/omap_hwmod Kevin Hilman
2010-01-12 23:58 ` [PATCH 1/2] OMAP3: add omap_hwmods for UART1,2,3 Kevin Hilman
2010-01-12 23:58 ` [PATCH 2/2] OMAP: UART: omap_device converions, remove implicit 8520 assumptions Kevin Hilman
2010-01-30  6:35   ` Nayak, Rajendra
2010-03-01 19:26     ` Kevin Hilman [this message]
2010-01-13  0:04 ` [PATCH 0/2] OMAP: UART conversion to omap_device/omap_hwmod Kevin Hilman

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=87k4tvetck.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=govindraj.raja@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=rnayak@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox