From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm: omap: hwmod: add a new addr space in otg for writing to control module
Date: Thu, 6 Sep 2012 12:56:07 -0700 [thread overview]
Message-ID: <20120906195607.GB1303@atomide.com> (raw)
In-Reply-To: <20120906171803.GA30717@arwen.pp.htv.fi>
* Felipe Balbi <balbi@ti.com> [120906 10:23]:
> Hi,
>
> On Thu, Sep 06, 2012 at 08:13:03PM +0300, Felipe Balbi wrote:
> > Hi,
> >
> > On Thu, Sep 06, 2012 at 09:04:58PM +0530, Vaibhav Hiremath wrote:
> > >
> > >
> > > On 9/6/2012 8:25 PM, Kishon Vijay Abraham I wrote:
> > > > The mailbox register for usb otg in omap is present in control module.
> > > > On detection of any events VBUS or ID, this register should be written
> > > > to send the notification to musb core.
> > > >
> > > > Till we have a separate control module driver to write to control module,
> > > > omap2430 will handle the register writes to control module by itself. So
> > > > a new address space to represent this control module register is added
> > > > to usb_otg_hs.
> > > >
> > > > Cc: Benoit Cousson <b-cousson@ti.com>
> > > > Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> > > > ---
> > > > arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 5 +++++
> > > > 1 file changed, 5 insertions(+)
> > > >
> > > > diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> > > > index 242aee4..02341bc 100644
> > > > --- a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> > > > +++ b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
> > > > @@ -5890,6 +5890,11 @@ static struct omap_hwmod_addr_space omap44xx_usb_otg_hs_addrs[] = {
> > > > .pa_end = 0x4a0ab003,
> > > > .flags = ADDR_TYPE_RT
> > > > },
> > > > + {
> > > > + .pa_start = 0x4a00233c,
> > > > + .pa_end = 0x4a00233f,
> > > > + .flags = ADDR_TYPE_RT
> > > > + },
> > >
> > > I do not have any objection/comment here, but I believe this is control
> > > module address space required for USB module, right?
> > > I am not sure this is right way of accessing control module space.
> > > Actually Control Module Access required for drivers is one of the
> > > blocking issue we have currently.
> > >
> > > Also there was some effort put up by 'Konstantine' to convert Control
> > > module to MFD driver, I haven't seen any further update on it. But it
> > > would be good to check with him.
> >
> > this was an agreement with Benoit since we already lost a couple merge
> > windows for this patchset. We agreed to wait until -rc4 for SCM driver
> > and if it wasn't ready, we'd go ahead with this and SCM author would fix
> > it up on a patch converting users to new SCM driver.
>
> Tony, can I get your Acked-by to this patch so I can take it together
> with the rest of the series ? Thanks
>
> ps: I'll apply this to my 'musb' branch which is immutable, so it's safe
> to merge it into your tree once I apply.
It would be best if this got acked by Benoit and Paul as they may
have some other patches queued up. I'll ack if they ack ;)
Tony
next prev parent reply other threads:[~2012-09-06 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 14:55 [PATCH 0/3] omap: musb: Add device tree support Kishon Vijay Abraham I
2012-09-06 14:55 ` [PATCH 1/3] arm: omap: hwmod: add a new addr space in otg for writing to control module Kishon Vijay Abraham I
2012-09-06 15:34 ` Vaibhav Hiremath
2012-09-06 17:13 ` Felipe Balbi
2012-09-06 17:18 ` Felipe Balbi
2012-09-06 19:56 ` Tony Lindgren [this message]
2012-09-10 15:58 ` Felipe Balbi
2012-09-10 16:17 ` Benoit Cousson
2012-09-10 16:43 ` Felipe Balbi
2012-09-11 8:52 ` ABRAHAM, KISHON VIJAY
2012-09-07 4:57 ` Hiremath, Vaibhav
2012-09-06 14:55 ` [PATCH 2/3] usb: musb: omap: write directly to mailbox instead of using phy Kishon Vijay Abraham I
2012-09-06 14:55 ` [PATCH 3/3] usb: musb: omap: Add device tree support for omap musb glue Kishon Vijay Abraham I
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=20120906195607.GB1303@atomide.com \
--to=tony@atomide.com \
--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).