All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Corentin Chary <corentin.chary@gmail.com>,
	Ike Panhc <ike.pan@canonical.com>,
	linux-kernel@vger.kernel.org, mjg@redhat.com,
	platform-driver-x86@vger.kernel.org
Subject: Re: [RESEND][PATCH 0/5] Support for the TS-5500 board
Date: Wed, 10 Aug 2011 15:09:19 -0400	[thread overview]
Message-ID: <20110810150919.39519e62@v0nbox> (raw)
In-Reply-To: <1312986047.2989.47.camel@i7.infradead.org>

On Wed, 10 Aug 2011 15:20:46 +0100,
David Woodhouse <dwmw2@infradead.org> wrote:
> Just expose these devices in the device-tree. You shouldn't *need* a
> new MTD device driver; physmap_of should be just fine.

I didn't write a new MTD device driver, but just moved the already
existing one to the ts5500 platform directory. The point is that my
TS-5500 doesn't have this flash, so I couldn't try. The fifth patch
from this set could just be ignored.

> If your bootloader doesn't pass one, your platform-specific code
> should just register its own device-tree blob during early boot. And
> your device drivers should just match against the devices therein.

I'm a bit confused with what should be done for the support for an
embedded platform (X86-based) like this TS-5500. Is the actual code
hierarchy OK? What is the impact of adding a device-tree to this code?

Thanks,
Vivien.

  reply	other threads:[~2011-08-10 19:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 21:10 [RESEND][PATCH 0/5] Support for the TS-5500 board Vivien Didelot
2011-07-28 21:10 ` [RESEND][PATCH 1/5] x86: base support for TS-5500 Single Board Computer Vivien Didelot
2011-07-28 21:10 ` [RESEND][PATCH 2/5] gpio: add support for TS-5500 GPIO Vivien Didelot
2011-07-28 21:10 ` [RESEND][PATCH 3/5] leds: add support for TS-5500 LED Vivien Didelot
2011-07-28 21:10 ` [RESEND][PATCH 4/5] adc: add support for TS-5500 ADC Vivien Didelot
2011-07-28 21:10 ` [RESEND][PATCH 5/5] mtd: move support for TS-5500 MTD Vivien Didelot
2011-08-10  3:32 ` [RESEND][PATCH 0/5] Support for the TS-5500 board Vivien Didelot
2011-08-10  5:53   ` Ike Panhc
2011-08-10  6:18     ` Corentin Chary
2011-08-10 14:06       ` Vivien Didelot
2011-08-10 14:20         ` David Woodhouse
2011-08-10 19:09           ` Vivien Didelot [this message]
2011-08-12 14:26             ` Vivien Didelot
2011-08-24 13:42               ` Matthew Garrett
2011-08-24 15:16                 ` Vivien Didelot

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=20110810150919.39519e62@v0nbox \
    --to=vivien.didelot@savoirfairelinux.com \
    --cc=corentin.chary@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=ike.pan@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=platform-driver-x86@vger.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 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.