All of lore.kernel.org
 help / color / mirror / Atom feed
From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: Converting "board file" to device tree one device at a time?
Date: Fri, 31 Jul 2015 18:17:11 +0200	[thread overview]
Message-ID: <55BB9F87.2050307@free.fr> (raw)
In-Reply-To: <20150731150551.GW7557@n2100.arm.linux.org.uk>

On 31/07/2015 17:05, Russell King - ARM Linux wrote:

> My /guess/ is that you have an .init_machine callback in place, but that
> is not calling of_platform_populate(NULL, of_default_bus_match_table,
> NULL, NULL); which means none of the DT-described devices are being
> created.

You guessed right. Thanks again!

One more question, if I may.

I deleted the .init_machine callback, but the board init
function was still being called!

MACHINE_START(TANGOX_87XX, "TANGOX_87XX")
  ...
  //.init_machine = tangox_87xx_board_init,
MACHINE_END

I suspected it might be called directly from elsewhere,
and launched grep:

  arch_initcall(tangox_init_devices);

I suppose the arch_initcall macro registers the function
to be called at some point during init?

Then this means that, before I commented the .init_machine
callback, the function was being called twice?

Once through .init_machine and once through arch_initcall?

Regards.

  parent reply	other threads:[~2015-07-31 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  9:57 Converting "board file" to device tree one device at a time? Mason
2015-07-31  9:57 ` Mason
2015-07-31 14:54 ` Mason
2015-07-31 14:54   ` Mason
2015-07-31 15:05   ` Russell King - ARM Linux
2015-07-31 15:05     ` Russell King - ARM Linux
2015-07-31 15:13     ` Mason
2015-07-31 15:13       ` Mason
2015-07-31 16:17     ` Mason [this message]
2015-07-31 16:46       ` Russell King - ARM Linux

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=55BB9F87.2050307@free.fr \
    --to=slash.tmp@free.fr \
    --cc=linux-arm-kernel@lists.infradead.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.