On Thu, Nov 1, 2012 at 5:23 PM, Felipe Balbi wrote:
> Hi,
>
> On Thu, Nov 01, 2012 at 06:04:20AM -0700, Greg KH wrote:
>> On Thu, Nov 01, 2012 at 12:50:34PM +0200, Felipe Balbi wrote:
>> > On Thu, Nov 01, 2012 at 12:33:39PM +0200, Felipe Balbi wrote:
>> > > Hi,
>> > >
>> > > On Thu, Nov 01, 2012 a
Hello,
there are two fixes for the CY7C67x00 host controller:
one fixes memory allocation with non-atomic flags in the atomic context,
the other adds proper delays to the register access methods which makes
possible to use the chip with fast host CPU.
Max Filippov (2):
USB: c67x00: move URB
/0x170
c67x00_urb_enqueue+0x5c/0x254
usb_hcd_submit_urb+0x66e/0x724
usb_submit_urb+0x2ac/0x308
usb_start_wait_urb+0x2c/0xb8
usb_control_msg+0x8c/0xa8
hub_port_init+0x191/0x718
hub_thread+0x804/0xe14
kthread+0x72/0x78
ret_from_kernel_thread+0x8/0xc
Signed-off-by: Max Filippov
According to CY7C67300 specification HPI read and write cycle duration
Tcyc must be at least 6T long, where T is 1/48MHz, which is 125ns.
Without this delay fast host processor cannot write to chip registers.
Add proper ndelay to hpi_{read,write}_reg.
Signed-off-by: Max Filippov
---
drivers/usb
cro with a comment why it is needed;
- add Peter's Acked-bys. Thanks for the review, Peter.
Max Filippov (2):
USB: c67x00: move URB private data allocation from under spinlock
USB: c67x00: add proper delays to HPI read/write
drivers/usb/c67x00/c67x00-ll-hpi.c | 10 ++
drivers/us
/0x170
c67x00_urb_enqueue+0x5c/0x254
usb_hcd_submit_urb+0x66e/0x724
usb_submit_urb+0x2ac/0x308
usb_start_wait_urb+0x2c/0xb8
usb_control_msg+0x8c/0xa8
hub_port_init+0x191/0x718
hub_thread+0x804/0xe14
kthread+0x72/0x78
ret_from_kernel_thread+0x8/0xc
Signed-off-by: Max Filippov
According to CY7C67300 specification HPI read and write cycle duration
Tcyc must be at least 6T long, where T is 1/48MHz, which is 125ns.
Without this delay fast host processor cannot write to chip registers.
Add proper ndelay to hpi_{read,write}_reg.
Signed-off-by: Max Filippov
Acked-by: Peter
Hi Babu,
On Tue, Jul 4, 2017 at 10:19 AM, Babu Moger wrote:
> Max, Do you have any concerns about xtensa?
no, not ATM. I still haven't got a chance to look closer at moving endianness
macros back to Kconfig for xtensa.
--
Thanks.
-- Max
--
To unsubscribe from this list: send the line "unsubscr
