From: Greg KH <gregkh@linuxfoundation.org>
To: Roland Stigge <stigge@antcom.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kevin.wells@nxp.com, srinivas.bakki@nxp.com,
stern@rowland.harvard.edu, linux-arm-kernel@lists.infradead.org,
arnd@arndb.de
Subject: Re: [PATCH v5 1/3] USB: Add driver for NXP ISP1301 USB transceiver
Date: Tue, 24 Apr 2012 16:20:44 -0700 [thread overview]
Message-ID: <20120424232044.GA2657@kroah.com> (raw)
In-Reply-To: <1335002264-22225-1-git-send-email-stigge@antcom.de>
On Sat, Apr 21, 2012 at 11:57:42AM +0200, Roland Stigge wrote:
> This very-lowlevel driver registers the NXP ISP1301 chip via the I2C subsystem.
> The chip is the USB transceiver shared by ohci-nxp, lpc32xx_udc (gadget) and
> isp1301_omap.
>
> Following patches let the respective USB host and gadget drivers use this
> driver, instead of duplicating ISP1301 handling.
>
> Signed-off-by: Roland Stigge <stigge@antcom.de>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> ---
>
> Applies to v3.4-rc3
>
> Changes since v4:
> * Documentation adjustment of device tree "compatible" string:
> "nxp,lpc32xx-udc" -> "nxp,lpc3220-udc"
>
> Documentation/devicetree/bindings/usb/isp1301.txt | 25 ++++++
> drivers/usb/Kconfig | 2
> drivers/usb/Makefile | 1
> drivers/usb/phy/Kconfig | 17 ++++
> drivers/usb/phy/Makefile | 7 +
> drivers/usb/phy/isp1301.c | 79 ++++++++++++++++++++
Nice, but:
> include/linux/usb/isp1301.h | 84 ++++++++++++++++++++++
Why this file? You have a lot of register stuff in here that should be
in the .c file, right? Only put what other files need in this .h file,
which shouldn't be much at all from what I can tell.
> +#define DRV_VERSION "0.1.0"
Is that really needed?
> +struct i2c_client *isp1301_get_client(struct device_node *node)
> +{
> + if (node) { /* reference of ISP1301 I2C node via DT */
> + struct device *dev = bus_find_device(&i2c_bus_type, NULL,
> + node, match);
> + if (!dev)
> + return NULL;
> + return to_i2c_client(dev);
> + } else { /* non-DT: only one ISP1301 chip supported */
> + return isp1301_i2c_client;
> + }
> +}
> +EXPORT_SYMBOL(isp1301_get_client);
EXPORT_SYMBOL_GPL()?
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Are you really willing to keep track of where the FSF keeps it's office
for the next 40 years? Just delete this paragraph please, it's not
needed at all.
thanks,
greg k-h
next prev parent reply other threads:[~2012-04-24 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 9:57 [PATCH v5 1/3] USB: Add driver for NXP ISP1301 USB transceiver Roland Stigge
2012-04-21 9:57 ` [PATCH v5 2/3] USB: gadget driver for LPC32xx Roland Stigge
2012-04-21 9:57 ` [PATCH v5 3/3] USB: ohci-nxp: Use isp1301 driver Roland Stigge
2012-04-24 23:20 ` Greg KH [this message]
2012-04-25 8:19 ` [PATCH v5 1/3] USB: Add driver for NXP ISP1301 USB transceiver Roland Stigge
2012-04-25 18:35 ` Greg KH
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=20120424232044.GA2657@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=kevin.wells@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=srinivas.bakki@nxp.com \
--cc=stern@rowland.harvard.edu \
--cc=stigge@antcom.de \
/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