public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Govindraj.R" <govindraj.raja@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv2 2/3] OMAP UART: Add platform data for omap-serial driver.
Date: Wed, 28 Oct 2009 09:35:22 -0700	[thread overview]
Message-ID: <87ljiv5ved.fsf@deeprootsystems.com> (raw)
In-Reply-To: <36298.192.168.10.88.1256714022.squirrel@dbdmail.itg.ti.com> (Govindraj R.'s message of "Wed\, 28 Oct 2009 12\:43\:42 +0530 \(IST\)")

"Govindraj.R" <govindraj.raja@ti.com> writes:

> From 0f017ffac2990876331a2378e7845d91b2e0088c Mon Sep 17 00:00:00 2001
> From: Govindraj R <govindraj.raja@ti.com>
> Date: Wed, 28 Oct 2009 12:23:02 +0530
> Subject: [PATCHv2 2/3] OMAP UART: Add platform data for omap-serial driver.
>
> This patch adds platform data support for omap-serial driver.
>
> Signed-off-by: Govindraj R <govindraj.raja@ti.com>
> ---
>  arch/arm/mach-omap2/serial.c |  166 ++++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 166 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/serial.c b/arch/arm/mach-omap2/serial.c
> index dabc089..aa3a282 100644
> --- a/arch/arm/mach-omap2/serial.c
> +++ b/arch/arm/mach-omap2/serial.c
> @@ -13,6 +13,9 @@
>   * Copyright (C) 2009 Texas Instruments
>   * Added OMAP4 support - Santosh Shilimkar <santosh.shilimkar@ti.com
>   *
> + * Copyright (C) 2009 Texas Instruments
> + * Added support for Omap-Serial driver - Govindraj R <govindraj.raja@ti.com>
> + *
>   * This file is subject to the terms and conditions of the GNU General Public
>   * License. See the file "COPYING" in the main directory of this archive
>   * for more details.
> @@ -29,6 +32,10 @@
>  #include <plat/clock.h>
>  #include <plat/control.h>
>
> +#ifdef CONFIG_SERIAL_OMAP
> +#include <plat/dma.h>
> +#include <plat/omap-serial.h>
> +#endif
>  #include "prm.h"
>  #include "pm.h"
>  #include "prm-regbits-34xx.h"
> @@ -37,6 +44,7 @@
>
>  #define DEFAULT_TIMEOUT (5 * HZ)
>
> +#ifdef CONFIG_SERIAL_8250
>  struct omap_uart_state {
>  	int num;
>  	int can_sleep;
> @@ -654,3 +662,161 @@ void __init omap_serial_init(void)
>  		}
>  	}
>  }
> +#endif
> +
> +#ifdef CONFIG_SERIAL_OMAP

Can you do this without the #ifdefs?

Instead, we should drop the 8250 specifics from omap_uart_state.

At first glance, the plat_serial8250_port pointer is passed around
mainly so it can be passed to serial_read|write_reg().  If you changed
that function to take an omap_uart_state instead, and add the base and
regshift values to omap_uart_state you could get rid of the 8250
pointer from omap_uart_state.

Looks like omap_uart_state should also grow an irq field so
omap_uart_idle_init() could work for both drivers.

