public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
	David Cohen <david.a.cohen@linux.intel.com>,
	wim@iguana.be, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 2/2] x86: intel-mid: add watchdog platform code for Merrifield
Date: Wed, 9 Apr 2014 08:18:22 -0700	[thread overview]
Message-ID: <20140409151822.GA21864@roeck-us.net> (raw)
In-Reply-To: <2205089.MXSpGW1NLo@ws-stein>

On Wed, Apr 09, 2014 at 04:03:14PM +0200, Alexander Stein wrote:
> On Wednesday 09 April 2014 14:58:48, One Thousand Gnomes wrote:
> > > I'm getting curious: How can I use device-tree on x86(_64)?
> > > Reading the dependencies from CONFIG_OF it can only be used on 32bit systems with some special hardware bases.
> > > So, how to use otherwise?
> > 
> > There isn't any fundamental thing tying device tree to a given
> > architecture or 32bitness, it's just that sane PC architectures use ACPI
> > to enumerate devices, and/or have a discoverable bus architecture.
> > 
> > Some of the phones don't so this now becoems a point of consideration. In
> > fact it's already also used on CE4100 (which is an embedded media SoC
> > found in some TV devices and set-top boxes) and on the OLPC (One laptop
> > per child). There is no intrinsic reason it couldn't be used in other x86
> > special cases.
> > 
> > If its PC shaped however it probably has ACPI and ACPI and DT are not a
> > 1:1 mapping. ACPI has method invocations, and various firmware provided
> > interfaces such as the EC, Device tree is better at some other bits.
> 
> Yep, like SPI devices on embedded x86 hardware.
> 
> > Converting the phones to embedded device tree rather than adding a
> > billion little platform files on the other hand seems to me like a
> > no-brainer.
> 
> I found http://thread.gmane.org/gmane.linux.drivers.devicetree/4475. Why didn't that get into mainline?
> 

Isn't that patch set in mainline ?

We are working on a patch set to make DT support on x86 more
widely available. Thierry Reding did some work on it a while ago.
Some of it is upstream, other parts are available in 
	https://github.com/avionic-design/linux/commits/medatom/master

We'll see if and what will be accepted upstream.

Guenter

  reply	other threads:[~2014-04-09 15:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 20:59 [PATCH 0/2] Initial implementation of Intel MID watchdog driver David Cohen
2014-04-08 20:59 ` [PATCH 1/2] watchdog: add Intel MID watchdog driver support David Cohen
2014-04-08 23:56   ` Randy Dunlap
2014-04-09 17:48     ` David Cohen
2014-04-10 13:51       ` Guenter Roeck
2014-04-10 18:24         ` David Cohen
2014-04-09  0:17   ` Guenter Roeck
2014-04-09 12:41     ` One Thousand Gnomes
2014-04-08 20:59 ` [PATCH 2/2] x86: intel-mid: add watchdog platform code for Merrifield David Cohen
2014-04-09 12:42   ` One Thousand Gnomes
2014-04-09 13:49     ` Alexander Stein
2014-04-09 13:58       ` One Thousand Gnomes
2014-04-09 14:03         ` Alexander Stein
2014-04-09 15:18           ` Guenter Roeck [this message]
2014-04-09 16:10             ` Alexander Stein
2014-04-09 17:15               ` Guenter Roeck
2014-04-10 11:08               ` One Thousand Gnomes
2014-04-09 18:00     ` David Cohen
2014-04-10 19:15   ` Guenter Roeck
2014-04-10 19:30     ` David Cohen
2014-04-10 20:35       ` Guenter Roeck
2014-04-10 21:23         ` David Cohen
2014-04-10 22:51           ` Guenter Roeck
2014-04-11 20:50 ` [PATCH v2 0/2] Initial implementation of Intel MID watchdog driver David Cohen
2014-04-11 20:50   ` [PATCH v2 1/2] watchdog: add Intel MID watchdog driver support David Cohen
2014-04-11 20:50   ` [PATCH v2 2/2] x86: intel-mid: add watchdog platform code for Merrifield David Cohen
2014-04-15 18:41   ` [PATCH v3 0/2] Initial implementation of Intel MID watchdog driver David Cohen
2014-04-15 18:41     ` [PATCH v3 1/2] watchdog: add Intel MID watchdog driver support David Cohen
2014-04-15 19:01       ` Guenter Roeck
2014-04-15 19:24         ` David Cohen
2014-04-15 18:41     ` [PATCH v3 2/2] x86: intel-mid: add watchdog platform code for Merrifield David Cohen
2014-04-15 19:09       ` Guenter Roeck
2014-04-15 19:30         ` David Cohen
2014-04-15 20:06     ` [PATCH v4 0/2] Initial implementation of Intel MID watchdog driver David Cohen
2014-04-15 20:06       ` [PATCH v4 1/2] watchdog: add Intel MID watchdog driver support David Cohen
2014-04-16  0:13         ` Guenter Roeck
2014-04-15 20:06       ` [PATCH v4 2/2] x86: intel-mid: add watchdog platform code for Merrifield David Cohen
2014-04-15 20:09         ` David Cohen
2014-04-15 21:13           ` Guenter Roeck
2014-04-15 21:17             ` David Cohen
2014-04-15 21:35               ` Guenter Roeck
2014-04-15 21:39                 ` David Cohen
2014-04-15 22:20         ` [PATCH v4.1 " David Cohen
2014-04-16  0:16           ` Guenter Roeck

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=20140409151822.GA21864@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=alexander.stein@systec-electronic.com \
    --cc=david.a.cohen@linux.intel.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=wim@iguana.be \
    --cc=x86@kernel.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