All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Nate Case <ncase@xes-inc.com>
Cc: devicetree-discuss@ozlabs.org, linux-embedded@vger.kernel.org,
	linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org
Subject: Re: [RFC] misc/at24: add experimental OF support for the generic  eeprom driver
Date: Fri, 9 Oct 2009 10:13:58 -0600	[thread overview]
Message-ID: <fa686aa40910090913p719ef4cdqe480ae01bd4ab6c8@mail.gmail.com> (raw)
In-Reply-To: <1255095793.16018.32.camel@localhost.localdomain>

On Fri, Oct 9, 2009 at 7:43 AM, Nate Case <ncase@xes-inc.com> wrote:
> On Fri, 2009-10-09 at 07:14 +0200, Wolfram Sang wrote:
>> And while doing this and figuring the pro/cons of those methods, I
>> stumbled over this commit:
>>
>>         gpio: pca953x: Get platform_data from OpenFirmware
>>         (1965d30356c1c65660ba3330927671cfe81acdd5)
>
> Aside from any issues you have with the properties themselves, what's
> your take on this approach?

As I mentioned in an earlier email, I don't think quite the right form
has been found yet, but I like the direction things are moving.

> Personally, I just got tired of waiting for someone else to solve the
> pdata/OF problem.  So I submitted that commit as an attempt at something
> very simple and unobtrusive to the device driver itself.  It seems
> pretty clean to me, but I'm curious to see if others have any better
> ideas.

Yup, that's good.  Between Anton's, Wolfram's and your work things are
going the right way.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

WARNING: multiple messages have this Message-ID (diff)
From: Grant Likely <grant.likely@secretlab.ca>
To: Nate Case <ncase@xes-inc.com>
Cc: devicetree-discuss@ozlabs.org, linux-embedded@vger.kernel.org,
	linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org
Subject: Re: [RFC] misc/at24: add experimental OF support for the generic eeprom driver
Date: Fri, 9 Oct 2009 10:13:58 -0600	[thread overview]
Message-ID: <fa686aa40910090913p719ef4cdqe480ae01bd4ab6c8@mail.gmail.com> (raw)
In-Reply-To: <1255095793.16018.32.camel@localhost.localdomain>

On Fri, Oct 9, 2009 at 7:43 AM, Nate Case <ncase@xes-inc.com> wrote:
> On Fri, 2009-10-09 at 07:14 +0200, Wolfram Sang wrote:
>> And while doing this and figuring the pro/cons of those methods, I
>> stumbled over this commit:
>>
>>         gpio: pca953x: Get platform_data from OpenFirmware
>>         (1965d30356c1c65660ba3330927671cfe81acdd5)
>
> Aside from any issues you have with the properties themselves, what's
> your take on this approach?

As I mentioned in an earlier email, I don't think quite the right form
has been found yet, but I like the direction things are moving.

> Personally, I just got tired of waiting for someone else to solve the
> pdata/OF problem.  So I submitted that commit as an attempt at something
> very simple and unobtrusive to the device driver itself.  It seems
> pretty clean to me, but I'm curious to see if others have any better
> ideas.

Yup, that's good.  Between Anton's, Wolfram's and your work things are
going the right way.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

WARNING: multiple messages have this Message-ID (diff)
From: Grant Likely <grant.likely@secretlab.ca>
To: Nate Case <ncase@xes-inc.com>
Cc: devicetree-discuss@ozlabs.org, linux-embedded@vger.kernel.org,
	linuxppc-dev@ozlabs.org, linux-i2c@vger.kernel.org
Subject: Re: [RFC] misc/at24: add experimental OF support for the generic eeprom driver
Date: Fri, 9 Oct 2009 10:13:58 -0600	[thread overview]
Message-ID: <fa686aa40910090913p719ef4cdqe480ae01bd4ab6c8@mail.gmail.com> (raw)
In-Reply-To: <1255095793.16018.32.camel@localhost.localdomain>

On Fri, Oct 9, 2009 at 7:43 AM, Nate Case <ncase@xes-inc.com> wrote:
> On Fri, 2009-10-09 at 07:14 +0200, Wolfram Sang wrote:
>> And while doing this and figuring the pro/cons of those methods, I
>> stumbled over this commit:
>>
>> =A0 =A0 =A0 =A0 gpio: pca953x: Get platform_data from OpenFirmware
>> =A0 =A0 =A0 =A0 (1965d30356c1c65660ba3330927671cfe81acdd5)
>
> Aside from any issues you have with the properties themselves, what's
> your take on this approach?

As I mentioned in an earlier email, I don't think quite the right form
has been found yet, but I like the direction things are moving.

> Personally, I just got tired of waiting for someone else to solve the
> pdata/OF problem. =A0So I submitted that commit as an attempt at somethin=
g
> very simple and unobtrusive to the device driver itself. =A0It seems
> pretty clean to me, but I'm curious to see if others have any better
> ideas.

Yup, that's good.  Between Anton's, Wolfram's and your work things are
going the right way.

g.

--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  parent reply	other threads:[~2009-10-09 16:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 14:04 [RFC] misc/at24: add experimental OF support for the generic eeprom driver Wolfram Sang
2009-10-08 14:33 ` Anton Vorontsov
     [not found]   ` <20091008143301.GA6084-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>
2009-10-08 14:53     ` Grant Likely
2009-10-08 14:53       ` Grant Likely
2009-10-08 15:10       ` Anton Vorontsov
2009-10-08 15:48         ` Grant Likely
2009-10-08 15:48           ` Grant Likely
2009-10-08 15:48           ` Grant Likely
2009-10-08 20:27           ` Wolfram Sang
2009-10-08 20:27             ` Wolfram Sang
2009-10-09  5:14             ` Wolfram Sang
2009-10-09  5:14               ` Wolfram Sang
     [not found]               ` <20091009051409.GA2361-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-09  5:40                 ` Grant Likely
2009-10-09  5:40                   ` Grant Likely
2009-10-09  5:40                   ` Grant Likely
2009-10-09 14:01                   ` Nate Case
2009-10-09 14:01                     ` Nate Case
2009-10-09 16:09                     ` Grant Likely
2009-10-09 16:09                       ` Grant Likely
2009-10-09 16:09                       ` Grant Likely
2009-10-09 16:20                     ` Wolfram Sang
2009-10-09 16:20                       ` Wolfram Sang
2009-10-09 13:43               ` Nate Case
2009-10-09 16:12                 ` Wolfram Sang
2009-10-09 16:12                   ` Wolfram Sang
2009-10-09 16:13                 ` Grant Likely [this message]
2009-10-09 16:13                   ` Grant Likely
2009-10-09 16:13                   ` Grant Likely
     [not found]           ` <fa686aa40910080848r459c47baob73fc70a95a08604-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-08 22:20             ` Anton Vorontsov
2009-10-08 22:20               ` Anton Vorontsov
2009-10-09  6:37               ` Grant Likely
2009-10-09  6:37                 ` Grant Likely
2009-10-09  6:37                 ` Grant Likely
2009-10-08 14:37 ` Grant Likely
     [not found]   ` <fa686aa40910080737l5b21654cw9c8f7426f9faf7c3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-08 20:48     ` Wolfram Sang
2009-10-08 20:48       ` Wolfram Sang
     [not found]       ` <20091008204808.GB8116-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-08 22:59         ` Grant Likely
2009-10-08 22:59           ` Grant Likely

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=fa686aa40910090913p719ef4cdqe480ae01bd4ab6c8@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ncase@xes-inc.com \
    /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.