From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id EC027E008CE; Mon, 13 Jul 2015 07:56:48 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.chez-thomas.org (mail.mlbassoc.com [65.100.170.105]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 047A1E00895 for ; Mon, 13 Jul 2015 07:56:45 -0700 (PDT) Received: by mail.chez-thomas.org (Postfix, from userid 1998) id E8975F811D7; Mon, 13 Jul 2015 08:56:44 -0600 (MDT) Received: from [192.168.1.114] (zeus [192.168.1.114]) by mail.chez-thomas.org (Postfix) with ESMTP id 67315F8119A; Mon, 13 Jul 2015 08:56:44 -0600 (MDT) Message-ID: <55A3D1B2.8070501@mlbassoc.com> Date: Mon, 13 Jul 2015 08:56:50 -0600 From: Gary Thomas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Nikolay Dimitrov , meta-freescale@yoctoproject.org References: <55A3CD11.3020306@mlbassoc.com> <55A3D08F.3060608@mail.bg> In-Reply-To: <55A3D08F.3060608@mail.bg> Subject: Re: Device tree question X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jul 2015 14:56:49 -0000 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 2015-07-13 08:51, Nikolay Dimitrov wrote: > Hi Gary, > > On 07/13/2015 05:37 PM, Gary Thomas wrote: >> A bit off topic, but perhaps someone here knows the answer :-) >> >> If my device tree has a device/element that is enabled, why would >> that device be disabled when I boot? I have this on my (LS1021) board: >> quadspi@1550000 { >> compatible = "fsl,ls1-qspi"; >> #address-cells = <0x00000001>; >> #size-cells = <0x00000000>; >> reg = <0x00000000 0x01550000 0x00000000 0x00010000 >> 0x00000000 0x40000000 0x00000000 0x04000000>; >> reg-names = "QuadSPI", "QuadSPI-memory"; >> interrupts = <0x00000000 0x00000083 0x00000004>; >> clock-names = "qspi_en", "qspi"; >> clocks = <0x00000003 0x00000001 0x00000003 0x00000001>; >> big-endian; >> amba-base = <0x40000000>; >> num-cs = <0x00000002>; >> status = "okay"; >> s70fl01gs@0 { >> #address-cells = <0x00000001>; >> #size-cells = <0x00000001>; >> compatible = "spansion,s70fl01gs"; >> spi-max-frequency = <0x02faf080>; >> reg = <0x00000000>; >> partition@0 { >> label = "s70fl01gs-0"; >> reg = <0x00000000 0x04000000>; >> }; >> }; >> }; >> >> However when I boot the system, this device is disabled. >> # cat /proc/device-tree/soc/quadspi@1550000/status >> disabled >> I know this must happen very early on as the device driver >> for this device is never even probed. >> >> Any ideas where/why this becomes disabled and how I keep that >> from happening? >> > > Is it possible to have an invalid device node parameter, which can > cause the node to become disabled? Have you seen related warn/err > messages in the bootlog? Also, is the ls1-qspi driver enabled in the > defconfig (stupid question, but sometimes we do such things :D). No warnings/errors and the driver is enabled in the config. What puzzles me is that the device tree says it should be enabled but at run time it is not :-( -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------