From: Sergei Shtylyov <sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
To: George Cherian <george.cherian-l0cyMroinI0@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org,
balbi-l0cyMroinI0@public.gmane.org,
zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
b-liu-l0cyMroinI0@public.gmane.org
Subject: Re: [PATCH v5 6/6] usb: musb: dsps: Enable sw babble control for newer silicon
Date: Thu, 22 May 2014 15:58:50 +0400 [thread overview]
Message-ID: <537DE67A.10203@cogentembedded.com> (raw)
In-Reply-To: <1400740181-31213-7-git-send-email-george.cherian-l0cyMroinI0@public.gmane.org>
Hello.
On 22-05-2014 10:29, George Cherian wrote:
> Find whether we are running on newer silicon. The babble control
> register reads 0x4 by default in newer silicon as opposed to 0
> in old versions of AM335x. Based on this enable the sw babble
> control logic.
> Signed-off-by: George Cherian <george.cherian-l0cyMroinI0@public.gmane.org>
> ---
> drivers/usb/musb/musb_dsps.c | 38 ++++++++++++++++++++++++++++++++------
> 1 file changed, 32 insertions(+), 6 deletions(-)
> diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/musb_dsps.c
> index 868caf8..2ced061 100644
> --- a/drivers/usb/musb/musb_dsps.c
> +++ b/drivers/usb/musb/musb_dsps.c
[...]
> @@ -469,6 +470,19 @@ static int dsps_musb_init(struct musb *musb)
> val &= ~(1 << wrp->otg_disable);
> dsps_writel(musb->ctrl_base, wrp->phy_utmi, val);
>
> + /*
> + * Check whether the dsps version has babble control enabled.
One space too many before this sentence.
> + * In latest silicon revision the babble control logic is enabled.
> + * If MUSB_BABBLE_CTL returns 0x4 then we have the babble control
> + * logic enabled.
> + */
> + val = dsps_readb(musb->mregs, MUSB_BABBLE_CTL);
> + if (val == MUSB_BABBLE_RCV_DISABLE) {
> + glue->sw_babble_enabled = true;
> + val |= MUSB_BABBLE_SW_SESSION_CTRL;
> + dsps_writeb(musb->mregs, MUSB_BABBLE_CTL, val);
> + }
> +
Hm, from the register offset that you declared in the previous patch, I
got an impression that this is a new standard MUSB register? Shouldn't this
check be done in the generic MUSB code then?
WBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-22 11:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 6:29 [PATCH v5 0/6] Add support for SW babble Control George Cherian
2014-05-22 6:29 ` [PATCH v5 1/6] usb: musb: core: Handle Babble condition only in HOST mode George Cherian
2014-05-22 6:29 ` [PATCH v5 2/6] usb: musb: core: Convert babble recover work to delayed work George Cherian
[not found] ` <1400740181-31213-1-git-send-email-george.cherian-l0cyMroinI0@public.gmane.org>
2014-05-22 6:29 ` [PATCH v5 3/6] usb: musb: dsps: Call usb_phy(_shutdown/_init) during musb_platform_reset() George Cherian
2014-05-22 6:29 ` [PATCH v5 4/6] usb: musb: core: Convert the musb_platform_reset to have a return value George Cherian
2014-05-22 6:29 ` [PATCH v5 5/6] usb: musb: dsps: Add the sw_babble_control() George Cherian
2014-05-22 11:23 ` Sergei Shtylyov
2014-05-22 11:39 ` Sergei Shtylyov
2014-05-22 6:29 ` [PATCH v5 6/6] usb: musb: dsps: Enable sw babble control for newer silicon George Cherian
[not found] ` <1400740181-31213-7-git-send-email-george.cherian-l0cyMroinI0@public.gmane.org>
2014-05-22 11:58 ` Sergei Shtylyov [this message]
2014-05-22 12:52 ` George Cherian
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=537DE67A.10203@cogentembedded.com \
--to=sergei.shtylyov-m4dtvfq/zs1mrggop+s0pdbpr1lh4cv8@public.gmane.org \
--cc=b-liu-l0cyMroinI0@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=george.cherian-l0cyMroinI0@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).