All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: meta-freescale@yoctoproject.org
Subject: Device tree question
Date: Mon, 13 Jul 2015 08:37:05 -0600	[thread overview]
Message-ID: <55A3CD11.3020306@mlbassoc.com> (raw)

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?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2015-07-13 14:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 14:37 Gary Thomas [this message]
2015-07-13 14:51 ` Device tree question Nikolay Dimitrov
2015-07-13 14:56   ` Gary Thomas
     [not found] <406TgmPNY6832S04.1436800490@web04.cms.usa.net>
2015-07-13 15:18 ` Gary Thomas
2015-07-13 15:53   ` Gary Thomas
2015-07-13 16:04     ` Nikolay Dimitrov
  -- strict thread matches above, loose matches on Subject: below --
2008-08-07 19:56 Steven A. Falco
2008-08-09  7:41 ` Benjamin Herrenschmidt
2008-08-11 14:05   ` Steven A. Falco
2007-09-18 20:43 device " Alan Bennett
2007-09-18 22:06 ` Scott Wood
2007-09-18 22:21   ` Alan Bennett
2007-09-18 22:36     ` Scott Wood
     [not found]       ` <bfa0697f0709181604i5758824foad67a86455f45d8e@mail.gmail.com>
     [not found]         ` <46F05BF7.6020906@freescale.com>
     [not found]           ` <bfa0697f0709190638r6894fab6gd31a5672a997e97@mail.gmail.com>
     [not found]             ` <46F16BD4.2000207@freescale.com>
     [not found]               ` <bfa0697f0709191420x5a6aed9dx499fe4a8cf6b1b2d@mail.gmail.com>
     [not found]                 ` <46F19326.7050507@freescale.com>
2007-09-20 17:53                   ` Alan Bennett
2007-09-20 18:31                     ` Scott Wood
2007-09-20 21:38                       ` Alan Bennett
2007-09-20 21:43                         ` Scott Wood

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=55A3CD11.3020306@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.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.