From: Antony Pavlov <antonynpavlov@gmail.com>
To: Mason <mpeg.blue@free.fr>
Cc: "Andreas Färber" <afaerber@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
"Device Tree" <devicetree@vger.kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>
Subject: Re: Looking for good references for ARM driver development
Date: Thu, 20 Nov 2014 18:33:05 +0400 [thread overview]
Message-ID: <20141120183305.53af4ec99d746403b339aaf1@gmail.com> (raw)
In-Reply-To: <546CBFAC.9040906@free.fr>
On Wed, 19 Nov 2014 17:05:00 +0100
Mason <mpeg.blue@free.fr> wrote:
> Hello Andreas,
>
> On 19/11/2014 16:02, Andreas Färber wrote:
>
> > Am 19.11.2014 um 13:50 schrieb Mason:
> >
...
> > Since this appears to be about an ARM SoC according to your To list,
> > in general, you create a device tree binding, that binding is
> > registered within your platform/... driver code and referenced in the
> > device tree for SoC or board, and then your driver will automatically
> > be probed.
>
> I know nothing about DT (aside from the Wikipedia entry).
> I'll take a closer look at Documentation/devicetree.
> Will that explain what platform/... is?
>
> I see a drivers/platform folder, but nothing ARM-specific there?
There are very good presentations from Free Electrons:
* http://free-electrons.com/pub/conferences/2013/elce/petazzoni-device-tree-dummies/petazzoni-device-tree-dummies.pdf
** see also http://www.youtube.com/watch?v=m_NyYEBxfn8
* https://archive.fosdem.org/2013/schedule/event/arm_in_the_linux_kernel/attachments/slides/273/export/events/attachments/arm_in_the_linux_kernel/slides/273/arm_support_kernel.pdf
--
Best regards,
Antony Pavlov
next prev parent reply other threads:[~2014-11-20 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 12:50 Looking for good references for ARM driver development Mason
2014-11-19 15:02 ` Andreas Färber
2014-11-19 16:05 ` Mason
2014-11-20 9:18 ` Viresh Kumar
2014-11-20 14:33 ` Antony Pavlov [this message]
2014-11-19 16:57 ` Victor Ascroft
2014-11-19 17:19 ` Mason
2014-11-19 17:30 ` Victor Ascroft
2014-11-20 21:41 ` Mason
2014-11-21 6:00 ` Victor Ascroft
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=20141120183305.53af4ec99d746403b339aaf1@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpeg.blue@free.fr \
/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).