From: Tony Lindgren <tony@atomide.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: linux-omap@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] ARM: dts: am335x: add am335x-sancloud-bbe board support
Date: Mon, 16 Jul 2018 23:36:31 -0700 [thread overview]
Message-ID: <20180717063631.GZ99251@atomide.com> (raw)
In-Reply-To: <1531808688-9716-3-git-send-email-koen@dominion.thruhere.net>
* Koen Kooi <koen@dominion.thruhere.net> [180717 06:28]:
> +&i2c0 {
> + lps331ap: barometer@5c {
> + compatible = "st,lps331ap-press";
> + st,drdy-int-pin = <1>;
> + reg = <0x5c>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <26 IRQ_TYPE_EDGE_RISING>;
> + };
> +
> + mpu6050: accelerometer@68 {
> + compatible = "invensense,mpu6050";
> + reg = <0x68>;
> + interrupt-parent = <&gpio0>;
> + interrupts = <2 IRQ_TYPE_EDGE_RISING>;
> + orientation = <0xff 0 0 0 1 0 0 0 0xff>;
> + };
> +
> + usb2512b@2c {
> + compatible = "microchip,usb2512b";
> + reg = <0x2c>;
> + reset-gpios = <&gpio0 29 GPIO_ACTIVE_LOW>;
> + /* wifi on port 4 */
> + };
> +};
Thanks for updating it, should the last one be usb-hub@2c?
Regards,
Tony
next prev parent reply other threads:[~2018-07-17 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 6:24 [PATCH v5 0/2] ARM: dts: am3355: add support for the Sancloud Beaglebone Enhanced Koen Kooi
2018-07-17 6:24 ` [PATCH v5 1/2] dt-bindings: Add vendor prefix for Sancloud Koen Kooi
2018-07-17 7:20 ` Alexandre Belloni
2018-07-17 7:31 ` Koen Kooi
2018-07-17 7:36 ` Alexandre Belloni
2018-07-17 7:43 ` Koen Kooi
2018-07-17 8:02 ` Tony Lindgren
2018-07-17 6:24 ` [PATCH v5 2/2] ARM: dts: am335x: add am335x-sancloud-bbe board support Koen Kooi
2018-07-17 6:36 ` Tony Lindgren [this message]
2018-07-17 6:52 ` Koen Kooi
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=20180717063631.GZ99251@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=koen@dominion.thruhere.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).