devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Andra Danciu <andradanciu1997@gmail.com>
Cc: robh+dt@kernel.org, mark.rutland@arm.com, leoyang.li@nxp.com,
	Fabio Estevam <festevam@gmail.com>,
	aisheng.dong@nxp.com, l.stach@pengutronix.de, angus@akkea.ca,
	vabhav.sharma@nxp.com, pankaj.bansal@nxp.com,
	bhaskar.upadhaya@nxp.com, ping.bai@nxp.com,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	Richard Hu <richard.hu@technexion.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	matti.vaittinen@fi.rohmeurope.com, linux-imx@nxp.com,
	Daniel Baluta <daniel.baluta@nxp.com>
Subject: Re: [PATCH v2] arm64: dts: fsl: pico-pi: Add a device tree for the PICO-PI-IMX8M
Date: Mon, 22 Jul 2019 10:03:46 +0800	[thread overview]
Message-ID: <20190722020345.GR3738@dragon> (raw)
In-Reply-To: <CAJNLGszB239AHpD+kRCPRWZaToTYHiq5YUHRjfRwTqknwHMdMA@mail.gmail.com>

On Thu, Jul 18, 2019 at 02:12:10PM +0300, Andra Danciu wrote:
...
> > > +     pmic: pmic@4b {
> > > +             reg = <0x4b>;
> > > +             compatible = "rohm,bd71837";
> > > +             /* PMIC BD71837 PMIC_nINT GPIO1_IO12 */
> > > +             pinctrl-0 = <&pinctrl_pmic>;
> > > +             gpio_intr = <&gpio1 3 GPIO_ACTIVE_LOW>;
> >
> > Where is the bindings for this property?
> Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt

I do not see property 'gpio_intr' in there.

Shawn

  reply	other threads:[~2019-07-22  2:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-25 12:34 [PATCH v2] arm64: dts: fsl: pico-pi: Add a device tree for the PICO-PI-IMX8M Andra Danciu
2019-07-18  3:55 ` Shawn Guo
2019-07-18 11:12   ` Andra Danciu
2019-07-22  2:03     ` Shawn Guo [this message]
2019-07-22 17:40       ` Vaittinen, Matti
2019-07-22 21:19         ` Daniel Baluta

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=20190722020345.GR3738@dragon \
    --to=shawnguo@kernel.org \
    --cc=aisheng.dong@nxp.com \
    --cc=andradanciu1997@gmail.com \
    --cc=angus@akkea.ca \
    --cc=bhaskar.upadhaya@nxp.com \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=leoyang.li@nxp.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mark.rutland@arm.com \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=pankaj.bansal@nxp.com \
    --cc=ping.bai@nxp.com \
    --cc=richard.hu@technexion.com \
    --cc=robh+dt@kernel.org \
    --cc=vabhav.sharma@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).