From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kishon Vijay Abraham I <kishon@ti.com>,
Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Lee Jones <lee.jones@linaro.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: [PATCH v2 0/4] phy/mfd/soc: exynos: Header cleanup
Date: Sat, 11 Mar 2017 20:25:30 +0200 [thread overview]
Message-ID: <20170311182534.13345-1-krzk@kernel.org> (raw)
Suggested by Marek, continuation of cleanup of PMU register defines
in headers.
Let's keep all of them in include/linux/soc/samsung/exynos-regs-pmu.h.
Merging strategy: probably through phy tree (in that case they have
samsung-soc's ack).
I can also take it through samsung-soc - please let me know.
Changes since v1:
=================
1. Rebase - dependencies should be already in.
2. Add Lee's acks.
Best regards,
Krzysztof
Krzysztof Kozlowski (4):
phy: exynos4: Remove duplicated defines of PHY register defines
phy: exynos5: Remove duplicated defines of PHY register defines
phy: exynos-mipi-video: Use consistent method to address phy registers
phy: exynos: Use one define for enable bit
drivers/phy/phy-exynos-dp-video.c | 6 +--
drivers/phy/phy-exynos-mipi-video.c | 71 ++++++++++++++---------------
drivers/phy/phy-exynos5-usbdrd.c | 6 +--
include/linux/mfd/syscon/exynos4-pmu.h | 21 ---------
include/linux/mfd/syscon/exynos5-pmu.h | 52 ---------------------
include/linux/soc/samsung/exynos-regs-pmu.h | 16 ++++++-
6 files changed, 56 insertions(+), 116 deletions(-)
delete mode 100644 include/linux/mfd/syscon/exynos4-pmu.h
delete mode 100644 include/linux/mfd/syscon/exynos5-pmu.h
--
2.9.3
next reply other threads:[~2017-03-11 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 18:25 Krzysztof Kozlowski [this message]
2017-03-11 18:25 ` [PATCH v2 1/4] phy: exynos4: Remove duplicated defines of PHY register defines Krzysztof Kozlowski
[not found] ` <CGME20170314143354epcas5p264689de8b8889e4e06a145d89b376581@epcas5p2.samsung.com>
2017-03-14 14:33 ` Bartlomiej Zolnierkiewicz
2017-03-11 18:25 ` [PATCH v2 2/4] phy: exynos5: " Krzysztof Kozlowski
[not found] ` <CGME20170314143705epcas5p42e226d072b9ec705bb0dca981923f313@epcas5p4.samsung.com>
2017-03-14 14:37 ` Bartlomiej Zolnierkiewicz
2017-03-14 14:56 ` Krzysztof Kozlowski
2017-03-11 18:25 ` [PATCH v2 3/4] phy: exynos-mipi-video: Use consistent method to address phy registers Krzysztof Kozlowski
[not found] ` <CGME20170314143728epcas5p37af94136c79bb91b7917036117d29463@epcas5p3.samsung.com>
2017-03-14 14:37 ` Bartlomiej Zolnierkiewicz
2017-03-11 18:25 ` [PATCH v2 4/4] phy: exynos: Use one define for enable bit Krzysztof Kozlowski
[not found] ` <CGME20170314144612epcas5p43922a86ea62ef32bc8e32dc27f5164ab@epcas5p4.samsung.com>
2017-03-14 14:46 ` Bartlomiej Zolnierkiewicz
2017-03-14 14:55 ` Krzysztof Kozlowski
[not found] ` <CGME20170314155351epcas5p210791391569477d6b115bb922ab068ed@epcas5p2.samsung.com>
2017-03-14 15:53 ` Bartlomiej Zolnierkiewicz
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=20170311182534.13345-1-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=javier@osg.samsung.com \
--cc=kgene@kernel.org \
--cc=kishon@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@samsung.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).