From: frowand.list@gmail.com (Frank Rowand)
To: linux-arm-kernel@lists.infradead.org
Subject: [ARM ATTEND] DT from the driver perspective
Date: Tue, 03 Sep 2013 09:34:20 -0700 [thread overview]
Message-ID: <52260F8C.6060108@gmail.com> (raw)
I would like to request an invite to the ARM Kernel Summit.
I have seen a lot of documentation, discussion, and presentations on what the
.dts files should look like, but very little on how drivers should use the
device tree API. As I am diving into the device tree world with some hardware
with many layers of dependencies and cross function interactions I am finding
that the device tree implementation is not as complete and robust as I had
expected. Of course, I am also interested in discussions about .dts files.
-Frank Rowand
Sony Mobile Communications
reply other threads:[~2013-09-03 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52260F8C.6060108@gmail.com \
--to=frowand.list@gmail.com \
--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).