From: Chen Zhong <chen.zhong@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Eddie Huang <eddie.huang@mediatek.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Jaechul Lee <jcsing.lee@samsung.com>,
Jonathan Cameron <jic23@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Linus Walleij <linus.walleij@linaro.org>,
Beomho Seo <beomho.seo@samsung.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v2 2/5] dt-bindings: input: Add document bindings for mtk-pmic-keys
Date: Fri, 11 Aug 2017 15:01:32 +0800 [thread overview]
Message-ID: <1502434892.28466.18.camel@mhfsdcap03> (raw)
In-Reply-To: <20170810204136.eghsslqq6d5fqg5d@rob-hp-laptop>
Hi Rob,
On Thu, 2017-08-10 at 15:41 -0500, Rob Herring wrote:
> On Mon, Aug 07, 2017 at 09:57:42AM +0800, Chen Zhong wrote:
> > This patch adds the device tree binding documentation for the MediaTek
> > pmic keys found on PMIC MT6397/MT6323.
> >
> > Signed-off-by: Chen Zhong <chen.zhong@mediatek.com>
> > ---
> > .../devicetree/bindings/input/mtk-pmic-keys.txt | 36 ++++++++++++++++++++
> > 1 file changed, 36 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/input/mtk-pmic-keys.txt
> >
> > diff --git a/Documentation/devicetree/bindings/input/mtk-pmic-keys.txt b/Documentation/devicetree/bindings/input/mtk-pmic-keys.txt
> > new file mode 100644
> > index 0000000..c5b230f
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/input/mtk-pmic-keys.txt
> > @@ -0,0 +1,36 @@
> > +MediaTek MT6397/MT6323 PMIC Keys Device Driver
> > +
> > +There are two key functions provided by MT6397/MT6323 PMIC, pwrkey
> > +and homekey. The key functions are defined as the subnode of the function
> > +node provided by MT6397/MT6323 PMIC that is being defined as one kind
> > +of Muti-Function Device (MFD)
> > +
> > +For MT6397/MT6323 MFD bindings see:
> > +Documentation/devicetree/bindings/mfd/mt6397.txt
> > +
> > +Required properties:
> > +- compatible: "mediatek,mt6397-keys" or "mediatek,mt6323-keys"
> > +- mediatek,pwrkey-code: Keycode of pwrkey
> > +
> > +Optional Properties:
> > +- mediatek,homekey-code: Keycode of homekey
> > +- mediatek,long-press-mode: Long press key shutdown setting, 1 for
> > + pwrkey only, 2 for pwrkey/homekey together, others for disabled.
> > +- mediatek,long-press-duration: Long press key shutdown duration setting,
> > + 0/1/2/3 for 8/11/14/5 seconds.
>
> Surely this could be a common property.
Sorry I'm not very clear about this. Could i move this to required
properties or remove the "mediatek" string here?
>
> > +
> > +Example:
> > +
> > + pmic: mt6397 {
> > + compatible = "mediatek,mt6397";
> > +
> > + ...
> > +
> > + mt6397keys: mt6397keys {
> > + compatible = "mediatek,mt6397-keys";
> > + mediatek,pwrkey-code = <116>;
> > + mediatek,homekey-code = <114>;
>
> We have a standard properties for keycodes.
Could i write them like this way?
linux,keycodes = <KEY_POWER>, <KEY_VOLUMEDOWN>
>
> > + mediatek,long-press-mode = <1>;
> > + mediatek,long-press-duration = <0>;
> > + };
> > + };
> > \ No newline at end of file
> > --
> > 1.7.9.5
> >
Thanks.
next prev parent reply other threads:[~2017-08-11 7:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 1:57 [PATCH v2 0/5] Add MediaTek PMIC keys support Chen Zhong
2017-08-07 1:57 ` [PATCH v2 1/5] mfd: mt6397: create irq mappings in mfd core driver Chen Zhong
2017-08-07 21:32 ` Alexandre Belloni
[not found] ` <20170807213244.7hrd3isq5jj44dgd-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2017-08-08 2:53 ` Dmitry Torokhov
2017-08-08 9:09 ` Chen Zhong
2017-08-08 11:14 ` Lee Jones
2017-08-07 1:57 ` [PATCH v2 2/5] dt-bindings: input: Add document bindings for mtk-pmic-keys Chen Zhong
2017-08-10 20:41 ` Rob Herring
2017-08-11 7:01 ` Chen Zhong [this message]
2017-08-07 1:57 ` [PATCH v2 3/5] dt-bindings: mfd: Add bindings for the keys as subnode of PMIC Chen Zhong
2017-08-10 20:42 ` Rob Herring
2017-08-07 1:57 ` [PATCH v2 4/5] input: Add MediaTek PMIC keys support Chen Zhong
2017-08-08 3:03 ` Dmitry Torokhov
2017-08-08 9:22 ` Chen Zhong
[not found] ` <1502071065-6745-1-git-send-email-chen.zhong-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-08-07 1:57 ` [PATCH v2 5/5] mfd: mt6397: Add PMIC keys support to MT6397 driver Chen Zhong
2017-08-08 11:15 ` Lee Jones
2017-08-11 7:18 ` Chen Zhong
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=1502434892.28466.18.camel@mhfsdcap03 \
--to=chen.zhong@mediatek.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=beomho.seo@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eddie.huang@mediatek.com \
--cc=javier@osg.samsung.com \
--cc=jcsing.lee@samsung.com \
--cc=jic23@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).