devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 김봉규 <bongkyu.kim-Hm3cg6mZ9cc@public.gmane.org>
To: 'Rob Herring' <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH] of/i2c: support more interrupt specifiers
Date: Thu, 22 Nov 2012 14:50:28 +0900	[thread overview]
Message-ID: <002b01cdc875$470e22d0$d52a6870$@lge.com> (raw)
In-Reply-To: <50ACD9F2.40207-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 11/21/2012 10:41 PM, Rob Herring wrote:

> On 11/21/2012 02:58 AM, Bongkyu Kim wrote:
> > This patch supports more interrupt specifiers for i2c client.
> 
> Why?
> 

If we are registering a device has 2 interrupts like the below,
	i2c@f9968000 {
		lsm330_acc@1D {
			compatible = "ST,lsm330_acc",
			interrupts = <73 0x2 65 0x2>, /* #interrupt-cells =
<2> */
		};
	};

we can't use second irq(65) in a driver because of mapping first interrupt
only.
If second irq(65) is mapped, we can use by gpio_to_irq() function at a
driver.
So, I think that all interrupt specifiers should be parsed and mapped
if DT's interrupts property is allowed several interrupt specifiers.

> > Signed-off-by: Bongkyu Kim <bongkyu.kim-Hm3cg6mZ9cc@public.gmane.org>
> > ---
> >  drivers/of/of_i2c.c | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/of/of_i2c.c b/drivers/of/of_i2c.c
> > index 3550f3b..c6d9b7e 100644
> > --- a/drivers/of/of_i2c.c
> > +++ b/drivers/of/of_i2c.c
> > @@ -34,6 +34,7 @@ void of_i2c_register_devices(struct i2c_adapter
> *adap)
> >  		struct dev_archdata dev_ad = {};
> >  		const __be32 *addr;
> >  		int len;
> > +		int nr = 0;
> >
> >  		dev_dbg(&adap->dev, "of_i2c: register %s\n", node-
> >full_name);
> >
> > @@ -57,7 +58,9 @@ void of_i2c_register_devices(struct i2c_adapter
> *adap)
> >  			continue;
> >  		}
> >
> > -		info.irq = irq_of_parse_and_map(node, 0);
> > +		info.irq = irq_of_parse_and_map(node, nr++);
> > +		while (irq_of_parse_and_map(node, nr))
> > +			nr++;
> 
> What's the point if you are just discarding the interrupt number? If
> this is needed, then shouldn't you fix i2c_board_info first?
> 
> Rob
> 

It is better that i2c_board_info will be fixed.
But, if it will be fixed, all i2c client drivers should be changed.
I think there're so many i2c drivers currently.
In my opinion, do not assign to i2c_board_info and just map for all
interrupts is the better.

Thanks,
Bongkyu.

> >  		info.of_node = of_node_get(node);
> >  		info.archdata = &dev_ad;
> >
> >

  parent reply	other threads:[~2012-11-22  5:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21  8:58 [PATCH] of/i2c: support more interrupt specifiers Bongkyu Kim
2012-11-21 13:41 ` Rob Herring
     [not found]   ` <50ACD9F2.40207-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-22  5:50     ` 김봉규 [this message]
2012-11-26  5:11   ` Bongkyu Kim
2012-11-26 14:08     ` 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='002b01cdc875$470e22d0$d52a6870$@lge.com' \
    --to=bongkyu.kim-hm3cg6mz9cc@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@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 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).