From: krzk@kernel.org (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/8] pinctrl: samsung: Add support for pad retention control for Exynos5433 SoCs
Date: Fri, 27 Jan 2017 20:02:03 +0200 [thread overview]
Message-ID: <20170127180203.eacwbyb2noqjpmgw@kozik-lap> (raw)
In-Reply-To: <20170126194811.rori5j5hmclniqig@kozik-lap>
On Thu, Jan 26, 2017 at 09:48:11PM +0200, Krzysztof Kozlowski wrote:
> On Thu, Jan 26, 2017 at 09:33:49AM +0100, Marek Szyprowski wrote:
> > This patch adds support for retention control for Exynos5433 SoCs. Three
> > groups of pins has been defined for retention control: common shared group
> > for ALIVE, CPIF, eSE, FINGER, IMEM, NFC, PERIC, TOUCH pin banks and
> > separate control for FSYS and AUD pin banks, for which PMU retention
> > registers match whole banks.
> >
> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > ---
> > drivers/pinctrl/samsung/pinctrl-exynos.c | 58 +++++++++++++++++++++++++++++
> > include/linux/soc/samsung/exynos-regs-pmu.h | 16 ++++++++
I already have some non-conflicting changes to exynos-regs-pmu.h in my
branch. Now I want to add some more which will create conflicts.
How about splitting the header to separate patch, so I will take it to
my exynos-pmu branch?
Best regards,
Krzysztof
next prev parent reply other threads:[~2017-01-27 18:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170126083401eucas1p20b4794fe46ccf2189bf734f0d8e3c536@eucas1p2.samsung.com>
2017-01-26 8:33 ` [PATCH v2 0/8] Pad retentions support for Exynos5433 Marek Szyprowski
2017-01-26 8:33 ` [PATCH v2 1/8] soc: samsung: pmu: Add dummy support for Exynos5433 SoC Marek Szyprowski
2017-01-26 19:57 ` Krzysztof Kozlowski
2017-01-26 8:33 ` [PATCH v2 2/8] pinctrl: samsung: Ensure that pad retention is disabled on driver init Marek Szyprowski
2017-01-26 8:33 ` [PATCH v2 3/8] pinctrl: samsung: Add support for pad retention control for Exynos5433 SoCs Marek Szyprowski
2017-01-26 19:48 ` Krzysztof Kozlowski
2017-01-27 18:02 ` Krzysztof Kozlowski [this message]
2017-01-30 10:39 ` Marek Szyprowski
2017-01-26 19:57 ` Krzysztof Kozlowski
2017-01-26 8:33 ` [PATCH v2 4/8] arm64: dts: exynos: Add clocks to Exynos5433 LPASS module Marek Szyprowski
2017-01-26 20:08 ` Krzysztof Kozlowski
2017-01-26 8:33 ` [PATCH v2 5/8] mfd: exynos-lpass: Remove pad retention control Marek Szyprowski
2017-01-26 9:36 ` Sylwester Nawrocki
2017-02-01 13:24 ` Rob Herring
2017-02-08 10:56 ` Lee Jones
2017-01-26 8:33 ` [PATCH v2 6/8] mfd: exynos-lpass: Add support for clocks Marek Szyprowski
2017-01-26 20:09 ` Krzysztof Kozlowski
2017-02-01 13:24 ` Rob Herring
2017-02-08 10:57 ` Lee Jones
2017-01-26 8:33 ` [PATCH v2 7/8] mfd: exynos-lpass: Add missing remove() function Marek Szyprowski
2017-01-26 20:11 ` Krzysztof Kozlowski
2017-02-08 10:57 ` Lee Jones
2017-01-26 8:33 ` [PATCH v2 8/8] mfd: exynos-lpass: Add runtime PM support Marek Szyprowski
2017-02-08 10:58 ` Lee Jones
2017-01-26 9:50 ` [PATCH v2 0/8] Pad retentions support for Exynos5433 Linus Walleij
2017-01-26 10:37 ` Marek Szyprowski
2017-01-26 14:32 ` Krzysztof Kozlowski
2017-01-26 15:47 ` Linus Walleij
2017-01-27 19:46 ` Krzysztof Kozlowski
2017-01-30 9:57 ` Marek Szyprowski
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=20170127180203.eacwbyb2noqjpmgw@kozik-lap \
--to=krzk@kernel.org \
--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