devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mason <mpeg.blue-GANU6spQydw@public.gmane.org>
Cc: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Device Tree"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"Linux ARM"
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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-GANU6spQydw@public.gmane.org>

On Wed, 19 Nov 2014 17:05:00 +0100
Mason <mpeg.blue-GANU6spQydw@public.gmane.org> 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
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-11-20 14:33 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
     [not found]     ` <546CBFAC.9040906-GANU6spQydw@public.gmane.org>
2014-11-20  9:18       ` Viresh Kumar
2014-11-20 14:33       ` Antony Pavlov [this message]
     [not found] ` <546C920A.7060800-GANU6spQydw@public.gmane.org>
2014-11-19 16:57   ` Victor Ascroft
     [not found]     ` <546CCBF6.7070607-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-19 17:19       ` Mason
     [not found]         ` <546CD11F.6050502-GANU6spQydw@public.gmane.org>
2014-11-19 17:30           ` Victor Ascroft
2014-11-20 21:41     ` Mason
     [not found]       ` <546E600F.8020704-GANU6spQydw@public.gmane.org>
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-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=afaerber-l3A5Bk7waGM@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mpeg.blue-GANU6spQydw@public.gmane.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).