All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/3] ARM: shmobile: r8a7790: add Ether support
Date: Wed, 17 Jul 2013 23:01:13 +0000	[thread overview]
Message-ID: <20130717230113.GA8154@verge.net.au> (raw)
In-Reply-To: <20130717091103.GD15981@e106331-lin.cambridge.arm.com>

On Wed, Jul 17, 2013 at 10:11:03AM +0100, Mark Rutland wrote:

[snip]

> Why are we hardcoding the address and interrupt of a device rather than
> describing it in the devicetree? This is the most trivial case to
> describe.

The approach that shmobile is taking is to either initialise a device
entirely using C (non-DT) or entirely using DT. And moreover to either
initialise a board using C or DT (though in the latter case some devices
still end up being initialised in C to provide a minimally working system).

At this time for more recent boards we typically provide both a C and DT
versions to initialise a board. The C version typically is able to
initialise a fuller set of hardware while the DT version catches up.

In this case the device is being initialised in C. And this code is
intended ti be used when a board and thus its SoC is initialised using C.

Once the SH ethernet driver and all its pre-requisite drivers and
infrastructure can be initialised using DT then that will be used when
initialising the board using DT.

WARNING: multiple messages have this Message-ID (diff)
From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] ARM: shmobile: r8a7790: add Ether support
Date: Thu, 18 Jul 2013 08:01:13 +0900	[thread overview]
Message-ID: <20130717230113.GA8154@verge.net.au> (raw)
In-Reply-To: <20130717091103.GD15981@e106331-lin.cambridge.arm.com>

On Wed, Jul 17, 2013 at 10:11:03AM +0100, Mark Rutland wrote:

[snip]

> Why are we hardcoding the address and interrupt of a device rather than
> describing it in the devicetree? This is the most trivial case to
> describe.

The approach that shmobile is taking is to either initialise a device
entirely using C (non-DT) or entirely using DT. And moreover to either
initialise a board using C or DT (though in the latter case some devices
still end up being initialised in C to provide a minimally working system).

At this time for more recent boards we typically provide both a C and DT
versions to initialise a board. The C version typically is able to
initialise a fuller set of hardware while the DT version catches up.

In this case the device is being initialised in C. And this code is
intended ti be used when a board and thus its SoC is initialised using C.

Once the SH ethernet driver and all its pre-requisite drivers and
infrastructure can be initialised using DT then that will be used when
initialising the board using DT.

  reply	other threads:[~2013-07-17 23:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  7:20 [PATCH v4 0/3] ARM: shmobile: lager: enable Ether Simon Horman
2013-07-01  7:20 ` Simon Horman
2013-07-01  7:20 ` [PATCH v4 1/3] ARM: shmobile: r8a7790: add Ether support Simon Horman
2013-07-01  7:20   ` Simon Horman
2013-07-17  9:11   ` Mark Rutland
2013-07-17  9:11     ` Mark Rutland
2013-07-17 23:01     ` Simon Horman [this message]
2013-07-17 23:01       ` Simon Horman
2013-07-01  7:20 ` [PATCH v4 2/3] ARM: shmobile: lager: enable Ether Simon Horman
2013-07-01  7:20   ` Simon Horman
2013-07-01 13:29   ` Laurent Pinchart
2013-07-01 13:29     ` Laurent Pinchart
2013-07-02  1:22     ` Simon Horman
2013-07-02  1:22       ` Simon Horman
2013-07-03  2:30       ` Laurent Pinchart
2013-07-03  2:30         ` Laurent Pinchart
2013-07-01  7:20 ` [PATCH v4 3/3] ARM: shmobile: lager: enable nfsroot in DTS Simon Horman
2013-07-01  7:20   ` Simon Horman
2013-07-16  9:42 ` [PATCH v4 0/3] ARM: shmobile: lager: enable Ether Laurent Pinchart
2013-07-16  9:42   ` Laurent Pinchart
2013-07-16 12:28   ` Sergei Shtylyov
2013-07-16 12:28     ` Sergei Shtylyov
2013-07-16 23:49   ` Simon Horman
2013-07-16 23:49     ` Simon Horman

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=20130717230113.GA8154@verge.net.au \
    --to=horms@verge.net.au \
    --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.