From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
linux-renesas-soc@vger.kernel.org, linux-sh@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v2 0/2] ARM/arm64: renesas: Stop using drivers/sh/
Date: Fri, 20 May 2016 07:50:53 +0000 [thread overview]
Message-ID: <1463730655-16199-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Simon, Magnus,
Now CONFIG_PM and CONFIG_PM_GENERIC_DOMAINS are enabled unconditionally
for Renesas ARM-based SoCs, the legacy clock domain is no longer used on
these SoCs, and we can return drivers/sh/ to SuperH.
Both patches were extracted from series "[PATCH 0/4] Enable PM and
PM_GENERIC_DOMAINS for SoCs with PM Domains", and updated, hence the
v2.
Note that this does break booting R-Car Gen2 boards using pre-v4.3 DTSes
that don't have power-domains properties, as this relied on the legacy
clock domain.
Thanks!
Geert Uytterhoeven (2):
drivers: sh: Stop using the legacy clock domain on ARM
MAINTAINERS: Drop drivers/sh/ for Renesas ARM
MAINTAINERS | 1 -
drivers/Makefile | 1 -
drivers/sh/pm_runtime.c | 9 ---------
3 files changed, 11 deletions(-)
--
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:[~2016-05-20 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 7:50 Geert Uytterhoeven [this message]
2016-05-20 7:50 ` [PATCH v2 1/2] drivers: sh: Stop using the legacy clock domain on ARM Geert Uytterhoeven
2016-05-20 7:50 ` [PATCH v2 2/2] MAINTAINERS: Drop drivers/sh/ for Renesas ARM Geert Uytterhoeven
2016-05-23 0:41 ` [PATCH v2 0/2] ARM/arm64: renesas: Stop using drivers/sh/ Simon Horman
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=1463730655-16199-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=dalias@libc.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ysato@users.sourceforge.jp \
/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).