linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nate Case <ncase@xes-inc.com>
To: Grant Likely <grant.likely@secretlab.ca>
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, 09 Oct 2009 09:01:11 -0500	[thread overview]
Message-ID: <1255096871.16018.49.camel@localhost.localdomain> (raw)
In-Reply-To: <fa686aa40910082240w7fb2a194tcc80e7afe182e781@mail.gmail.com>

On Thu, 2009-10-08 at 23:40 -0600, Grant Likely wrote:
> For your future reference, patches that look at the device tree should
> also cc: devicetree-discuss@lists.ozlabs.org so that new bindings can
> be reviewed and common mistakes can be avoided.  It is expected that
> new device tree bindings are accompanied with documentation describing
> what the binding is for and how it should be used (see
> Documentation/powerpc/dts-bindings).
> 
> I know this change is already in mainline, but can you please post the
> device tree fragment that you're using to describe this chip?  I want
> to make sure we don't get stuck with things in the kernel that will be
> hard to maintain in the long term.

Hi Grant,

Sorry for neglecting to include devicetree-discuss on that one.  I was
in fact aware of this list, and subscribe to it.  I really just forgot
in this case.

I also have a documentation patch for it that went along with it, but it
wasn't ready in time and so it's been sitting in our local patch queue.
I can submit that soon,  but it probably makes sense for Wolfram to
voice whatever his concerns were about "questionable" properties before
I document what's there.

Here's an example device tree node for this case:

               gpio1: gpio@18 {
                        compatible = "nxp,pca9557";
                        reg = <0x18>;
                        #gpio-cells = <2>;
                        gpio-controller;
                        polarity = <0x00>;
               };

In this case, the linux,gpio-base property wasn't specified.  But, the
use case is identical to the pdata->gpio_base field.  "polarity" is used
for specifying polarity inversion for each line, and is in the same
format of the 'polarity inversion' register on the chip.  My reasoning
in the property naming was as follows:

    linux,gpio-base: Linux-specific as it relates to internal GPIO
                     numbering.  So, it's prefixed with "linux,"
    polarity: Dictated by how hardware is wired up, so it's needed
              regardless of the OS.

- Nate

  reply	other threads:[~2009-10-09 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1255010672-21656-1-git-send-email-w.sang@pengutronix.de>
     [not found] ` <20091008143301.GA6084@oksana.dev.rtsoft.ru>
     [not found]   ` <fa686aa40910080753v6f597b0h4ce835db9f7a653@mail.gmail.com>
     [not found]     ` <20091008151007.GA21328@oksana.dev.rtsoft.ru>
2009-10-08 15:48       ` [RFC] misc/at24: add experimental OF support for the generic eeprom driver Grant Likely
2009-10-08 20:27         ` 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 14:01                 ` Nate Case [this message]
2009-10-09 16:09                   ` Grant Likely
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:13               ` Grant Likely
     [not found]         ` <fa686aa40910080848r459c47baob73fc70a95a08604-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-08 22:20           ` Anton Vorontsov
2009-10-09  6:37             ` 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=1255096871.16018.49.camel@localhost.localdomain \
    --to=ncase@xes-inc.com \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).