From: Argus Lin <argus.lin@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Chenglin Xu <chenglin.xu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
wsd_upstream@mediatek.com, henryc.chen@mediatek.com,
flora.fu@mediatek.com, Chen Zhong <chen.zhong@mediatek.com>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
"shailendra . v" <shailendra.v@samsung.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v2 3/5] soc: mediatek: pwrap: add int1_en_all and capability flag
Date: Mon, 12 Feb 2018 09:55:44 +0800 [thread overview]
Message-ID: <1518400544.27225.11.camel@mtkswgap22> (raw)
In-Reply-To: <3f4ce745-32e0-2ae6-1463-af041d608d8c@gmail.com>
[-- Attachment #1.1: Type: text/html, Size: 7804 bytes --]
[-- Attachment #1.2: Type: text/plain, Size: 4120 bytes --]
On Tue, 2018-01-30 at 13:55 +0100, Matthias Brugger wrote:
>
> On 01/29/2018 10:09 AM, argus.lin@mediatek.com wrote:
> > From: Argus Lin <argus.lin@mediatek.com>
> >
> > New pwrap support int1_en flag for starvation and channel
> > request exception. We need to register it for interrupt
> > handler.
> > We also add pwrap capability flag used to declare if we
>
> "We also" wording is nearly always a hint, that this should be done
> in two independent patches.
>
hmm, I see and will modify it.
> > support BRIDGE, RESET, DCM, PRIORITY_SEL and INT1_EN
> > or not.
> >
> > Signed-off-by: Argus Lin <argus.lin@mediatek.com>
> > ---
> > drivers/soc/mediatek/mtk-pmic-wrap.c | 11 ++++++++++-
> > 1 file changed, 10 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/soc/mediatek/mtk-pmic-wrap.c b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > index e9e054a15b7d..9f924d3f8645 100644
> > --- a/drivers/soc/mediatek/mtk-pmic-wrap.c
> > +++ b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > @@ -76,6 +76,13 @@
> > #define PWRAP_SLV_CAP_SECURITY BIT(2)
> > #define HAS_CAP(_c, _x) (((_c) & (_x)) == (_x))
> >
> > +/* Group of bits used for shown pwrap capability */
> > +#define PWRAP_CAP_BRIDGE BIT(0)
> > +#define PWRAP_CAP_RESET BIT(1)
> > +#define PWRAP_CAP_DCM BIT(2)
>
> As you told me the driver will be upstreamed in April, please add this flag when
> you upstream the driver, as this will be in a different kernel version.
>
Dear Matthias:
I add those flags for different wrap HW IP version.
To be forward compatible, I also modify MT2701/MT7622/MT8135/MT8173's
capability.
You can see [PATCH v2 4/5] soc: mediatek: pwrap: add pwrap for mt6797
SoCs for capability definition.
> > +#define PWRAP_CAP_PRIORITY_SEL BIT(3)
> > +#define PWRAP_CAP_INT1_EN BIT(4)
> > +
>
> Add each flag when you add the user of the flag.
I had added new struct for mt6797, caps was included in it.
It was declared at [PATCH v2 4/5] soc: mediatek: pwrap: add pwrap for
mt6797 SoCs.
+static const struct pmic_wrapper_type pwrap_mt6797 = {
+ .regs = mt6797_regs,
+ .type = PWRAP_MT6797,
+ .arb_en_all = 0x01fff,
+ .int_en_all = 0xfffffffd,
+ .int1_en_all = 0x0001ffff,
+ .spi_w = PWRAP_MAN_CMD_SPI_WRITE,
+ .wdt_src = PWRAP_WDT_SRC_MASK_ALL,
+ .caps = PWRAP_CAP_DCM | PWRAP_CAP_PRIORITY_SEL | PWRAP_CAP_INT1_EN,
+ .init_reg_clock = pwrap_common_init_reg_clock,
+ .init_soc_specific = NULL,
+};
+
>
> > /* defines for slave device wrapper registers */
> > enum dew_regs {
> > PWRAP_DEW_BASE,
> > @@ -681,9 +688,11 @@ struct pmic_wrapper_type {
> > enum pwrap_type type;
> > u32 arb_en_all;
> > u32 int_en_all;
> > + u32 int1_en_all;
> > u32 spi_w;
> > u32 wdt_src;
> > - unsigned int has_bridge:1;
> > + /* Flags indicating the capability for the target pwrap */
> > + u32 caps;
>
> NAK, this will not compile. Please make sure that every patch on it's own does
> not break compilation.
>
OK, I will check it.
> Regards,
> Matthias
>
> > int (*init_reg_clock)(struct pmic_wrapper *wrp);
> > int (*init_soc_specific)(struct pmic_wrapper *wrp);
> > };
> > --
> > 2.12.5
> >
> > ************* Email Confidentiality Notice
> > ********************
> > The information contained in this e-mail message (including any
> > attachments) may be confidential, proprietary, privileged, or otherwise
> > exempt from disclosure under applicable laws. It is intended to be
> > conveyed only to the designated recipient(s). Any use, dissemination,
> > distribution, printing, retaining or copying of this e-mail (including its
> > attachments) by unintended recipient(s) is strictly prohibited and may
> > be unlawful. If you are not an intended recipient of this e-mail, or believe
> >
> > that you have received this e-mail in error, please notify the sender
> > immediately (by replying to this e-mail), delete any and all copies of
> > this e-mail (including any attachments) from your system, and do not
> > disclose the content of this e-mail to any other person. Thank
> > you!
> >
>
next prev parent reply other threads:[~2018-02-12 1:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 9:09 [PATCH v2 1/5] dt-bindings: pwrap: mediatek: add pwrap support for MT6797 argus.lin
2018-01-29 9:09 ` [PATCH v2 2/5] arm64: dts: mt6797: add pwrap support for mt6797 argus.lin
2018-01-30 12:57 ` Matthias Brugger
2018-02-11 8:55 ` Argus Lin
2018-01-29 9:09 ` [PATCH v2 3/5] soc: mediatek: pwrap: add int1_en_all and capability flag argus.lin
2018-01-30 12:55 ` Matthias Brugger
2018-02-12 1:55 ` Argus Lin [this message]
2018-01-29 9:09 ` [PATCH v2 4/5] soc: mediatek: pwrap: add pwrap for mt6797 SoCs argus.lin
2018-01-29 9:09 ` [PATCH v2 5/5] soc: mediatek: pwrap: add mt6351 " argus.lin
2018-01-30 12:58 ` [PATCH v2 1/5] dt-bindings: pwrap: mediatek: add pwrap support for MT6797 Matthias Brugger
2018-02-11 8:52 ` Argus Lin (林書慶)
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=1518400544.27225.11.camel@mtkswgap22 \
--to=argus.lin@mediatek.com \
--cc=catalin.marinas@arm.com \
--cc=chen.zhong@mediatek.com \
--cc=chenglin.xu@mediatek.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=devicetree@vger.kernel.org \
--cc=flora.fu@mediatek.com \
--cc=henryc.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=shailendra.v@samsung.com \
--cc=will.deacon@arm.com \
--cc=wsd_upstream@mediatek.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).