From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: George Cherian <george.cherian@ti.com>
Cc: linux-usb@vger.kernel.org, balbi@ti.com,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
linux-omap@vger.kernel.org, kishon@ti.com
Subject: Re: [PATCH v2 1/4] usb: phy: phy-omap-control: Add API to power and wakeup
Date: Mon, 29 Jul 2013 16:25:17 +0200 [thread overview]
Message-ID: <20130729142517.GA827@linutronix.de> (raw)
In-Reply-To: <1374237277-17769-2-git-send-email-george.cherian@ti.com>
* George Cherian | 2013-07-19 18:04:34 [+0530]:
>diff --git a/drivers/usb/phy/phy-omap-control.c b/drivers/usb/phy/phy-omap-control.c
>index 1419ced..4f2502c 100644
>--- a/drivers/usb/phy/phy-omap-control.c
>+++ b/drivers/usb/phy/phy-omap-control.c
>@@ -46,6 +46,73 @@ struct device *omap_get_control_dev(void)
> EXPORT_SYMBOL_GPL(omap_get_control_dev);
>
> /**
>+ * omap_control_am335x_phy_wkup - PHY wakeup on/off using control
>+ * module
>+ * @dev: the control module device
>+ * @on: 0 to off and 1 to on PHY wakeup feature
>+ * @id: phy id 0 or 1 for phy instance 0 and 1 repectively
>+ *
>+ * AMXXXX PHY driver should call this API to enable or disable PHY wakeup.
>+ */
>+void omap_control_am335x_phy_wkup(struct device *dev, bool on, u8 id)
>+{
>+ u32 val;
>+ u32 *phy_wkup_reg;
>+ struct omap_control_usb *control_usb = dev_get_drvdata(dev);
>+
>+ if (control_usb->type != OMAP_CTRL_DEV_TYPE3 || id < 0 || id > 1)
>+ return;
>+
>+ phy_wkup_reg = control_usb->dev_conf + AM335X_USB_WKUP_OFFSET;
>+ val = readl(phy_wkup_reg);
Where do you get the memory from? In the DT patches I've made I export
one memory space of 8 bytes for each phy. This memory space applies
directly to the on/off register. I didn't export the register for wakeup
so far since I had no idea how this will be used.
So how do you get your re-mapped memory here?
>+
>+ if (on)
>+ val |= id ? AM335X_USB1_WKUP_CTRL_ENABLE :
>+ AM335X_USB0_WKUP_CTRL_ENABLE;
>+ else
>+ val &= id ? ~AM335X_USB1_WKUP_CTRL_ENABLE :
>+ ~AM335X_USB0_WKUP_CTRL_ENABLE;
>+
>+
>+ writel(val, phy_wkup_reg);
>+}
>+EXPORT_SYMBOL_GPL(omap_control_am335x_phy_wkup);
Sebastian
next prev parent reply other threads:[~2013-07-29 14:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 12:34 [PATCH v2 0/4] Add phy support for AM335X platform using Generic PHy framework George Cherian
2013-07-19 12:34 ` [PATCH v2 1/4] usb: phy: phy-omap-control: Add API to power and wakeup George Cherian
2013-07-19 13:20 ` Kishon Vijay Abraham I
2013-07-29 14:25 ` Sebastian Andrzej Siewior [this message]
2013-07-30 4:53 ` George Cherian
2013-07-30 7:35 ` Sebastian Andrzej Siewior
2013-07-19 12:34 ` [PATCH v2 2/4] phy: phy-amxxxx-usb: Add PHY driver for amxxxx platform George Cherian
2013-07-19 13:32 ` Kishon Vijay Abraham I
2013-07-29 15:17 ` Sebastian Andrzej Siewior
2013-07-30 5:19 ` George Cherian
2013-07-30 8:53 ` Sebastian Andrzej Siewior
2013-07-30 14:24 ` George Cherian
2013-07-30 14:33 ` Felipe Balbi
2013-07-30 14:39 ` Sebastian Andrzej Siewior
2013-07-19 12:34 ` [PATCH v2 3/4] arm: dts: Add USB phy nodes for AM33XX George Cherian
2013-07-19 13:34 ` Kishon Vijay Abraham I
2013-07-19 13:56 ` Sergei Shtylyov
2013-07-19 14:20 ` Sebastian Andrzej Siewior
2013-07-19 18:33 ` Sergei Shtylyov
2013-07-19 18:42 ` Sebastian Andrzej Siewior
2013-07-20 3:41 ` George Cherian
2013-07-22 5:45 ` George Cherian
2013-07-20 3:36 ` George Cherian
2013-07-19 12:34 ` [PATCH v2 4/4] usb: musb: dsps: Remove the phy control from glue and add phy driver APIs George Cherian
2013-07-19 13:44 ` Kishon Vijay Abraham I
2013-07-19 13:17 ` [PATCH v2 0/4] Add phy support for AM335X platform using Generic PHy framework Kishon Vijay Abraham I
2013-08-10 11:59 ` Ezequiel Garcia
2013-08-14 10:36 ` Sebastian Andrzej Siewior
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=20130729142517.GA827@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=balbi@ti.com \
--cc=george.cherian@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@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).