From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755100AbdDMIWi (ORCPT ); Thu, 13 Apr 2017 04:22:38 -0400 Received: from gloria.sntech.de ([95.129.55.99]:33332 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750746AbdDMIWf (ORCPT ); Thu, 13 Apr 2017 04:22:35 -0400 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Kever Yang Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org, Jianqun Xu , Liang Chen , Brian Norris , linux-kernel@vger.kernel.org, Andy Yan , Rob Herring , linux-arm-kernel@lists.infradead.org, Will Deacon , Mark Rutland , Catalin Marinas , Matthias Brugger Subject: Re: [PATCH v3] arm64: dts: rk3399: add support for firefly-rk3399 board Date: Thu, 13 Apr 2017 10:22:28 +0200 Message-ID: <11306035.2UDh49FpL9@diego> User-Agent: KMail/5.2.3 (Linux/4.8.0-2-amd64; KDE/5.27.0; x86_64; ; ) In-Reply-To: <6d1eb0cc-fe3b-a483-123c-8558096c0846@rock-chips.com> References: <1491796213-4115-1-git-send-email-kever.yang@rock-chips.com> <1642127.PiTFsmK4zh@phil> <6d1eb0cc-fe3b-a483-123c-8558096c0846@rock-chips.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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 > > > > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko =?ISO-8859-1?Q?St=FCbner?= Subject: Re: [PATCH v3] arm64: dts: rk3399: add support for firefly-rk3399 board Date: Thu, 13 Apr 2017 10:22:28 +0200 Message-ID: <11306035.2UDh49FpL9@diego> References: <1491796213-4115-1-git-send-email-kever.yang@rock-chips.com> <1642127.PiTFsmK4zh@phil> <6d1eb0cc-fe3b-a483-123c-8558096c0846@rock-chips.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <6d1eb0cc-fe3b-a483-123c-8558096c0846-TNX95d0MmH7DzftRWevZcw@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Kever Yang Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Jianqun Xu , Liang Chen , Brian Norris , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andy Yan , Rob Herring , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Will Deacon , Mark Rutland , Catalin Marinas , Matthias Brugger List-Id: devicetree@vger.kernel.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 > > > > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: heiko@sntech.de (Heiko =?ISO-8859-1?Q?St=FCbner?=) Date: Thu, 13 Apr 2017 10:22:28 +0200 Subject: [PATCH v3] arm64: dts: rk3399: add support for firefly-rk3399 board In-Reply-To: <6d1eb0cc-fe3b-a483-123c-8558096c0846@rock-chips.com> References: <1491796213-4115-1-git-send-email-kever.yang@rock-chips.com> <1642127.PiTFsmK4zh@phil> <6d1eb0cc-fe3b-a483-123c-8558096c0846@rock-chips.com> Message-ID: <11306035.2UDh49FpL9@diego> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.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 > > > > 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