All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linus.walleij@linaro.org, grant.likely@secretlab.ca,
	devicetree-discuss@lists.ozlabs.org,
	linux-kernel@vger.kernel.org, spear-devel@list.st.com,
	Vipul Kumar Samar <vipulkumar.samar@st.com>
Subject: Re: [PATCH] gpio: stmpe: Add DT support for stmpe gpio
Date: Fri, 23 Nov 2012 10:41:40 +0000	[thread overview]
Message-ID: <20121123104140.GP17471@gmail.com> (raw)
In-Reply-To: <20121123103400.GO17471@gmail.com>

> >  static struct mfd_cell stmpe_gpio_cell = {
> >  	.name		= "stmpe-gpio",
> > +	.of_compatible	= "st,stmpe-gpio",
> 
> There's no need for any of the STMPE to have their own compatible
> string, as they are MFD devices. They are registered as platform
> devices from the MFD subsystem.

Whoops, I've written this in the wrong place. 

Sorry, for the confusion. It does need to be here.

> >  	.resources	= stmpe_gpio_resources,
> >  	.num_resources	= ARRAY_SIZE(stmpe_gpio_resources),
> >  };
> >  
> >  static struct mfd_cell stmpe_gpio_cell_noirq = {
> >  	.name		= "stmpe-gpio",
> > +	.of_compatible	= "st,stmpe-gpio",

... and here.

> > +++ b/Documentation/devicetree/bindings/gpio/gpio-stmpe.txt
> > @@ -0,0 +1,18 @@
> > +STMPE gpio
> > +----------
> > +
> > +Required properties:
> > + - compatible: "st,stmpe-gpio"

... but this is wrong.

> > +Example:
> > +	stmpe_gpio {
> > +		compatible = "st,stmpe-gpio";
> > +		st,norequest-mask = <0x20>;	//gpio 5 can't be used
> > +	};

As is the example.

So will be the the DT - if you've already written it.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2012-11-23 10:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23  5:51 [PATCH] gpio: stmpe: Add DT support for stmpe gpio Viresh Kumar
2012-11-23 10:34 ` Lee Jones
2012-11-23 10:41   ` Lee Jones [this message]
     [not found]     ` <20121123104140.GP17471-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-23 10:47       ` Viresh Kumar
2012-11-23 10:47         ` Viresh Kumar
2012-11-23 10:43   ` Viresh Kumar
2012-11-23 12:14     ` Lee Jones
     [not found]       ` <20121123121413.GB22268-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-23 12:25         ` Viresh Kumar
2012-11-23 12:25           ` Viresh Kumar
2012-11-23 15:45           ` Lee Jones
2012-11-23 12:30       ` Shiraz Hashim
2012-11-23 12:30         ` Shiraz Hashim
2012-11-26 11:28         ` Lee Jones
2012-11-26 11:28           ` Lee Jones
2012-11-26 11:32           ` Shiraz Hashim
2012-11-26 11:32             ` Shiraz Hashim
2012-12-01 16:35             ` Linus Walleij
2012-12-01 18:31               ` Shiraz Hashim
2012-12-01 19:34           ` Linus Walleij
     [not found]             ` <CACRpkda6=UPW+Xy9ztkAtFvCMySt4iR8YabYNNTdnZBpVc98rQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-12-01 19:55               ` Linus Walleij
2012-12-01 19:55                 ` Linus Walleij

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=20121123104140.GP17471@gmail.com \
    --to=lee.jones@linaro.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spear-devel@list.st.com \
    --cc=vipulkumar.samar@st.com \
    --cc=viresh.kumar@linaro.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.