From: "Heiko Stübner" <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Kever Yang <kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jianqun Xu <jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
Liang Chen <cl-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
Brian Norris
<briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andy Yan <andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
Matthias Brugger
<matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v3] arm64: dts: rk3399: add support for firefly-rk3399 board
Date: Thu, 13 Apr 2017 10:22:28 +0200 [thread overview]
Message-ID: <11306035.2UDh49FpL9@diego> (raw)
In-Reply-To: <6d1eb0cc-fe3b-a483-123c-8558096c0846-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
Am Donnerstag, 13. April 2017, 12:00:19 CEST schrieb Kever Yang:
> Hi Heiko,
>
> On 04/12/2017 09:29 PM, Heiko Stuebner wrote:
> > Hi Kever,
> >
> > Am Montag, 10. April 2017, 11:50:13 CEST schrieb Kever Yang:
> >> Firefly-rk3399 is a bord from T-Firefly, you can find detail about
> >> it here:
> >> http://en.t-firefly.com/en/firenow/Firefly_RK3399/
> >>
> >> This patch add basic node for the board and make it able to bring
> >> up.
> >>
> >> Peripheral works:
> >> - usb hub which connect to ehci controller;
> >> - UART2 debug
> >> - eMMC
> >> - PCIe
> >>
> >> Not work:
> >> - USB 3.0 HOST, type-C port
> >> - sdio, sd-card
> >>
> >> Not test for other peripheral:
> >> - HDMI
> >> - Ethernet
> >> - OPTICAL
> >> - WiFi/BT
> >> - MIPI CSI/DSI
> >> - IR
> >> - EDP/DP
> >>
> >> Signed-off-by: Kever Yang <kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
> >
> > applied for 4.13, as we're a bit late for 4.12, with the following
changes:
> Thanks for your help, I'm not familiar with the devices status on upstream
> because not working on kernel upstream for a long time.
>
> > - commit subject
> > - dropped status from backlight (as there is no disabled common node
> >
> > and it's specific to the firefly itself)
> >
> > - quite some reordering of properties
> > - reordered regulator nodes per their addresses: 0x1b < 0x40
> > - dropped obsolete regulator-compatible properties
> > - fixed gpio-irq on the mpu6500
> > - dropped out-of-tree orientation properties of mpu6500
> >
> > --> please provide the optional "mount-matrix" in a follow-up patch
> >
> > see bindings/iio/imu/inv_mpu6050.txt
>
> Maybe we can drop this mpu6050 node first? I can't find binding file for it.
The binding (and driver in the kernel) is the same as for the mpu6050.
So you can find the documentation in
Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt
Someone should add the other ids from
drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c
to the binding.
mount-matrix is optional, so the basic node itself can stay in the dt.
Heiko
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] arm64: dts: rk3399: add support for firefly-rk3399 board
Date: Thu, 13 Apr 2017 10:22:28 +0200 [thread overview]
Message-ID: <11306035.2UDh49FpL9@diego> (raw)
In-Reply-To: <6d1eb0cc-fe3b-a483-123c-8558096c0846@rock-chips.com>
Am Donnerstag, 13. April 2017, 12:00:19 CEST schrieb Kever Yang:
> Hi Heiko,
>
> On 04/12/2017 09:29 PM, Heiko Stuebner wrote:
> > Hi Kever,
> >
> > Am Montag, 10. April 2017, 11:50:13 CEST schrieb Kever Yang:
> >> Firefly-rk3399 is a bord from T-Firefly, you can find detail about
> >> it here:
> >> http://en.t-firefly.com/en/firenow/Firefly_RK3399/
> >>
> >> This patch add basic node for the board and make it able to bring
> >> up.
> >>
> >> Peripheral works:
> >> - usb hub which connect to ehci controller;
> >> - UART2 debug
> >> - eMMC
> >> - PCIe
> >>
> >> Not work:
> >> - USB 3.0 HOST, type-C port
> >> - sdio, sd-card
> >>
> >> Not test for other peripheral:
> >> - HDMI
> >> - Ethernet
> >> - OPTICAL
> >> - WiFi/BT
> >> - MIPI CSI/DSI
> >> - IR
> >> - EDP/DP
> >>
> >> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> >
> > applied for 4.13, as we're a bit late for 4.12, with the following
changes:
> Thanks for your help, I'm not familiar with the devices status on upstream
> because not working on kernel upstream for a long time.
>
> > - commit subject
> > - dropped status from backlight (as there is no disabled common node
> >
> > and it's specific to the firefly itself)
> >
> > - quite some reordering of properties
> > - reordered regulator nodes per their addresses: 0x1b < 0x40
> > - dropped obsolete regulator-compatible properties
> > - fixed gpio-irq on the mpu6500
> > - dropped out-of-tree orientation properties of mpu6500
> >
> > --> please provide the optional "mount-matrix" in a follow-up patch
> >
> > see bindings/iio/imu/inv_mpu6050.txt
>
> Maybe we can drop this mpu6050 node first? I can't find binding file for it.
The binding (and driver in the kernel) is the same as for the mpu6050.
So you can find the documentation in
Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt
Someone should add the other ids from
drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c
to the binding.
mount-matrix is optional, so the basic node itself can stay in the dt.
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Kever Yang <kever.yang@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
Jianqun Xu <jay.xu@rock-chips.com>,
Liang Chen <cl@rock-chips.com>,
Brian Norris <briannorris@chromium.org>,
linux-kernel@vger.kernel.org, Andy Yan <andy.yan@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v3] arm64: dts: rk3399: add support for firefly-rk3399 board
Date: Thu, 13 Apr 2017 10:22:28 +0200 [thread overview]
Message-ID: <11306035.2UDh49FpL9@diego> (raw)
In-Reply-To: <6d1eb0cc-fe3b-a483-123c-8558096c0846@rock-chips.com>
Am Donnerstag, 13. April 2017, 12:00:19 CEST schrieb Kever Yang:
> Hi Heiko,
>
> On 04/12/2017 09:29 PM, Heiko Stuebner wrote:
> > Hi Kever,
> >
> > Am Montag, 10. April 2017, 11:50:13 CEST schrieb Kever Yang:
> >> Firefly-rk3399 is a bord from T-Firefly, you can find detail about
> >> it here:
> >> http://en.t-firefly.com/en/firenow/Firefly_RK3399/
> >>
> >> This patch add basic node for the board and make it able to bring
> >> up.
> >>
> >> Peripheral works:
> >> - usb hub which connect to ehci controller;
> >> - UART2 debug
> >> - eMMC
> >> - PCIe
> >>
> >> Not work:
> >> - USB 3.0 HOST, type-C port
> >> - sdio, sd-card
> >>
> >> Not test for other peripheral:
> >> - HDMI
> >> - Ethernet
> >> - OPTICAL
> >> - WiFi/BT
> >> - MIPI CSI/DSI
> >> - IR
> >> - EDP/DP
> >>
> >> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
> >
> > applied for 4.13, as we're a bit late for 4.12, with the following
changes:
> Thanks for your help, I'm not familiar with the devices status on upstream
> because not working on kernel upstream for a long time.
>
> > - commit subject
> > - dropped status from backlight (as there is no disabled common node
> >
> > and it's specific to the firefly itself)
> >
> > - quite some reordering of properties
> > - reordered regulator nodes per their addresses: 0x1b < 0x40
> > - dropped obsolete regulator-compatible properties
> > - fixed gpio-irq on the mpu6500
> > - dropped out-of-tree orientation properties of mpu6500
> >
> > --> please provide the optional "mount-matrix" in a follow-up patch
> >
> > see bindings/iio/imu/inv_mpu6050.txt
>
> Maybe we can drop this mpu6050 node first? I can't find binding file for it.
The binding (and driver in the kernel) is the same as for the mpu6050.
So you can find the documentation in
Documentation/devicetree/bindings/iio/imu/inv_mpu6050.txt
Someone should add the other ids from
drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c
to the binding.
mount-matrix is optional, so the basic node itself can stay in the dt.
Heiko
next prev parent reply other threads:[~2017-04-13 8:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 3:50 [PATCH v3] arm64: dts: rk3399: add support for firefly-rk3399 board Kever Yang
2017-04-10 3:50 ` Kever Yang
2017-04-10 3:50 ` Kever Yang
2017-04-12 13:29 ` Heiko Stuebner
2017-04-12 13:29 ` Heiko Stuebner
2017-04-13 4:00 ` Kever Yang
2017-04-13 4:00 ` Kever Yang
2017-04-13 4:00 ` Kever Yang
[not found] ` <6d1eb0cc-fe3b-a483-123c-8558096c0846-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-04-13 8:22 ` Heiko Stübner [this message]
2017-04-13 8:22 ` Heiko Stübner
2017-04-13 8:22 ` Heiko Stübner
[not found] ` <1491796213-4115-1-git-send-email-kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-04-18 19:31 ` Marc Zyngier
2017-04-18 19:31 ` Marc Zyngier
2017-04-18 19:31 ` Marc Zyngier
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=11306035.2UDh49FpL9@diego \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=andy.yan-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \
--cc=cl-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jay.xu-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=kever.yang-TNX95d0MmH7DzftRWevZcw@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.