devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
To: Jean-Christophe PLAGNIOL-VILLARD
	<plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org>
Cc: devicetree-discuss
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
	Bo Shen <voice.shen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: dts: question about how to configure PIO used as i2c irq
Date: Mon, 15 Oct 2012 10:07:37 +0200	[thread overview]
Message-ID: <507BC449.6070203@atmel.com> (raw)
In-Reply-To: <20121015055720.GQ12801-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>

On 10/15/2012 07:57 AM, Jean-Christophe PLAGNIOL-VILLARD :
> On 10:53 Mon 15 Oct     , Bo Shen wrote:
>> Hi All,
>>   When moving atmel qt1070 linux driver with DT support. The atmel
>> qt1070 is an I2C device. I meet the following questions.
>>
>>   The qt1070 DT node
>>   --<--------------
>>   qt1070: keyboard@1b {
>>         compatible = "atmel,qt1070";
>>         reg = <0x1b>;
>>         interrupt-parent = <&pioA>;
>>         interrupts = <7 0x0>;
>>   };
>>   -->--------------
>>
>>   DT will parse this node and map irq, the i2c_client->irq. This can
>> be used directly in atmel qt1070 driver. However, the PIO which used
>> as irq need configure as a PIO input. Now, we can not use
>> irq_to_gpio() function to convert irq to gpio. So, if we can not
>> configure this gpio.
>>
>>   If we configure the pio in board-dt.c, I think this is not a good
>> place. For example, if the kernel image support multiplatform, while
>> on these platform, using different pio for qt1070, so this will
>> cause only one platform can use qt1070.
>>
>>   So, for this question, how should I solve it? Would you please
>> give me some advice?
> I already reply you in private 4 times

Yes, but maybe it is because it was not well explained, or not developed
to the proper extend... So, please do not make these remarks: if the
conversation was private, it is not necessary to recall that here. Maybe
Voice is looking for help from someone else?

> you have only 2 choice pass the gpio and manage in c
> or configure the gpio as input in the xlate or map of the gpio drivers and the
> mux via pinctrl

Can you please develop a bit more: which xlate? How to tell the gpio
driver about the map? Can you provide an example?

Bye,
-- 
Nicolas Ferre

  parent reply	other threads:[~2012-10-15  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  2:53 dts: question about how to configure PIO used as i2c irq Bo Shen
     [not found] ` <507B7AC3.7090904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-10-15  5:57   ` Jean-Christophe PLAGNIOL-VILLARD
     [not found]     ` <20121015055720.GQ12801-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2012-10-15  8:07       ` Nicolas Ferre [this message]
2012-10-19  6:56         ` Bo Shen

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=507BC449.6070203@atmel.com \
    --to=nicolas.ferre-aife0yeh4naavxtiumwx3w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=plagnioj-sclMFOaUSTBWk0Htik3J/w@public.gmane.org \
    --cc=voice.shen-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).