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 16:54:00 +0200 [thread overview]
Message-ID: <55BB8C08.1060006@free.fr> (raw)
In-Reply-To: <55BB4686.8030509@free.fr>
On 31/07/2015 11:57, Mason wrote:
> Then I set a breakpoint in of_platform_serial_probe, hoping
> to witness the miracle... and nothing. Looks like device is
> never registered :-(
IIUC, the kernel is supposed to parse my "uart0" node, and
register the device. Then the platform framework should see
that the node's "compatible" property is equal to one
advertized by the of_platform_serial_driver, and the kernel
should #!@& call of_platform_serial_probe? Right?!
I just can't believe how much time I've been pulling my hair
over this trivial issue...
Regards.
next prev parent reply other threads:[~2015-07-31 14:54 UTC|newest]
Thread overview: 6+ 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 14:54 ` Mason [this message]
2015-07-31 15:05 ` Russell King - ARM Linux
2015-07-31 15:13 ` Mason
2015-07-31 16:17 ` Mason
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=55BB8C08.1060006@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).