From: Gururaja Hebbar <gururaja.hebbar-l0cyMroinI0@public.gmane.org>
Cc: mark.rutland-5wv7dgnIgG8@public.gmane.org,
a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org,
rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org,
grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v3 0/2] rtc: omap: update AM335x rtc ip revision
Date: Fri, 16 Aug 2013 17:44:54 +0530 [thread overview]
Message-ID: <520E17BE.2050008@ti.com> (raw)
In-Reply-To: <1376653017-21935-1-git-send-email-gururaja.hebbar-l0cyMroinI0@public.gmane.org>
Hi All,
Kindly ignore this series. there is mistake/typo because of which it
will not directly apply. I will resend the patch-set.
sorry for the trouble.
regards
Gururaja
On 8/16/2013 5:06 PM, Hebbar, Gururaja wrote:
> The syntax of compatible property in DT is to mention the Most specific
> match to most generic match.
>
> Since AM335x is the platform with latest IP revision, add it 1st in
> the device id table.
>
> This way, we can add new matching compatible as 1st and maintain old
> compatible string for backwards compatibility.
>
> ex:
> compatible = "ti,am3352-rtc", "ti,da830-rtc";
>
> Also, update am335x .dtsi file (am33xx.dtsi) as above.
>
> Note:
> This is a part of previously submitted patch-set [1]. Out of 4 patches,
> 3 was accepted and 1 got an acceptable NAK. Hence resubmitting only the
> rejected + updated changes.
>
> Changes in V3:
> - As per Mark Rutland's suggestion [2], maintain old compatible
> string and add the new matching string as the 1st compatible.
>
> Changes in V2:
> - Coding style corrections (remove extra space, use lower case
> for hex numbers
> - use prefix ARM: for commit subject keeping with arch/arm
> convention)
> - use "[AM/am]3352" instead of "[AM/am]335x" to keep the all
> usages in sync.
> - Use index defined for struct members so they remain in sync
> - Add new compatible to existing one so that when driver
> supports enhanced features of hardware, they are available
> to the user else the basic functionality still works
>
> [2]
> https://lkml.org/lkml/2013/7/3/74
> [1]
> https://lkml.org/lkml/2013/8/1/442
>
> Hebbar Gururaja (1):
> ARM: dts: AM33XX: update rtc node compatibility
>
> Hebbar, Gururaja (1):
> rtc: omap: update of_device_id to reflect latest ip revisions
>
> arch/arm/boot/dts/am33xx.dtsi | 2 +-
> drivers/rtc/rtc-omap.c | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: gururaja.hebbar@ti.com (Gururaja Hebbar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] rtc: omap: update AM335x rtc ip revision
Date: Fri, 16 Aug 2013 17:44:54 +0530 [thread overview]
Message-ID: <520E17BE.2050008@ti.com> (raw)
In-Reply-To: <1376653017-21935-1-git-send-email-gururaja.hebbar@ti.com>
Hi All,
Kindly ignore this series. there is mistake/typo because of which it
will not directly apply. I will resend the patch-set.
sorry for the trouble.
regards
Gururaja
On 8/16/2013 5:06 PM, Hebbar, Gururaja wrote:
> The syntax of compatible property in DT is to mention the Most specific
> match to most generic match.
>
> Since AM335x is the platform with latest IP revision, add it 1st in
> the device id table.
>
> This way, we can add new matching compatible as 1st and maintain old
> compatible string for backwards compatibility.
>
> ex:
> compatible = "ti,am3352-rtc", "ti,da830-rtc";
>
> Also, update am335x .dtsi file (am33xx.dtsi) as above.
>
> Note:
> This is a part of previously submitted patch-set [1]. Out of 4 patches,
> 3 was accepted and 1 got an acceptable NAK. Hence resubmitting only the
> rejected + updated changes.
>
> Changes in V3:
> - As per Mark Rutland's suggestion [2], maintain old compatible
> string and add the new matching string as the 1st compatible.
>
> Changes in V2:
> - Coding style corrections (remove extra space, use lower case
> for hex numbers
> - use prefix ARM: for commit subject keeping with arch/arm
> convention)
> - use "[AM/am]3352" instead of "[AM/am]335x" to keep the all
> usages in sync.
> - Use index defined for struct members so they remain in sync
> - Add new compatible to existing one so that when driver
> supports enhanced features of hardware, they are available
> to the user else the basic functionality still works
>
> [2]
> https://lkml.org/lkml/2013/7/3/74
> [1]
> https://lkml.org/lkml/2013/8/1/442
>
> Hebbar Gururaja (1):
> ARM: dts: AM33XX: update rtc node compatibility
>
> Hebbar, Gururaja (1):
> rtc: omap: update of_device_id to reflect latest ip revisions
>
> arch/arm/boot/dts/am33xx.dtsi | 2 +-
> drivers/rtc/rtc-omap.c | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: Gururaja Hebbar <gururaja.hebbar@ti.com>
To: unlisted-recipients:; (no To-header on input)
Cc: <akpm@linux-foundation.org>, <khilman@linaro.org>,
<tony@atomide.com>, <bcousson@baylibre.com>,
<rob.herring@calxeda.com>, <mark.rutland@arm.com>,
<a.zummo@towertech.it>, <rob@landley.net>,
<grant.likely@linaro.org>, <rtc-linux@googlegroups.com>,
<linux-omap@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<davinci-linux-open-source@linux.davincidsp.com>,
<sudhakar.raj@ti.com>
Subject: Re: [PATCH v3 0/2] rtc: omap: update AM335x rtc ip revision
Date: Fri, 16 Aug 2013 17:44:54 +0530 [thread overview]
Message-ID: <520E17BE.2050008@ti.com> (raw)
In-Reply-To: <1376653017-21935-1-git-send-email-gururaja.hebbar@ti.com>
Hi All,
Kindly ignore this series. there is mistake/typo because of which it
will not directly apply. I will resend the patch-set.
sorry for the trouble.
regards
Gururaja
On 8/16/2013 5:06 PM, Hebbar, Gururaja wrote:
> The syntax of compatible property in DT is to mention the Most specific
> match to most generic match.
>
> Since AM335x is the platform with latest IP revision, add it 1st in
> the device id table.
>
> This way, we can add new matching compatible as 1st and maintain old
> compatible string for backwards compatibility.
>
> ex:
> compatible = "ti,am3352-rtc", "ti,da830-rtc";
>
> Also, update am335x .dtsi file (am33xx.dtsi) as above.
>
> Note:
> This is a part of previously submitted patch-set [1]. Out of 4 patches,
> 3 was accepted and 1 got an acceptable NAK. Hence resubmitting only the
> rejected + updated changes.
>
> Changes in V3:
> - As per Mark Rutland's suggestion [2], maintain old compatible
> string and add the new matching string as the 1st compatible.
>
> Changes in V2:
> - Coding style corrections (remove extra space, use lower case
> for hex numbers
> - use prefix ARM: for commit subject keeping with arch/arm
> convention)
> - use "[AM/am]3352" instead of "[AM/am]335x" to keep the all
> usages in sync.
> - Use index defined for struct members so they remain in sync
> - Add new compatible to existing one so that when driver
> supports enhanced features of hardware, they are available
> to the user else the basic functionality still works
>
> [2]
> https://lkml.org/lkml/2013/7/3/74
> [1]
> https://lkml.org/lkml/2013/8/1/442
>
> Hebbar Gururaja (1):
> ARM: dts: AM33XX: update rtc node compatibility
>
> Hebbar, Gururaja (1):
> rtc: omap: update of_device_id to reflect latest ip revisions
>
> arch/arm/boot/dts/am33xx.dtsi | 2 +-
> drivers/rtc/rtc-omap.c | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2013-08-16 12:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 11:36 [PATCH v3 0/2] rtc: omap: update AM335x rtc ip revision Hebbar, Gururaja
2013-08-16 11:36 ` Hebbar, Gururaja
2013-08-16 11:36 ` Hebbar, Gururaja
[not found] ` <1376653017-21935-1-git-send-email-gururaja.hebbar-l0cyMroinI0@public.gmane.org>
2013-08-16 11:36 ` [PATCH v3 1/2] rtc: omap: update of_device_id to reflect latest ip revisions Hebbar, Gururaja
2013-08-16 11:36 ` Hebbar, Gururaja
2013-08-16 11:36 ` Hebbar, Gururaja
2013-08-16 14:15 ` Benoit Cousson
2013-08-16 14:15 ` Benoit Cousson
[not found] ` <520E341D.4080206-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2013-08-16 15:41 ` Sekhar Nori
2013-08-16 15:41 ` Sekhar Nori
2013-08-16 15:41 ` Sekhar Nori
2013-08-16 16:33 ` Benoit Cousson
2013-08-16 16:33 ` Benoit Cousson
2013-08-16 16:33 ` Benoit Cousson
[not found] ` <520E5444.1000700-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2013-08-23 8:50 ` Sekhar Nori
2013-08-23 8:50 ` Sekhar Nori
2013-08-23 8:50 ` Sekhar Nori
2013-08-23 15:10 ` Benoit Cousson
2013-08-23 15:10 ` Benoit Cousson
2013-08-23 15:10 ` Benoit Cousson
[not found] ` <52177B6C.2080406-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2013-08-23 16:17 ` Sekhar Nori
2013-08-23 16:17 ` Sekhar Nori
2013-08-23 16:17 ` Sekhar Nori
2013-08-16 17:20 ` Mark Rutland
2013-08-16 17:20 ` Mark Rutland
2013-08-16 18:12 ` Benoit Cousson
2013-08-16 18:12 ` Benoit Cousson
2013-08-19 14:45 ` Mark Rutland
2013-08-19 14:45 ` Mark Rutland
2013-08-16 11:36 ` [PATCH v3 2/2] ARM: dts: AM33XX: update rtc node compatibility Hebbar, Gururaja
2013-08-16 11:36 ` Hebbar, Gururaja
2013-08-16 11:36 ` Hebbar, Gururaja
2013-08-16 12:14 ` Gururaja Hebbar [this message]
2013-08-16 12:14 ` [PATCH v3 0/2] rtc: omap: update AM335x rtc ip revision Gururaja Hebbar
2013-08-16 12:14 ` Gururaja Hebbar
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=520E17BE.2050008@ti.com \
--to=gururaja.hebbar-l0cymroini0@public.gmane.org \
--cc=a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=bcousson-rdvid1DuHRBWk0Htik3J/w@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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.