From: Geert Uytterhoeven <geert+renesas@glider.be>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: shmobile: sh73a0 legacy: Add missing INTCA0 clock
Date: Wed, 19 Nov 2014 15:26:58 +0000 [thread overview]
Message-ID: <1416410820-30020-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Simon, Magnus,
This patch series adds the missing INTCA0 clock on sh73a0 SoCs, for both
legacy/reference and multi-platform builds.
The INTCA0 clock drives the irqpin controller modules.
Before, it was assumed enabled by the bootloader or reset state.
By making it available to the driver, we make sure it gets enabled when
needed, and allow it to be managed by system or runtime PM.
The first patch can be applied now.
The second patch depends on the series "[PATCH v5 0/6] sh73a0 common clock
framework implementation".
Thanks!
Geert Uytterhoeven (2):
ARM: shmobile: sh73a0 legacy: Add missing INTCA0 clock for irqpin
module
ARM: shmobile: sh73a0 dtsi: Add missing INTCA0 clock for irqpin module
arch/arm/boot/dts/sh73a0.dtsi | 15 +++++++++++++++
arch/arm/mach-shmobile/clock-sh73a0.c | 10 ++++++++++
include/dt-bindings/clock/sh73a0-clock.h | 3 +++
3 files changed, 28 insertions(+)
--
1.9.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2014-11-19 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 15:26 Geert Uytterhoeven [this message]
2014-11-19 15:26 ` [PATCH 1/2] ARM: shmobile: sh73a0 legacy/reference: Add missing INTCA0 clock for irqpin module Geert Uytterhoeven
2014-11-25 2:44 ` Simon Horman
2014-11-25 9:31 ` Geert Uytterhoeven
2014-11-25 10:16 ` Geert Uytterhoeven
2014-11-26 1:31 ` Simon Horman
2014-11-28 0:44 ` Simon Horman
2014-11-19 15:27 ` [PATCH 2/2] ARM: shmobile: sh73a0 dtsi: " Geert Uytterhoeven
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=1416410820-30020-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).