> +static struct uart_port_info uart1_port_info = {
> +		.dma_enabled	= 0,
> +		.uartclk	= OMAP24XX_BASE_BAUD * 16
> +};
> +
> +static struct uart_port_info uart2_port_info = {
> +		.dma_enabled	= 1,
> +		.uartclk	= OMAP24XX_BASE_BAUD * 16
> +};
> +
> +static struct uart_port_info uart3_port_info = {
> +		.dma_enabled	= 0,
> +		.uartclk	= OMAP24XX_BASE_BAUD * 16
> +};
> +
> +static struct resource omap2_uart1_resources[] = {
> +	{
> +		.start          = OMAP_UART1_BASE,
> +		.end            = OMAP_UART1_BASE + 0x3ff,
> +		.flags          = IORESOURCE_MEM,
> +	}, {
> +		/* UART1 IRQ - 72*/
> +		.start          = INT_24XX_UART1_IRQ,
> +		.flags          = IORESOURCE_IRQ,
> +	}, {
> +		/* UART1 TX DMA CHANNEL -S_DMA_48- */
> +		.start		= OMAP24XX_DMA_UART1_TX,
> +		.flags		= IORESOURCE_DMA,
> +	}, {
> +		/* UART1 RX DMA CHANNEL -S_DMA_49- */
> +		.start		= OMAP24XX_DMA_UART1_RX,
> +		.flags		= IORESOURCE_DMA,
> +	}
> +};
> +
> +static struct resource omap2_uart2_resources[] = {
> +	{
> +		.start          = OMAP_UART2_BASE,
> +		.end            = OMAP_UART2_BASE + 0x3ff,
> +		.flags          = IORESOURCE_MEM,
> +	}, {
> +		/* UART2 IRQ - 73*/
> +		.start          = INT_24XX_UART2_IRQ,
> +		.flags          = IORESOURCE_IRQ,
> +	}, {
> +		/* UART2 TX DMA CHANNEL -S_DMA_50- */
> +		.start		= OMAP24XX_DMA_UART2_TX,
> +		.flags		= IORESOURCE_DMA,
> +	}, {
> +		/* UART2 RX DMA CHANNEL -S_DMA_51- */
> +		.start		= OMAP24XX_DMA_UART2_RX,
> +		.flags		= IORESOURCE_DMA,
> +	}
> +};
> +
> +static struct resource omap2_uart3_resources[] = {
> +	{
> +		.start          = OMAP_UART3_BASE,
> +		.end            = OMAP_UART3_BASE + 0x3ff,
> +		.flags          = IORESOURCE_MEM,
> +	}, {
> +		/* UART3 IRQ - 74*/
> +		.start          = INT_24XX_UART3_IRQ,
> +		.flags          = IORESOURCE_IRQ,
> +	}, {
> +		/* UART3 TX DMA CHANNEL -S_DMA_52- */
> +		.start		= OMAP24XX_DMA_UART3_TX,
> +		.flags		= IORESOURCE_DMA,
> +	}, {
> +		/* UART3 RX DMA CHANNEL -S_DMA_53- */
> +		.start		= OMAP24XX_DMA_UART3_RX,
> +		.flags		= IORESOURCE_DMA,
> +	}
> +};
> +
> +/* OMAP UART platform structure */
> +static struct platform_device uart1_device = {
> +	.name			= "omap-uart",
> +	.id			= 1,
> +	.num_resources		= ARRAY_SIZE(omap2_uart1_resources),
> +	.resource		= omap2_uart1_resources,
> +	.dev			= {
> +		.platform_data  = &uart1_port_info
> +	},
> +};
> +static struct platform_device uart2_device = {
> +	.name			= "omap-uart",
> +	.id			= 2,
> +	.num_resources		= ARRAY_SIZE(omap2_uart2_resources),
> +	.resource		= omap2_uart2_resources,
> +	.dev			= {
> +		.platform_data  = &uart2_port_info,
> +	},
> +};
> +static struct platform_device uart3_device = {
> +	.name			= "omap-uart",
> +	.id			= 3,
> +	.num_resources		= ARRAY_SIZE(omap2_uart3_resources),
> +	.resource		= omap2_uart3_resources,
> +	.dev			= {
> +		.platform_data  = &uart3_port_info,
> +	},
> +};
> +
> +static struct platform_device *uart_devices[] = {
> +	&uart1_device,
> +	&uart2_device,
> +	&uart3_device,
> +};

NAK.  Now that we have omap_device upstream, we need to use
omap_device for the creation of these platform devices.  omap_device
building will use a UART hwmod to build the resources and
platform_devices automatically.

> +void omap_serial_hsuart_wakeup_source_init(int num)
> +{
> +	struct omap_hsuart_state *uart = &omap_hsuart[num];
> +
> +	if (cpu_is_omap34xx()) {
> +		u32 mod = (uart->num == 2) ? OMAP3430_PER_MOD : CORE_MOD;
> +		u32 wk_mask = 0;
> +		u32 padconf = 0;
> +
> +		uart->wk_en = OMAP34XX_PRM_REGADDR(mod, PM_WKEN1);
> +		uart->wk_st = OMAP34XX_PRM_REGADDR(mod, PM_WKST1);
> +		switch (uart->num) {
> +		case 0:
> +			wk_mask = OMAP3430_ST_UART1_MASK;
> +			padconf = 0x182;
> +			break;
> +		case 1:
> +			wk_mask = OMAP3430_ST_UART2_MASK;
> +			padconf = 0x17a;
> +			break;
> +		case 2:
> +			wk_mask = OMAP3430_ST_UART3_MASK;
> +			padconf = 0x19e;
> +			break;
> +		}
> +		uart->wk_mask = wk_mask;
> +		uart->padconf = padconf;

??? this looks like an exact copy of what's in omap_uart_idle_init()

> +	} else {
> +		uart->wk_en = 0;
> +		uart->wk_st = 0;
> +		uart->wk_mask = 0;
> +		uart->padconf = 0;
> +	}
> +}
> +
> +void __init omap_serial_init(void)
> +{
> +	int ret = 0, i;
> +	for (i = 0; i < ARRAY_SIZE(uart_devices); i++)
> +		omap_hsuart_idle_init(i);
> +
> +	ret = platform_add_devices(uart_devices, ARRAY_SIZE(uart_devices));
> +}
> +#endif /* CONFIG_SERIAL_OMAP */
> -- 
> 1.5.5

Kevin

  reply	other threads:[~2009-10-28 16:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28  7:13 [PATCHv2 2/3] OMAP UART: Add platform data for omap-serial driver Govindraj.R
2009-10-28 16:35 ` Kevin Hilman [this message]
2009-10-28 17:49   ` Kevin Hilman
2009-10-29 14:11 ` Kauppi Ari (EXT-Ixonos/Oulu)
2009-11-13  6:54 ` [PATCHv3 " Govindraj.R

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