From: Thierry Reding <thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Linus Walleij
<linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH 2/2] gpio: Add Avionic Design N-bit GPIO expander support
Date: Thu, 7 Jun 2012 10:40:15 +0200 [thread overview]
Message-ID: <20120607084015.GA27764@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <20120526004805.92B373E1E4E@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1092 bytes --]
* Grant Likely wrote:
> On Mon, 21 May 2012 12:20:32 +0200, Thierry Reding <thierry.reding@avionic-design.de> wrote:
> > * Grant Likely wrote:
> > > On Thu, 12 Apr 2012 13:24:18 +0200, Thierry Reding <thierry.reding@avionic-design.de> wrote:
[...]
> > > > +struct adnp_platform_data {
> > > > + unsigned gpio_base;
> > > > + unsigned nr_gpios;
> > > > + int irq_base;
> > > > + const char *const *names;
> > > > +};
> > >
> > > From the start this is a DT enabled driver. There should be no reason
> > > to also include platform_data support.
> >
> > I thought it might be a good idea to support both for now. There have been
> > some discussions that the device tree should be just an alternative source
> > for platform data, the main argument being that platform data could be used
> > to overwrite data provided via DT.
>
> Unless you have an *actual* user of platform_data, don't borrow
> trouble by adding it.
If I make the driver DT-only I should probably add a "select OF" to it's
Kconfig entry, right? Or should it rather be "depends on OF"?
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 192 bytes --]
_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
next prev parent reply other threads:[~2012-06-07 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 11:24 [PATCH 1/2] of: Add Avionic Design vendor prefix Thierry Reding
[not found] ` <1334229858-1665-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2012-04-12 11:24 ` [PATCH 2/2] gpio: Add Avionic Design N-bit GPIO expander support Thierry Reding
[not found] ` <1334229858-1665-2-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2012-05-11 23:47 ` Grant Likely
2012-05-21 10:20 ` Thierry Reding
[not found] ` <20120521102032.GA27686-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-05-26 0:48 ` Grant Likely
2012-06-07 8:40 ` Thierry Reding [this message]
[not found] ` <20120607084015.GA27764-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2012-06-10 6:43 ` Arnd Bergmann
2012-05-22 13:57 ` [PATCH 1/2] of: Add Avionic Design vendor prefix Thierry Reding
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=20120607084015.GA27764@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding-rm9k5ik7kjkj5m59nbduvrnah6klmebb@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@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 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.