From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Roger Quadros <rogerq@ti.com>, balbi@ti.com
Cc: tony@atomide.com, Joao.Pinto@synopsys.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 4/9] usb: dwc3: core: Adapt to named interrupts
Date: Wed, 8 Jul 2015 16:06:48 +0300 [thread overview]
Message-ID: <559D2068.90208@cogentembedded.com> (raw)
In-Reply-To: <1436351795-28556-1-git-send-email-rogerq@ti.com>
Hello.
On 7/8/2015 1:36 PM, Roger Quadros wrote:
> From: Felipe Balbi <balbi@ti.com>
> Add support to use interrupt names,
> Following are the interrupt names
> Peripheral Interrupt - peripheral
> HOST Interrupt - host
> OTG Interrupt - otg
> [Roger Q]
> - If any of these are missing we use the
> first available IRQ resource so that we don't
> break with older DTBs.
> - Use gadget_irq in gadget driver.
> Signed-off-by: Felipe Balbi <balbi@ti.com>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
> ---
> drivers/usb/dwc3/core.c | 12 ++++++++++++
> drivers/usb/dwc3/core.h | 7 +++++++
> drivers/usb/dwc3/gadget.c | 2 +-
> 3 files changed, 20 insertions(+), 1 deletion(-)
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index a7498e0..7b33d7b 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -941,6 +941,18 @@ static int dwc3_probe(struct platform_device *pdev)
> dwc->xhci_resources[1].flags = res->flags;
> dwc->xhci_resources[1].name = res->name;
>
> + dwc->otg_irq = platform_get_irq_byname(pdev, "otg");
> + if (!dwc->otg_irq)
The usual mistake repeated again: that function reutrns error # on
failure, not 0.
> + dwc->otg_irq = res->start;
> +
> + dwc->gadget_irq = platform_get_irq_byname(pdev, "peripheral");
> + if (!dwc->gadget_irq)
> + dwc->gadget_irq = res->start;
Likewise.
> +
> + dwc->xhci_irq = platform_get_irq_byname(pdev, "host");
> + if (!dwc->xhci_irq)
Likewise.
[...]
WBR, Sergei
next prev parent reply other threads:[~2015-07-08 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 10:31 [PATCH v3 0/9] usb: dwc3: add dual-role support Roger Quadros
2015-07-08 10:31 ` [PATCH v3 1/9] " Roger Quadros
2015-07-08 10:31 ` [PATCH v3 2/9] usb: dwc3: core.h: add some register definitions Roger Quadros
2015-07-08 10:36 ` [PATCH v3 3/9] usb: dwc3: dwc3-omap: Make the wrapper interrupt shared Roger Quadros
2015-07-08 10:36 ` [PATCH v3 4/9] usb: dwc3: core: Adapt to named interrupts Roger Quadros
2015-07-08 13:06 ` Sergei Shtylyov [this message]
2015-07-08 14:43 ` Roger Quadros
2015-07-08 10:36 ` [PATCH v3 5/9] usb: dwc3: core: make dual-role work with OTG irq Roger Quadros
2015-07-08 10:36 ` [PATCH v3 6/9] usb: dwc3: save/restore OTG registers during suspend/resume Roger Quadros
2015-07-08 10:37 ` [PATCH v3 7/9] usb: dwc3: gadget: Fix suspend/resume during dual-role mode Roger Quadros
2015-07-08 10:37 ` [PATCH v3 8/9] usb: dwc3: core: Prevent otg events from disabling themselves Roger Quadros
2015-07-08 10:37 ` [PATCH v3 9/9] usb: dwc3: core: don't break during suspend/resume while we're dual-role Roger Quadros
2015-07-08 13:11 ` Sergei Shtylyov
2015-07-08 14:44 ` Roger Quadros
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=559D2068.90208@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=Joao.Pinto@synopsys.com \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=tony@atomide.com \
/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