From: Baoyou Xie <baoyou.xie@linaro.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Jun Nie <jun.nie@linaro.org>, Rob Herring <robh+dt@kernel.org>,
mark.rutland@arm.com, krzk@kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
amit daniel <amitdanielk@gmail.com>,
claudiu.manoil@nxp.com, yangbo.lu@nxp.com,
pankaj.dubey@samsung.com, geert+renesas@glider.be,
laurent.pinchart@ideasonboard.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"xie.baoyou" <xie.baoyou@zte.com.cn>,
chen.chaokai@zte.com.cn, wang.qiang01@zte.com.cn
Subject: Re: [PATCH v6 5/5] soc: zte: pm_domains: Add support for zx296718
Date: Fri, 6 Jan 2017 16:23:41 +0800 [thread overview]
Message-ID: <CA+DQWkwt3oGe1mZppeTkYJptakJYjrahSKdn+kn_FpQGDUgAxA@mail.gmail.com> (raw)
In-Reply-To: <20170105073846.GD4667@x250>
[-- Attachment #1: Type: text/plain, Size: 7727 bytes --]
On 5 January 2017 at 15:38, Shawn Guo <shawnguo@kernel.org> wrote:
> On Wed, Jan 04, 2017 at 07:48:14PM +0800, Baoyou Xie wrote:
> > This patch introduces the power domain driver of zx296718
> > which belongs to zte's zx2967 family.
> >
> > Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>
> > Reviewed-by: Jun Nie <jun.nie@linaro.org>
> > ---
> > drivers/soc/zte/Makefile | 1 +
> > drivers/soc/zte/zx296718_pm_domains.c | 181
> ++++++++++++++++++++++++++++++++++
> > 2 files changed, 182 insertions(+)
> > create mode 100644 drivers/soc/zte/zx296718_pm_domains.c
> >
> > diff --git a/drivers/soc/zte/Makefile b/drivers/soc/zte/Makefile
> > index 8a37f2f..96b7cd4 100644
> > --- a/drivers/soc/zte/Makefile
> > +++ b/drivers/soc/zte/Makefile
> > @@ -2,3 +2,4 @@
> > # ZTE SOC drivers
> > #
> > obj-$(CONFIG_ZX2967_PM_DOMAINS) += zx2967_pm_domains.o
> > +obj-$(CONFIG_ZX2967_PM_DOMAINS) += zx296718_pm_domains.o
> > diff --git a/drivers/soc/zte/zx296718_pm_domains.c
> b/drivers/soc/zte/zx296718_pm_domains.c
> > new file mode 100644
> > index 0000000..52003ee
> > --- /dev/null
> > +++ b/drivers/soc/zte/zx296718_pm_domains.c
> > @@ -0,0 +1,181 @@
> > +/*
> > + * Copyright (C) 2017 ZTE Ltd.
> > + *
> > + * Author: Baoyou Xie <baoyou.xie@linaro.org>
> > + * License terms: GNU General Public License (GPL) version 2
> > + */
>
> Please have a newline between licence declaration and headers to improve
> the readability. Same for zx2967_pm_domains.c.
>
> > +#include <dt-bindings/soc/zte,pm_domains.h>
> > +#include "zx2967_pm_domains.h"
> > +
> > +static u16 zx296718_offsets[REG_ARRAY_SIZE] = {
> > + [REG_CLKEN] = 0x18,
> > + [REG_ISOEN] = 0x1c,
> > + [REG_RSTEN] = 0x20,
> > + [REG_PWREN] = 0x24,
> > + [REG_ACK_SYNC] = 0x28,
> > +};
> > +
> > +enum {
> > + PCU_DM_VOU = 0,
> > + PCU_DM_SAPPU,
> > + PCU_DM_VDE,
> > + PCU_DM_VCE,
> > + PCU_DM_HDE,
> > + PCU_DM_VIU,
> > + PCU_DM_USB20,
> > + PCU_DM_USB21,
> > + PCU_DM_USB30,
> > + PCU_DM_HSIC,
> > + PCU_DM_GMAC,
> > + PCU_DM_TS,
> > +};
>
> I think we can save this enum completely by defining those
> DM_ZX296718_xxx constants in zte,pm_domains.h in the same order of this
> enum (hardware bit position order), so that DM_ZX296718_xxx can directly
> be used as .bit field of struct zx2967_pm_domain.
>
> we should not replace PCU_DM_XX with DM_ZX296718_xxx, their means are
different,
one is the array index, but another is the bit index.
I suggest to keep them strongly.
> #define DM_ZX296718_VOU 0
> #define DM_ZX296718_SAPPU 1
> #define DM_ZX296718_VDE 2 /* g1v6 */
> #define DM_ZX296718_VCE 3 /* h1v6 */
> #define DM_ZX296718_HDE 4 /* g2v2 */
> #define DM_ZX296718_VIU 5
> #define DM_ZX296718_USB20 6
> #define DM_ZX296718_USB21 7
> #define DM_ZX296718_USB30 8
> #define DM_ZX296718_HSIC 9
> #define DM_ZX296718_GMAC 10
> #define DM_ZX296718_TS 11
>
> > +
> > +static struct zx2967_pm_domain vou_domain = {
> > + .dm = {
> > + .name = "vou_domain",
> > + },
> > + .bit = PCU_DM_VOU,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain sappu_domain = {
> > + .dm = {
> > + .name = "sappu_domain",
> > + },
> > + .bit = PCU_DM_SAPPU,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain vde_domain = {
> > + .dm = {
> > + .name = "vde_domain",
> > + },
> > + .bit = PCU_DM_VDE,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain vce_domain = {
> > + .dm = {
> > + .name = "vce_domain",
> > + },
> > + .bit = PCU_DM_VCE,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain hde_domain = {
> > + .dm = {
> > + .name = "hde_domain",
> > + },
> > + .bit = PCU_DM_HDE,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain viu_domain = {
> > + .dm = {
> > + .name = "viu_domain",
> > + },
> > + .bit = PCU_DM_VIU,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain usb20_domain = {
> > + .dm = {
> > + .name = "usb20_domain",
> > + },
> > + .bit = PCU_DM_USB20,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain usb21_domain = {
> > + .dm = {
> > + .name = "usb21_domain",
> > + },
> > + .bit = PCU_DM_USB21,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain usb30_domain = {
> > + .dm = {
> > + .name = "usb30_domain",
> > + },
> > + .bit = PCU_DM_USB30,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain hsic_domain = {
> > + .dm = {
> > + .name = "hsic_domain",
> > + },
> > + .bit = PCU_DM_HSIC,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain gmac_domain = {
> > + .dm = {
> > + .name = "gmac_domain",
> > + },
> > + .bit = PCU_DM_GMAC,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct zx2967_pm_domain ts_domain = {
> > + .dm = {
> > + .name = "ts_domain",
> > + },
> > + .bit = PCU_DM_TS,
> > + .polarity = PWREN,
> > + .reg_offset = zx296718_offsets,
> > +};
> > +
> > +static struct generic_pm_domain *zx296718_pm_domains[] = {
> > + [DM_ZX296718_SAPPU] = &sappu_domain.dm,
> > + [DM_ZX296718_VDE] = &vde_domain.dm,
> > + [DM_ZX296718_VCE] = &vce_domain.dm,
> > + [DM_ZX296718_HDE] = &hde_domain.dm,
> > + [DM_ZX296718_VIU] = &viu_domain.dm,
> > + [DM_ZX296718_USB20] = &usb20_domain.dm,
> > + [DM_ZX296718_USB21] = &usb21_domain.dm,
> > + [DM_ZX296718_USB30] = &usb30_domain.dm,
> > + [DM_ZX296718_HSIC] = &hsic_domain.dm,
> > + [DM_ZX296718_GMAC] = &gmac_domain.dm,
> > + [DM_ZX296718_TS] = &ts_domain.dm,
> > + [DM_ZX296718_VOU] = &vou_domain.dm,
>
> If you update the order of DM_ZX296718_xxx in zte,pm_domains.h, it would
> be nice to update this list accordingly as well.
>
> > +};
> > +
> > +static int zx296718_pd_probe(struct platform_device *pdev)
> > +{
> > + return zx2967_pd_probe(pdev,
> > + zx296718_pm_domains,
> > + ARRAY_SIZE(zx296718_pm_domains));
> > +}
> > +
> > +static const struct of_device_id zx296718_pm_domain_matches[] = {
> > + { .compatible = "zte,zx296718-pcu", },
> > + { },
> > +};
> > +
> > +static struct platform_driver zx296718_pd_driver = {
> > + .driver = {
> > + .name = "zx-powerdomain",
>
> This is a zx296718 specific driver. So zx296718-powerdomain should
> be a better name?
>
> Shawn
>
> > + .owner = THIS_MODULE,
> > + .of_match_table = zx296718_pm_domain_matches,
> > + },
> > + .probe = zx296718_pd_probe,
> > +};
> > +
> > +static int __init zx296718_pd_init(void)
> > +{
> > + return platform_driver_register(&zx296718_pd_driver);
> > +}
> > +subsys_initcall(zx296718_pd_init);
> > --
> > 2.7.4
> >
>
[-- Attachment #2: Type: text/html, Size: 11692 bytes --]
next prev parent reply other threads:[~2017-01-06 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 11:48 [PATCH v6 1/5] dt-bindings: zte: documents zx2967 power domain driver bindings Baoyou Xie
[not found] ` <1483530494-14177-1-git-send-email-baoyou.xie-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-01-04 11:48 ` [PATCH v6 2/5] MAINTAINERS: add zx2967 SoC drivers to ARM ZTE architecture Baoyou Xie
2017-01-05 6:49 ` Shawn Guo
2017-01-04 11:48 ` [PATCH v6 3/5] soc: zte: Add header for PM domains specifiers Baoyou Xie
2017-01-04 11:48 ` [PATCH v6 5/5] soc: zte: pm_domains: Add support for zx296718 Baoyou Xie
2017-01-05 7:38 ` Shawn Guo
2017-01-06 8:23 ` Baoyou Xie [this message]
2017-01-04 11:48 ` [PATCH v6 4/5] soc: zte: pm_domains: Prepare for supporting ARMv8 zx2967 family Baoyou Xie
2017-01-05 7:05 ` Shawn Guo
2017-01-04 14:54 ` [PATCH v6 1/5] dt-bindings: zte: documents zx2967 power domain driver bindings Rob Herring
2017-01-05 6:46 ` Shawn Guo
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=CA+DQWkwt3oGe1mZppeTkYJptakJYjrahSKdn+kn_FpQGDUgAxA@mail.gmail.com \
--to=baoyou.xie@linaro.org \
--cc=amitdanielk@gmail.com \
--cc=arnd@arndb.de \
--cc=chen.chaokai@zte.com.cn \
--cc=claudiu.manoil@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jun.nie@linaro.org \
--cc=krzk@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pankaj.dubey@samsung.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wang.qiang01@zte.com.cn \
--cc=xie.baoyou@zte.com.cn \
--cc=yangbo.lu@nxp.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).