linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: mach-shmobile: mackerel: add renesas_usbhs support for USB1
Date: Wed, 25 May 2011 02:57:02 +0000	[thread overview]
Message-ID: <20110525025701.GI14329@linux-sh.org> (raw)
In-Reply-To: <w3phbc5yjly.wl%kuninori.morimoto.gx@renesas.com>

On Wed, May 25, 2011 at 11:49:25AM +0900, Kuninori Morimoto wrote:
> CN31 USB1 can be Host/Function, and it can use IRQ8 as USB-phy.
> This mean we can power off it if...
>  - while USB1 is disconnected.
>  - USB-Function is selected.
>  - driver is supporting it.
> 
> OTOH, CN22 USB0 which is only USB Function
> can not use USB-phy interrupt (IRQ7) on mackerel board.
> Because IRQ7 is already used by Touchscreen,
> and it is impossible to use cascaded IRQ7.
> 
Why is it impossible to have an IRQ7 demux?

> renesas_usbhs driver which is supporting USB-Function
> is supporting USB power off when disconnect.
> mackerel board will use renesas_usbhs driver as
> USB-Function on CN31 if it have CONFIG_USB_RENESAS_USBHS.
> And r8a66597_hcd will be used as USB Host if it have CONFIG_USB_R8A66597_HCD.
> 
> But you can not select both CONFIG_USB_R8A66597_HCD and
> CONFIG_USB_RENESAS_USBHS in same time for now.
> Because IRQ8 will be requested in different driver.
> 
Is there some particular reason why IRQF_SHARED isn't sufficient for
working around this? Since you're leveraging the IORESOURCE PnP IRQ bits
anyways, you could easily just or in IORESOURCE_IRQ_SHAREABLE and
translate that in to an IRQF_SHARED at request_irq() time for the cases
that need it.

  parent reply	other threads:[~2011-05-25  2:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15  5:03 [PATCH 2/2] ARM: mach-shmobile: mackerel: fixup memory initialize for Kuninori Morimoto
2011-02-17  0:41 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: fixup memory Simon Horman
2011-02-17  1:11 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: fixup memory initialize Kuninori Morimoto
2011-05-25  2:49 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: add renesas_usbhs support Kuninori Morimoto
2011-05-25  2:57 ` Paul Mundt [this message]
2011-05-25  4:24 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: add renesas_usbhs Kuninori Morimoto
2011-05-25  5:40 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: add renesas_usbhs support for USB1 Paul Mundt
2012-03-01  4:25 ` [PATCH 2/2] ARM: mach-shmobile: mackerel: Add FSI DMAEngine support Kuninori Morimoto

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=20110525025701.GI14329@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.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).