From: Dave Gerlach <d-gerlach@ti.com>
To: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: Paul Walmsley <paul@pwsan.com>, Tony Lindgren <tony@atomide.com>,
	KEERTHY <j-keerthy@ti.com>, Dave Gerlach <d-gerlach@ti.com>
Subject: [PATCH 0/4] Add AM437x RTC
Date: Thu, 5 Mar 2015 07:13:27 -0600	[thread overview]
Message-ID: <1425561211-31003-1-git-send-email-d-gerlach@ti.com> (raw)
Hi,
This series adds support for the rtc on am437x, as previously the hwmod
and dt entries were missing. The am43x-epos-evm requires special treatment
because the RTC gets disabled in hardware with no way to tell through
software so we add a ti,no-init dt flag for the hwmod layer so we can
avoid writing to the SYSCONFIG register and triggering an external abort.
If we use this flag for the am43x-epos-evm we can add the rtc as normal
to am437x-gp-evm. am437x-sk-evm already has the required dt entry in place. 
Regards,
Dave
Dave Gerlach (3):
  ARM: OMAP2+: omap_hwmod: Introduce ti,no-init dt property
  ARM: OMAP2+: AM43xx hwmod: Add RTC hwmod for AM43xx
  ARM: dts: am43x-epos-evm: Add rtc node with ti,no-init property
Keerthy (1):
  ARM: dts: am437x-gp-evm: Enable RTC
 Documentation/devicetree/bindings/arm/omap/omap.txt | 2 ++
 arch/arm/boot/dts/am437x-gp-evm.dts                 | 4 ++++
 arch/arm/boot/dts/am43x-epos-evm.dts                | 4 ++++
 arch/arm/mach-omap2/omap_hwmod.c                    | 7 ++++++-
 arch/arm/mach-omap2/omap_hwmod.h                    | 4 ++++
 arch/arm/mach-omap2/omap_hwmod_43xx_data.c          | 1 +
 6 files changed, 21 insertions(+), 1 deletion(-)
-- 
2.3.0
next             reply	other threads:[~2015-03-05 13:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 13:13 Dave Gerlach [this message]
2015-03-05 13:13 ` [PATCH 1/4] ARM: OMAP2+: omap_hwmod: Introduce ti,no-init dt property Dave Gerlach
2015-03-05 18:16   ` Paul Walmsley
2015-03-05 18:49     ` Tony Lindgren
2015-03-05 19:47       ` Dave Gerlach
2015-03-05 20:17         ` Tony Lindgren
2015-03-06  0:41           ` Tony Lindgren
2015-03-06 17:28             ` Dave Gerlach
     [not found]               ` <54F9E3BF.5010407-l0cyMroinI0@public.gmane.org>
2015-03-06 17:45                 ` Tony Lindgren
2015-03-10 16:12                   ` Dave Gerlach
2015-03-10 17:36                   ` Grygorii Strashko
2015-03-10 17:59                     ` Dave Gerlach
2015-03-11 16:32                       ` Grygorii Strashko
2015-03-12 20:05                         ` Dave Gerlach
2015-03-05 13:13 ` [PATCH 2/4] ARM: OMAP2+: AM43xx hwmod: Add RTC hwmod for AM43xx Dave Gerlach
2015-03-06  4:26   ` Paul Walmsley
2015-03-06 17:30     ` Dave Gerlach
2015-03-06 17:44       ` Paul Walmsley
2015-03-06 17:50         ` Dave Gerlach
2015-03-07  0:37           ` Paul Walmsley
2015-03-05 13:13 ` [PATCH 3/4] ARM: dts: am43x-epos-evm: Add rtc node with ti,no-init property Dave Gerlach
2015-03-05 13:13 ` [PATCH 4/4] ARM: dts: am437x-gp-evm: Enable RTC Dave Gerlach
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=1425561211-31003-1-git-send-email-d-gerlach@ti.com \
    --to=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-keerthy@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).