linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sre@ring0.de (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v1 2/5] misc: tda8026: Add NXP TDA8026 PHY driver
Date: Tue, 7 Jan 2014 12:45:53 +0100	[thread overview]
Message-ID: <20140107114552.GA900@earth.universe> (raw)
In-Reply-To: <52CBA075.8080506@ti.com>

On Tue, Jan 07, 2014 at 12:06:37PM +0530, Satish Patel wrote:
> >> +       if (pdata->irq == 0) {
> >> +               /* look for the field irq-gpio in DT */
> >> +               irq_gpio = of_get_named_gpio(np, "irq-gpio", 0);
> >> +               if (!gpio_is_valid(irq_gpio)) {
> >> +                       dev_err(dev, "Failed to get irq gpio,\n");
> >> +                       return -EIO;
> >> +               }
> > 
> > This is horrible. If the gpio controller can act as an irq controller
> 
> No it's not true. Let me clarify the signal flow,
> 
> Pins => GPIO => GPIO BANK => Interrupt controller => CPU/MPU

This is done automatically if you use the gpio controller as
interrupt source (here with GPIO line 22 as example):

device-tree-node {
    interrupts-extended = <&gpio1 22>;
};

alternatively, but then the irqs from the normal irq controller
can't be used:

device-tree-node {
    interrupt-parent = <&gpio1>;
    interrupts = <22>;
};

-- Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140107/bc4b2c23/attachment.sig>

  reply	other threads:[~2014-01-07 11:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 12:07 [RFC PATCH v1 0/5] Smart Card(SC) interface, TI USIM & NxP SC phy driver Satish Patel
2014-01-06 12:07 ` [RFC PATCH v1 1/5] sc_phy:SmartCard(SC) PHY interface to SC controller Satish Patel
2014-01-06 12:07 ` [RFC PATCH v1 2/5] misc: tda8026: Add NXP TDA8026 PHY driver Satish Patel
2014-01-06 15:30   ` Mark Rutland
2014-01-07  6:36     ` Satish Patel
2014-01-07 11:45       ` Sebastian Reichel [this message]
2014-01-06 12:07 ` [RFC PATCH v1 3/5] char: ti-usim: Add driver for USIM module on AM43xx Satish Patel
2014-01-06 12:07 ` [RFC PATCH v1 4/5] ARM: dts: AM43xx: DT entries added for ti-usim Satish Patel
2014-01-06 12:07 ` [RFC PATCH v1 5/5] ARM: dts: AM43xx-epos-evm: DT entries " Satish Patel

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=20140107114552.GA900@earth.universe \
    --to=sre@ring0.de \
    --cc=linux-arm-kernel@lists.infradead.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).