From: Dan Carpenter <error27@gmail.com>
To: "Anoop P.A" <anoop.pa@gmail.com>
Cc: "gregkh @ suse . de" <gregkh@suse.de>,
"dbrownell @ users . sourceforge . net"
<dbrownell@users.sourceforge.net>,
"stern @ rowland . harvard . edu" <stern@rowland.harvard.edu>,
"pkondeti @ codeaurora . org" <pkondeti@codeaurora.org>,
"jacob . jun . pan @ intel . com" <jacob.jun.pan@intel.com>,
"linux-usb @ vger . kernel . org" <linux-usb@vger.kernel.org>,
"alek . du @ intel . com" <alek.du@intel.com>,
"linux-kernel @ vger . kernel . org"
<linux-kernel@vger.kernel.org>,
"gadiyar @ ti . com" <gadiyar@ti.com>,
"ralf @ linux-mips . org" <ralf@linux-mips.org>,
"linux-mips @ linux-mips . org" <linux-mips@linux-mips.org>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH v5] EHCI bus glue for on-chip PMC MSP USB controller
Date: Tue, 22 Feb 2011 23:04:27 +0300 [thread overview]
Message-ID: <20110222200427.GB1966@bicker> (raw)
In-Reply-To: <1298388933-13707-1-git-send-email-anoop.pa@gmail.com>
On Tue, Feb 22, 2011 at 09:05:33PM +0530, Anoop P.A wrote:
> From: Anoop <paanoop1@paanoop1-desktop.(none)>
>
> This patch add bus glue for USB controller commonly found in PMC-Sierra MSP71xx family of SoC's.
>
>
> Signed-off-by: Anoop P A <anoop.pa@gmail.com>
> ---
> Changes.
> ehci-pmcmsp.c is based on latest ehci-pci.c.Addressed some stylistic issue pointed by Greg.
> Addressed comments from Matthieu CASTET.
Could you spell that out more completely next time?
> +config USB_EHCI_HCD_PMC_MSP
> + tristate "EHCI support for on-chip PMC MSP USB controller"
Better to say "EHCI support for on-chip PMC-Sierra MSP71xx USB controllers"
> + depends on USB_EHCI_HCD && MSP_HAS_USB
> + default y
New features always default to No.
> +#include <msp_usb.h>
Cannot find the msp_usb.h in linux-next. Doesn't compile.
> +static void usb_hcd_tdi_set_mode(struct ehci_hcd *ehci)
> +{
> + u8 *base;
> + u8 *statreg;
> + u8 *fiforeg;
> + u32 val;
> + struct ehci_regs *reg_base = ehci->regs;
> +
> + /* get register base */
> + base = (u8 *)reg_base + USB_EHCI_REG_USB_MODE;
> + statreg = (u8 *)reg_base + USB_EHCI_REG_USB_STATUS;
> + fiforeg = (u8 *)reg_base + USB_EHCI_REG_USB_FIFO;
> +
> + /* Disable controller mode stream */
> + val = ehci_readl(ehci, (u32 *)base);
It doesn't compile so I can't test this, but I think that this will
cause a sparse warning. "base" should have an __iomem tag. Please
run sparse on this driver.
> +/* called after powerup, by probe or system-pm "wakeup" */
> +static int ehci_msp_reinit(struct ehci_hcd *ehci)
> +{
> + ehci_port_power(ehci, 0);
> +
> + return 0;
Better to make this function void.
> +}
> +
> +/* called during probe() after chip reset completes */
> +static int ehci_msp_setup(struct usb_hcd *hcd)
> +{
> + struct ehci_hcd *ehci = hcd_to_ehci(hcd);
> + u32 temp;
> + int retval;
Needs a blank line here to separate declarations from code.
> + ehci->big_endian_mmio = 1;
> + ehci->big_endian_desc = 1;
> +
> + ehci->caps = hcd->regs;
> + ehci->regs = hcd->regs +
> + HC_LENGTH(ehci_readl(ehci, &ehci->caps->hc_capbase));
[snip]
> + /* data structure init */
> + retval = ehci_init(hcd);
> + if (retval)
> + return retval;
> +
> + temp = HCS_N_CC(ehci->hcs_params) * HCS_N_PCC(ehci->hcs_params);
> + temp &= 0x0f;
companion HCs * ports per CC & 0xf?
What's the &= 0x0f for? It's left out of the printk.
> + if (temp && HCS_N_PORTS(ehci->hcs_params) > temp) {
> + ehci_dbg(ehci, "bogus port configuration: "
> + "cc=%d x pcc=%d < ports=%d\n",
> + HCS_N_CC(ehci->hcs_params),
> + HCS_N_PCC(ehci->hcs_params),
> + HCS_N_PORTS(ehci->hcs_params));
> + }
[snip]
> +/*-------------------------------------------------------------------------*/
No need for these blank comments.
> +
> +static void msp_start_hc(struct platform_device *dev)
> +{
> +}
> +
> +static void msp_stop_hc(struct platform_device *dev)
> +{
> +}
> +
I don't understand the point of these empty functions.
> +static int ehci_msp_suspend(struct device *dev)
> +{
> + struct usb_hcd *hcd = dev_get_drvdata(dev);
> + struct ehci_hcd *ehci = hcd_to_ehci(hcd);
> + unsigned long flags;
> + int rc;
> +
> + return 0;
> + rc = 0;
> +
> + if (time_before(jiffies, ehci->next_statechange))
> + usleep(10000);
Is there still a usleep() function? Either way, can you send us
something that compiles on linux-next?
regards,
dan carpenter
next prev parent reply other threads:[~2011-02-22 20:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 11:06 [PATCH] EHCI support for on-chip PMC MSP USB controller Anoop P
2010-12-21 16:00 ` Alan Stern
2010-12-21 16:00 ` Alan Stern
2010-12-21 17:59 ` Greg KH
2010-12-22 14:34 ` [PATCH V2 0/2] " Anoop P.A
2010-12-22 14:36 ` [PATCH V2 1/2] " Anoop P.A
2010-12-22 14:58 ` Anoop P A
2010-12-24 9:44 ` Shane McDonald
2011-01-27 11:28 ` [PATCH v3] EHCI bus glue " Anoop P.A
2011-02-04 19:56 ` Greg KH
2011-02-09 14:12 ` Anoop P A
2011-02-09 17:20 ` Greg KH
2011-02-09 15:10 ` Matthieu CASTET
2011-02-09 15:44 ` Anoop P A
2011-02-15 10:43 ` [PATCH v4] " Anoop P.A
2011-02-15 17:44 ` Matthieu CASTET
2011-02-22 15:35 ` [PATCH v5] " Anoop P.A
2011-02-22 20:04 ` Dan Carpenter [this message]
2011-02-23 13:22 ` Anoop P A
2011-02-23 17:02 ` Dan Carpenter
2011-02-24 10:19 ` Anoop P A
2011-02-24 11:28 ` Dan Carpenter
2011-02-24 13:56 ` [PATCH] " Anoop P.A
2010-12-22 14:36 ` [PATCH V2 2/2] MSP onchip root hub over current quirk Anoop P.A
2010-12-23 2:18 ` Alan Stern
2010-12-23 2:18 ` Alan Stern
2010-12-23 9:29 ` Anoop P A
2010-12-23 16:08 ` Alan Stern
2010-12-23 16:08 ` Alan Stern
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=20110222200427.GB1966@bicker \
--to=error27@gmail.com \
--cc=alek.du@intel.com \
--cc=anoop.pa@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=gadiyar@ti.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jacob.jun.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb@vger.kernel.org \
--cc=pkondeti@codeaurora.org \
--cc=ralf@linux-mips.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.