From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] USB: gadget driver for LPC32xx
Date: Tue, 20 Mar 2012 19:20:12 +0100 [thread overview]
Message-ID: <4F68CA5C.2090406@antcom.de> (raw)
In-Reply-To: <201203201301.50159.arnd@arndb.de>
Hi Arnd,
On 03/20/2012 02:01 PM, Arnd Bergmann wrote:
>> Maybe the right thing is a common low-level isp1301 interface defining
>> all the registers and providing low-level (I2C) access functions,
>> leaving all the "higher level"/"board specific" functions up to the
>> existing drivers?
>>
>> (I guess you meant drivers/usb/otg/isp1301_omap.c ?)
>
> Yes, that sounds like a very good idea. Can you describe which part of
> the function isp1301 does? It's not clear how the layering between
> that and the platform driver should end up.
The ISP1301 is a relatively simple transceiver where the actual
differential USB signals end up being generated/decoded. It contains
some registers and is controlled via I2C to manipulate electrical
settings (pull up / power etc.).
At a first glance, I found the following drivers to be using it:
ohci-nxp (was: ohci-pnx4008 + ohci-lpc32xx)
isp1301_omap
lpc32xx_udc (WIP)
The common functions that all of them are using are some low-level
functions like read/write byte, read/write word. (For ohci-nxp, I used
smbus commands.) I propose exporting just the defines for all the
registers and their bits together with some accessor functions.
Would those be the correct places for header and driver:
drivers/usb/misc/isp1301.c
include/linux/usb/isp1301.h
?
As an example usage, I would let the next update of the lpc32xx_udc use
it and separately provide patches to make the other drivers above also
use it.
Thanks in advance,
Roland
WARNING: multiple messages have this Message-ID (diff)
From: Roland Stigge <stigge@antcom.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
w.sang@pengutronix.de, kevin.wells@nxp.com,
linux-arm-kernel@lists.infradead.org, arm@kernel.org,
srinivas.bakki@nxp.com
Subject: Re: [PATCH] USB: gadget driver for LPC32xx
Date: Tue, 20 Mar 2012 19:20:12 +0100 [thread overview]
Message-ID: <4F68CA5C.2090406@antcom.de> (raw)
In-Reply-To: <201203201301.50159.arnd@arndb.de>
Hi Arnd,
On 03/20/2012 02:01 PM, Arnd Bergmann wrote:
>> Maybe the right thing is a common low-level isp1301 interface defining
>> all the registers and providing low-level (I2C) access functions,
>> leaving all the "higher level"/"board specific" functions up to the
>> existing drivers?
>>
>> (I guess you meant drivers/usb/otg/isp1301_omap.c ?)
>
> Yes, that sounds like a very good idea. Can you describe which part of
> the function isp1301 does? It's not clear how the layering between
> that and the platform driver should end up.
The ISP1301 is a relatively simple transceiver where the actual
differential USB signals end up being generated/decoded. It contains
some registers and is controlled via I2C to manipulate electrical
settings (pull up / power etc.).
At a first glance, I found the following drivers to be using it:
ohci-nxp (was: ohci-pnx4008 + ohci-lpc32xx)
isp1301_omap
lpc32xx_udc (WIP)
The common functions that all of them are using are some low-level
functions like read/write byte, read/write word. (For ohci-nxp, I used
smbus commands.) I propose exporting just the defines for all the
registers and their bits together with some accessor functions.
Would those be the correct places for header and driver:
drivers/usb/misc/isp1301.c
include/linux/usb/isp1301.h
?
As an example usage, I would let the next update of the lpc32xx_udc use
it and separately provide patches to make the other drivers above also
use it.
Thanks in advance,
Roland
next prev parent reply other threads:[~2012-03-20 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 21:18 [PATCH] USB: gadget driver for LPC32xx Roland Stigge
2012-03-19 21:18 ` Roland Stigge
2012-03-19 21:30 ` Arnd Bergmann
2012-03-19 21:30 ` Arnd Bergmann
2012-03-19 22:26 ` Roland Stigge
2012-03-19 22:26 ` Roland Stigge
2012-03-20 13:01 ` Arnd Bergmann
2012-03-20 13:01 ` Arnd Bergmann
2012-03-20 18:20 ` Roland Stigge [this message]
2012-03-20 18:20 ` Roland Stigge
2012-03-20 19:21 ` Arnd Bergmann
2012-03-20 19:21 ` Arnd Bergmann
2012-03-20 1:56 ` Alan Stern
2012-03-20 1:56 ` Alan Stern
2012-03-23 8:38 ` Arnd Bergmann
2012-03-23 8:38 ` Arnd Bergmann
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=4F68CA5C.2090406@antcom.de \
--to=stigge@antcom.de \
--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 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.