From: Matthias Brugger <matthias.bgg@gmail.com>
To: Argus Lin <argus.lin@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>
Cc: devicetree@vger.kernel.org, wsd_upstream@mediatek.com,
Chenglin Xu <chenglin.xu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
linux-kernel@vger.kernel.org, henryc.chen@mediatek.com,
flora.fu@mediatek.com,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
linux-mediatek@lists.infradead.org,
Chen Zhong <chen.zhong@mediatek.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/3] soc: mediatek: pwrap: add pwrap driver for MT6779 SoCs
Date: Mon, 17 Feb 2020 11:07:59 +0100 [thread overview]
Message-ID: <60a52486-3669-4a3e-c6b1-0eac7a8dceb3@gmail.com> (raw)
In-Reply-To: <1581833843-4485-1-git-send-email-argus.lin@mediatek.com>
On 16/02/2020 07:17, Argus Lin wrote:
> changes since v1:
> 1. Modify pwrap_mt6779 arb_en_all, int_en_all, and wdt_src value
> when initialization.
> 2. Remove PWRAP_WDT_UNIT, PWRAP_WDT_UNIT, PWRAP_INT_EN, and
> PWRAP_CAP_INT1_EN registered value check, we will initialize them
> again at kernel level.
>
> Here's version 1 of the patch series, include 3 patches:
> 1. Add compatible for MT6779 pwrap
> 2. Add pwrap driver for MT6779 SoCs. Keep PWRAP_HIPRIO_ARB_EN,
> PWRAP_WDT_UNIT, and PWRAP_WDT_SRC_EN value if it has initialized.
> When we enable interrupt flag, read current value then do logical
> OR opersion with wrp->master->int_en_all.
> 3. Add MT6359 support for MT6779 SoCs.
>
> Argus Lin (3):
> dt-bindings: pwrap: mediatek: add pwrap support for MT6779
> soc: mediatek: pwrap: add pwrap driver for MT6779 SoCs
> soc: mediatek: pwrap: add support for MT6359 PMIC
>
Applied all three to v5.6-next/soc
Thanks a lot!
Matthias
> .../devicetree/bindings/soc/mediatek/pwrap.txt | 1 +
> drivers/soc/mediatek/mtk-pmic-wrap.c | 128 +++++++++++++++++++++
> 2 files changed, 129 insertions(+)
>
> --
> 1.8.1.1.dirty
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-17 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 6:17 [PATCH v2 0/3] soc: mediatek: pwrap: add pwrap driver for MT6779 SoCs Argus Lin
2020-02-16 6:17 ` [PATCH v2 1/3] dt-bindings: pwrap: mediatek: add pwrap support for MT6779 Argus Lin
2020-02-16 6:17 ` [PATCH v2 2/3] soc: mediatek: pwrap: add pwrap driver for MT6779 SoCs Argus Lin
2020-02-16 6:17 ` [PATCH v2 3/3] soc: mediatek: pwrap: add support for MT6359 PMIC Argus Lin
2020-02-17 10:07 ` Matthias Brugger [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-16 6:14 [PATCH v2 0/3] soc: mediatek: pwrap: add pwrap driver for MT6779 SoCs 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=60a52486-3669-4a3e-c6b1-0eac7a8dceb3@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=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=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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).