From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752059AbdLEU6u (ORCPT ); Tue, 5 Dec 2017 15:58:50 -0500 Received: from mail-wm0-f44.google.com ([74.125.82.44]:46164 "EHLO mail-wm0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751937AbdLEU6q (ORCPT ); Tue, 5 Dec 2017 15:58:46 -0500 X-Google-Smtp-Source: AGs4zMYPk4IRbT5c5FCVSCwcjzgtaf2HedJLLGwO7P5/wGefnn+AY2BFMQ91oIZs6Brjd3K7tqBW5tcuK47QX/I0oCo= MIME-Version: 1.0 In-Reply-To: References: <20171130201434.14122-1-tyler@opensourcefoundries.com> <20171130201434.14122-2-tyler@opensourcefoundries.com> From: Tyler Baker Date: Tue, 5 Dec 2017 12:58:44 -0800 Message-ID: Subject: Re: [PATCH 1/8] ARM: dts: imx7d-sbc-iot: add initial iot gateway dts To: Fabio Estevam Cc: Shawn Guo , Fabio Estevam , Sascha Hauer , "robh+dt@kernel.org" , Mark Rutland , "linux-arm-kernel@lists.infradead.org" , "devicetree@vger.kernel.org" , linux-kernel , Ilya Ledvich Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 1, 2017 at 12:10 PM, Fabio Estevam wrote: > On Thu, Nov 30, 2017 at 6:14 PM, wrote: > >> +&ecspi3 { >> + fsl,spi-num-chipselects = <1>; > > Please remove this property. It is no longer used. Ack. > > >> + dvicape@39 { >> + compatible = "sil164_simple"; > > This compatible string does not exist. I'm going to drop this, and address the display hardware it in a later series. > > > >> +&lcdif { >> + pinctrl-names = "default"; >> + pinctrl-0 = <&pinctrl_lcdif_dat >> + &pinctrl_lcdif_ctrl>; >> + display = <&display0>; >> + status = "okay"; >> + >> + display0: display { >> + bits-per-pixel = <24>; >> + bus-width = <24>; >> + >> + display-timings { >> + native-mode = <&timing0>; >> + timing0: dvi { >> + /* 1024x768p60 */ >> + clock-frequency = <65000000>; >> + hactive = <1024>; >> + hfront-porch = <40>; >> + hback-porch = <220>; >> + hsync-len = <60>; >> + vactive = <768>; >> + vfront-porch = <7>; >> + vback-porch = <21>; >> + vsync-len = <10>; >> + >> + hsync-active = <0>; >> + vsync-active = <0>; >> + de-active = <1>; >> + pixelclk-active = <0>; > > Which panel is this? Could you use a simple panel driver compatible > string instead? I'll switch to a simple panel driver and do some more testing. Will submit a follow up series to address the LCD panel and dvi cape. > > >> + }; >> + }; >> + }; >> +}; >> + >> +&uart2 { >> + pinctrl-names = "default"; >> + pinctrl-0 = <&pinctrl_uart2>; >> + assigned-clocks = <&clks IMX7D_UART2_ROOT_SRC>; >> + assigned-clock-parents = <&clks IMX7D_OSC_24M_CLK>; >> + fsl,uart-has-rtscts; > > Please use 'uart-has-rtscts' instead. Ack. > >> + status = "okay"; >> +}; >> + >> +&uart5 { >> + pinctrl-names = "default"; >> + pinctrl-0 = <&pinctrl_uart5>; >> + assigned-clocks = <&clks IMX7D_UART5_ROOT_SRC>; >> + assigned-clock-parents = <&clks IMX7D_PLL_SYS_MAIN_240M_CLK>; >> + fsl,uart-has-rtscts; > > Ditto. Ack. > >> + status = "okay"; >> +}; >> + >> +&uart7 { >> + pinctrl-names = "default"; >> + pinctrl-0 = <&pinctrl_uart7>; >> + assigned-clocks = <&clks IMX7D_UART7_ROOT_SRC>; >> + assigned-clock-parents = <&clks IMX7D_PLL_SYS_MAIN_240M_CLK>; >> + fsl,uart-has-rtscts; > > Ditto Ack.