public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: charu@ti.com
Cc: linux-omap@vger.kernel.org, tony@atomide.com,
	david-b@pacbell.net, sameo@linux.intel.com,
	p_gortmaker@yahoo.com
Subject: Re: [RFC][PATCH 0/3] RTC platform data structure defined
Date: Sat, 22 Aug 2009 19:27:31 +0300	[thread overview]
Message-ID: <87fxbjvmoc.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1250091912-5334-1-git-send-email-charu@ti.com> (charu@ti.com's message of "Wed\, 12 Aug 2009 21\:15\:12 +0530")

charu@ti.com writes:

> This series contains patches which
>         1. define TWL4030 rtc platform data which has msecure gpio line info
>         2. initialise msecure gpio line from rtc driver
>         3. twl core file passes rtc platform data from board file to rtc driver
>         4. Board files handle mux configuration of msecure gpio line
>
> This series applies on top of linux-2.6.31-rc5.
>
> CharuLatha (4):
>
>         [PATCH 0/3] RTC platform data structure defined

Normally, PATCH 0/n is a summary of the other patches, and does not
include a patch itself.

I recommend using 'git format-patch' which will take care of the
formatting and the numbering for you.

>         [PATCH 1/3] RTC periodic interrupts enabling and msecure init
>         [PATCH 2/3] handling rtc platform data
>         [PATCH 3/3] board files do msecure line mux configuration
>
> Structure "twl4030_rtc_platform_data" is defined with msecure_gpio in it. 
> This structure would be initialised in board file. 
> RTC msecure line initialization happens in RTC driver.
> The same structure can be used for any future enhancements in RTC.
>
>
> Signed-off-by: Charulatha V <charu@ti.com>
> ---
>  include/linux/i2c/twl4030.h |    8 ++++++++
>  1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/i2c/twl4030.h b/include/linux/i2c/twl4030.h
> index 15edfaa..6ae582b 100644
> --- a/include/linux/i2c/twl4030.h
> +++ b/include/linux/i2c/twl4030.h
> @@ -341,6 +341,13 @@ struct twl4030_gpio_platform_data {
>  				unsigned gpio, unsigned ngpio);
>  };
>  
> +struct twl4030_rtc_platform_data {
> +	int 		msecure_gpio;
> +	/* More structures/elements can be added
> +	 * for future Triton RTC driver enhancements
> +	 */

very true, but does not need to be documented.

> +};
> +
>  struct twl4030_madc_platform_data {
>  	int		irq_line;
>  };
> @@ -395,6 +402,7 @@ struct twl4030_platform_data {
>  	unsigned				irq_base, irq_end;
>  	struct twl4030_bci_platform_data	*bci;
>  	struct twl4030_gpio_platform_data	*gpio;
> +	struct twl4030_rtc_platform_data	*rtc;
>  	struct twl4030_madc_platform_data	*madc;
>  	struct twl4030_keypad_data		*keypad;
>  	struct twl4030_usb_data			*usb;
> -- 
> 1.6.0.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Kevin

  reply	other threads:[~2009-08-22 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12 15:45 [RFC][PATCH 0/3] RTC platform data structure defined charu
2009-08-22 16:27 ` Kevin Hilman [this message]
     [not found]   ` <E0D41E29EB0DAC4E9F3FF173962E9E94025349A10B@dbde02.ent.ti.com>
2009-08-24  6:07     ` Varadarajan, Charu Latha

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=87fxbjvmoc.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=charu@ti.com \
    --cc=david-b@pacbell.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=p_gortmaker@yahoo.com \
    --cc=sameo@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox