Hi,
the parameter is file=/dev/mmcblk0p1
Perhaps you have already realized this... mmcblk0p1 is the first
partition of the mmcblk0 device. Block 0 of the partition is the boot
sector, not the MBR. The MBR is block 0 of the mmcblk0 device. So
perhaps you really meant to use:
Hi Roger,
On 03/20/2013 04:44 PM, Roger Quadros wrote:
Hi Tony,
These patches provide the SoC side code required to support
the changes in the OMAP USB Host drivers done in [1], [2] [3].
Device tree support is added for Beagleboard only. I've removed
Panda device tree support till we
Hi Roger,
On 04/05/2013 10:30 AM, Benoit Cousson wrote:
...
ARM: dts: OMAP4: Add HS USB Host IP nodes
ARM: dts: OMAP3: Add HS USB Host IP nodes
ARM: dts: omap3-beagle: Add USB Host support
These 3 DTS patches are good to me, but I cannot applied them on top of
the already existing
Hi,
On Thu, Apr 04, 2013 at 09:50:06PM +0200, Daniel Mack wrote:
Hi all,
here are some patches to separate the HCD and gadget part of the musb
driver so they can be deselected in Kconfig. They also make the driver
keep track of the configured port mode that is set from DT, so the
actual
Hi,
On 05.04.2013 11:58, Felipe Balbi wrote:
On Thu, Apr 04, 2013 at 09:50:06PM +0200, Daniel Mack wrote:
Hi all,
here are some patches to separate the HCD and gadget part of the musb
driver so they can be deselected in Kconfig. They also make the driver
keep track of the configured port
On 04/04/2013 07:41 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130404 00:39]:
On 04/04/2013 02:42 AM, Tony Lindgren wrote:
--- a/arch/arm/mach-omap2/cclock44xx_data.c
+++ b/arch/arm/mach-omap2/cclock44xx_data.c
@@ -27,6 +27,7 @@
#include linux/clk-private.h
#include
On Thu, Apr 4, 2013 at 2:50 PM, Roger Quadros rog...@ti.com wrote:
correcting misleading subject line.
was (Re: MUSB regression in linux next at least for pandboard)
On 04/04/2013 02:36 PM, Roger Quadros wrote:
Hi,
On 02/07/2013 04:10 PM, Grazvydas Ignotas wrote:
On Thu, Feb 7, 2013 at
On 04/05/2013 02:11 PM, Grazvydas Ignotas wrote:
On Thu, Apr 4, 2013 at 2:50 PM, Roger Quadros rog...@ti.com wrote:
correcting misleading subject line.
was (Re: MUSB regression in linux next at least for pandboard)
On 04/04/2013 02:36 PM, Roger Quadros wrote:
Hi,
On 02/07/2013 04:10 PM,
Hi,
On 05.04.2013 11:58, Felipe Balbi wrote:
On Thu, Apr 04, 2013 at 09:50:06PM +0200, Daniel Mack wrote:
Hi all,
here are some patches to separate the HCD and gadget part of the musb
driver so they can be deselected in Kconfig. They also make the driver
keep track of the configured port
On Thu, Apr 04, 2013 at 09:50:07PM +0200, Daniel Mack wrote:
The functionality meant to be represented by this symbol will be
re-added later, but for now, USB_GADGET_MUSB_HDRC is in fact unused and
can be dropped.
Signed-off-by: Daniel Mack zon...@gmail.com
this one is good to go for v3.11
On Thu, Apr 04, 2013 at 09:50:08PM +0200, Daniel Mack wrote:
Let the function declarations live in the header file the belong to,
header file *they* belong to. Typo there.
other than that, patch looks alright.
--
balbi
signature.asc
Description: Digital signature
On Thu, Apr 04, 2013 at 09:50:09PM +0200, Daniel Mack wrote:
The musb struct is currently allocated along with the hcd, which makes
it difficult to build a driver that only acts as gadget device.
Fix this by allocation musb directly, and keep the hcd around as pointer.
Fix this by
Hi
On Thu, Apr 04, 2013 at 09:50:10PM +0200, Daniel Mack wrote:
This makes building the actual object files optional to the selected
mode, which saves users who know which kind of USB mode support they
need some binary size.
Unimplemented functions are stubbed out with static inline
Hi,
On Thu, Apr 04, 2013 at 09:50:11PM +0200, Daniel Mack wrote:
diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
index d564580..d298be7 100644
--- a/drivers/usb/musb/musb_host.c
+++ b/drivers/usb/musb/musb_host.c
@@ -2649,6 +2649,27 @@ void musb_host_free(struct musb
On 05.04.2013 15:07, Felipe Balbi wrote:
Hi,
On Thu, Apr 04, 2013 at 09:50:11PM +0200, Daniel Mack wrote:
diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
index d564580..d298be7 100644
--- a/drivers/usb/musb/musb_host.c
+++ b/drivers/usb/musb/musb_host.c
@@ -2649,6
Hi,
On Thu, Apr 04, 2013 at 09:50:12PM +0200, Daniel Mack wrote:
Initialize the host and gagdet subsystems of the musb driver only when
the appropriate mode is selected from platform data, or device-tree
information, respectively.
Refuse to start the gadget part if the port is in host-only
On Fri, 5 Apr 2013, victor yeo wrote:
Now i insmod g_file_storage gadget with file=/mnt/sd/backing_file, the
SCSI_READ_10 command is still not working properly.
What makes you think that?
See the gadget log below. The g_file_storage gadget receives SCSI
command: Unknown xa1 from the Linux
On Fri, 5 Apr 2013, Sergei Shtylyov wrote:
Sometimes there is a need to initialize some non-standard registers mapped to
the EHCI region before accessing the standard EHCI registers. Add the init()
method to the 'ehci-platform' platform data for this purpose.
init isn't such a good name for
On Fri, 5 Apr 2013, Paul Menzel wrote:
Dear Linux USB folks,
using Debian Wheezy/testing with Linux 3.2.39-2 and
uswsusp 1.0+20110509-3, I see the following problem similar to the one
described in some Ubuntu forum from 2009 [1] or a question from 2012 to
Ask Ubuntu [2].
Running
Hi all,
here are some patches to separate the HCD and gadget part of the musb
driver so they can be deselected in Kconfig. They also make the driver
keep track of the configured port mode that is set from DT, so the
actual runtime configuration can be selected dynamically.
One thing that is
The functionality meant to be represented by this symbol will be
re-added later, but for now, USB_GADGET_MUSB_HDRC is in fact unused and
can be dropped.
Signed-off-by: Daniel Mack zon...@gmail.com
---
drivers/usb/gadget/Kconfig | 8
1 file changed, 8 deletions(-)
diff --git
Let the function declarations live in the header files they belong to,
which makes it easier to stub them out later.
Signed-off-by: Daniel Mack zon...@gmail.com
---
drivers/usb/musb/musb_core.h | 17 -
drivers/usb/musb/musb_gadget.h | 17 +++--
In particular, this introduces musb_host_resume_root_hub()and
musb_host_poke_root_hub() which will be stubbed out later.
Signed-off-by: Daniel Mack zon...@gmail.com
---
drivers/usb/musb/musb_core.c | 18 +++---
drivers/usb/musb/musb_host.c | 15 ++-
This function has its only user in musb_virthub.c, so let's move it
there and make it static.
Signed-off-by: Daniel Mack zon...@gmail.com
---
drivers/usb/musb/musb_core.c| 45 -
drivers/usb/musb/musb_core.h| 1 -
drivers/usb/musb/musb_virthub.c |
This makes building the actual object files optional to the selected
mode, which saves users who know which kind of USB mode support they
need some binary size.
Unimplemented functions are stubbed out with static inline functions.
Signed-off-by: Daniel Mack zon...@gmail.com
---
This patch re-introduces the bits that are necessary to use the musb
controller in host mode.
Signed-off-by: Daniel Mack zon...@gmail.com
---
drivers/usb/musb/musb_core.c | 5 +
drivers/usb/musb/musb_host.c | 21 +
drivers/usb/musb/musb_host.h | 8
3 files
The musb struct is currently allocated along with the hcd, which makes
it difficult to build a driver that only acts as gadget device.
Fix this by allocating musb directly, and keep the hcd around as
a pointer in the musb struct.
struct hc_driver musb_hc_driver can now also be static to
Define MUSB_PORT_MODE_{HOST,GADGET,DUAL_ROLE} and store the
platform-specified value in struct musb.
Note that MUSB_PORT_MODE_HOST has to be set to 1 in order to match
existing device tree bindings which are already documented but in fact
unusued.
Signed-off-by: Daniel Mack zon...@gmail.com
---
With the hcd is now a direct member of struct musb, we can now simply
eliminate the musb_to_hcd() macro. There aren't that many users left
anyway, as some where already fixed up when parts were factored out to
musb_host.c
Signed-off-by: Daniel Mack zon...@gmail.com
---
Initialize the host and gagdet subsystems of the musb driver only when
the appropriate mode is selected from platform data, or device-tree
information, respectively.
Signed-off-by: Daniel Mack zon...@gmail.com
---
drivers/usb/musb/musb_core.c| 22 +-
* Benoit Cousson b-cous...@ti.com [130405 03:00]:
On 04/05/2013 10:30 AM, Benoit Cousson wrote:
...
ARM: dts: OMAP4: Add HS USB Host IP nodes
ARM: dts: OMAP3: Add HS USB Host IP nodes
ARM: dts: omap3-beagle: Add USB Host support
These 3 DTS patches are good to me, but I
On Fri, Apr 05, 2013 at 06:51:21AM +0400, Vladimir Murzin wrote:
On Thu, Apr 04, 2013 at 12:29:25PM -0700, Sarah Sharp wrote:
Someone else is already working on a patch to fix part of this:
http://marc.info/?l=linux-usbm=136509667003716w=2
Please coordinate with them.
Also, two
* Roger Quadros rog...@ti.com [130405 03:44]:
On 04/04/2013 07:41 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130404 00:39]:
On 04/04/2013 02:42 AM, Tony Lindgren wrote:
For v3.10, let's just make sure that USB works with DT as then
after v3.10 we can make omap4 DT only and
Hello.
On 05-04-2013 4:43, Simon Horman wrote:
Now that the EHCI internal buffer setup is done by the platform code, we can
remove such code from this driver as it never really belonged here. We also
no longer need the 2nd memory region now (2nd EHCI controller is simply missing
in e.g.
Hello.
On 05-04-2013 4:43, Simon Horman wrote:
The memory region that is used by the driver overlaps EHCI and OHCI register
regions for absolutely no reason now -- fix it by adding offset of 0x800 to
the base address, changing the register #define's accordingly. This has extra
positive effect
Hello.
On 05-04-2013 4:44, Simon Horman wrote:
Since we're now going to setup the USBPCTRL0 register using the USB PHY device's
platform data, we now need a way to pass those platform data from the board file
to the device which is situated in setup-r8a7779.c -- and what I'm suggesting is
On Wed, 27 Mar 2013, Petko Manolov wrote:
On Tue, 26 Mar 2013, Sarah Sharp wrote:
ctrl_callback is still reading the URB status, and using it in the
switch statement. It's also using the urb-context as well, to dig out
a pointer (pegasus_t) that the pegasus_set_multicast already has access
On 04/04/2013 07:41 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130404 00:39]:
On 04/04/2013 02:42 AM, Tony Lindgren wrote:
--- a/arch/arm/mach-omap2/cclock44xx_data.c
+++ b/arch/arm/mach-omap2/cclock44xx_data.c
@@ -27,6 +27,7 @@
#include linux/clk-private.h
#include
There are no functional changes in this patch. However, because the
compliance mode timer can be deleted in more than one function, it
seemed expedient to include the function name in the debug strings.
Also limited the use of capitals to the first word in the compliance
mode debug messages,
On Thu, Apr 04, 2013 at 01:13:45PM +0300, Alexander Shishkin wrote:
Hi,
This series contains two fixes, both of which are also applicable to
-stable.
Michael Grzeschik (2):
usb: chipidea: udc: fix memory access of shared memory on armv5
machines
usb: chipidea: udc: fix memory
Hello.
On 04/05/2013 06:43 PM, Alan Stern wrote:
Sometimes there is a need to initialize some non-standard registers mapped to
the EHCI region before accessing the standard EHCI registers. Add the init()
method to the 'ehci-platform' platform data for this purpose.
init isn't such a good
On 04/06/2013 12:40 AM, Sergei Shtylyov wrote:
And instead of passing hcd-regs, wouldn't it be better to pass hcd?
I really don't know.
Other users of this interface might need to initialize something other
than a non-standard register.
Hm, maybe... if passing 'struct usb_hcd *'
On Sat, 6 Apr 2013, Sergei Shtylyov wrote:
On 04/06/2013 12:40 AM, Sergei Shtylyov wrote:
And instead of passing hcd-regs, wouldn't it be better to pass hcd?
I really don't know.
Other users of this interface might need to initialize something other
than a non-standard
On 04/06/2013 12:56 AM, Alan Stern wrote:
And instead of passing hcd-regs, wouldn't it be better to pass hcd?
I really don't know.
Other users of this interface might need to initialize something other
than a non-standard register.
Hm, maybe... if passing 'struct usb_hcd *' would
On Sat, 6 Apr 2013, Sergei Shtylyov wrote:
On 04/06/2013 12:56 AM, Alan Stern wrote:
And instead of passing hcd-regs, wouldn't it be better to pass hcd?
I really don't know.
Other users of this interface might need to initialize something other
than a non-standard register.
On Thu, Apr 04, 2013 at 04:03:14PM +0200, Stefan Reif wrote:
From: Kurt Kanzenbach ly80t...@cip.cs.fau.de
Since the names.c/names.h are taken from another project, some
functions which names.c provides aren't used by usbipd.
This patch fixes:
- removed useless comments
- unified
Each of the parameters in the dwc2_core_params struct can now be changed
using devicetree parameters.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
Documentation/devicetree/bindings/staging/dwc2.txt | 36
drivers/staging/dwc2/platform.c| 68
Bits 16-31 are reserved, so the old code just reads the whole register to
get bits 0-15, assuming the reserved bits would be 0 (which seems true
on current hardware, but who knows...).
This commit properly masks out the reserved bits when reading and
doesn't touch the reserved bits while writing.
Some of the defaults were missing or unclear. In particular, I suspect
the defaults were documented assuming there were still module parameters
and taking the default module parameters into account. Now, the defaults
are the values that will get chosen when the params passed to
dwc2_hcd_init are
A generic set of FIFOSIZE_* constants was used for both the GNPTXFSIZ
and HPTXFSIZ registers, even where a specific set of constants was a
available for the GNPTXFSIZ register. This change adds specific
constants for the HPTXFSIZ register as well, changes the code to use
those specific constants
Previously, the max_packet_count could be set to 1 x, where x is the
number of bits available (width + 4 in the code). Since 1 x requires
x + 1 bits to represent, this will not work. The real maximum value is
(1 x) - 1. This value is already used the default when the set value
is invalid, but
Instead of just setting the dma_mask to the empty mask, the pointer to
the mask is cleared altogether. This is needed because
usb_create_shared_hcd sets hcd-self.uses_dma based on
dev-dma_mask != NULL, not by looking at the actual mask itself.
This change thus makes hcd-self.uses_dma have the
From: Stephen Warren swar...@wwwdotorg.org
Signed-off-by: Stephen Warren swar...@wwwdotorg.org
[matth...@stdin.nl: Split patch from bigger patch and added commit message]
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/core.c | 2 +-
drivers/staging/dwc2/hcd.c | 2 +-
This (read-only) register was read twice, storing it for later use the
second time. Now it is only read once, storing it right away.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/hcd.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git
Before, it was a function that would set all members of a given struct
containing only int members to -1. Now, it is renamed to
dwc_set_all_params and it works only on the dwc2_core_params struct.
This makes sure that all of the slightly dubious casting and assumptions
happen inside the function
Various register fields wider than one bit have constants defined for
their value. Previously, these registers would define the values as they
appear in the register, so shifted to the right to the position the
value appears in the register.
This commit changes those constants to their natural
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/pci.c | 7 ---
1 file changed, 7 deletions(-)
This is just the minimal list of includes that made the compile work.
diff --git a/drivers/staging/dwc2/pci.c b/drivers/staging/dwc2/pci.c
index acf2008..a1d2ede 100644
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/core.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/dwc2/core.c b/drivers/staging/dwc2/core.c
index 9162bed..9a34ac7 100644
--- a/drivers/staging/dwc2/core.c
+++
Before, the value of the hcchar register was shifted and masked and then
the debug output extracted the individual values out of the complete
hcchar register again. This commit makes the debug prints directly use
the original values instead.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
Previously, it was dwc_otg, but this does not correspond to the
directory name and might cause confusion with the old out-of-tree
dwc_otg driver of which many versions circulate.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/hcd.c | 2 +-
drivers/staging/dwc2/pci.c
This function disables all common interrupts, i.e., those that are
handled by the common interrupt handler.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/core.c | 14 ++
drivers/staging/dwc2/core.h | 6 ++
drivers/staging/dwc2/core_intr.c
This flag is a deprecated NOOP, interrupt handlers are always run
with interupts disabled.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
See include/linux/interrupt.h and 6932bf37 (genirq: Remove
If the platform driver failed to setup a dma_mask, but the hardware
advertises support for DMA, before DMA would be enabled in dwc2, but
disabled in the usb core, making all connectivity break.
With this commit, the dwc2 driver will emit a warning and fall back to
slave mode in this case.
The value in params-enable_dynamic_fifo can only be true if the
corresponding bit in hwcfg2 is set, this is already checked by
dwc2_set_param_enable_dynamic_fifo.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/core.c | 3 +--
1 file changed, 1 insertion(+), 2
---
arch/arm/Kconfig | 1 +
arch/arm/boot/dts/bcm2835.dtsi | 6 ++
arch/arm/configs/bcm2835_defconfig | 20 ++--
3 files changed, 21 insertions(+), 6 deletions(-)
This patch is just FYI.
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index
This line extracted the available queue space without properly shifting
it. Since the code only cared wether it was zero or not, it worked as
expected without the shift, but adding shift makes the code cleaner.
While we're here, store the result in a helper variable that was already
declared to
This commit changes expressions from (val shift) (mask shift) to
(val mask) shift.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/core.c | 20 ++---
drivers/staging/dwc2/hcd.c | 62 +++--
Before, this was initialized in pci.c, after the dwc2_hcd_init was
called and the interrupts were enabled. This opened up a small time
window where common interrupts could be triggered, but there was no
handler for them, causing them to keep triggering infinitely and locking
up the machine.
On my
---
arch/mips/ralink/rt305x-usb.c | 5 +
1 file changed, 5 insertions(+)
This patch is just FYI.
diff --git a/arch/mips/ralink/rt305x-usb.c b/arch/mips/ralink/rt305x-usb.c
index 793fc82..7d87740 100644
--- a/arch/mips/ralink/rt305x-usb.c
+++ b/arch/mips/ralink/rt305x-usb.c
@@ -108,6 +108,7
This adds a dwc_platform.ko module that can be loaded by using
compatible = snps,dwc2 in a device tree.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
Documentation/devicetree/bindings/staging/dwc2.txt | 15 +++
drivers/staging/dwc2/Kconfig | 6 +-
For some reason, the value of the HPTXFSIZ register was built in the
ptxfsiz variable, while there was also a hptxfsiz variable availble.
Better just use that.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/core.c | 12 ++--
1 file changed, 6 insertions(+), 6
This code appears to be partially incorrect. Since this is only debug
code and only applies to device mode, it seems better to remove this
code for now than to invest time fixing it.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/core.c | 19 ---
1
This interrupt is currently not enabled anywhere, but there is some
(dummy) handling for it in the host interrupt handler. This marks it as
a host mode interrupt, so it makes sense to disable it when disabling
the other host mode interrupts.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
The HWCFG4 register stores the supported utmi width values (8, 16 or
both). This commit reads that value and validates the configured value
against that.
If no (valid) value is given, the parameter defaulted to 8 bits
previously. However, the documentation for dwc2_core_params_struct
suggests
---
arch/mips/ralink/dts/rt3050.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
This patch is just FYI.
diff --git a/arch/mips/ralink/dts/rt3050.dtsi b/arch/mips/ralink/dts/rt3050.dtsi
index 5aede8d..2b7ab42 100644
--- a/arch/mips/ralink/dts/rt3050.dtsi
+++
For host mode, this interrupt is already handled by the hcd interrupt
handler. The common interrupt handler additionally did a noop handling
(it only cleared the flag and nothing else) when in device mode.
Since the driver currently supports only host mode, this shouldn't
result in any behaviour
Convert use of devm_request_and_ioremap() to the newly introduced
devm_ioremap_resource() which provides more consistent error handling.
devm_ioremap_resource() provides its own error messages so the explicit
error code can be removed from the failure code path.
Signed-off-by: Matthijs Kooijman
For calculating FIFO offsets, the sizes of preceding fifos need to be
known. For filling the GDFIFOCFG register, these fifo sizes were read
from hardware registers. However, these values were written to these
registers just a few lines before, so we can just use the values written
instead.
It seems this flag is intended to pass to irq_set_status_flags, not
request_irq, and is not available on all architectures. Its value
corresponds to IRQF_PROBE_SHARED, which shouldn't be needed for this
driver, so removing this flag should be safe.
Signed-off-by: Matthijs Kooijman
Before, the DISCONNINT interrupt was enabled in
dwc2_enable_host_interrupts, but handled in dwc2_handle_common_intr,
while the RXFLVL interrupt was enabled in dwc2_enable_commont_interrupts
and handled in dwc_handle_hcd_intr.
This moves the enabling of these interrupts around to match the spot
This piece of code manually disabled interrupts, while there are
perfectly good functions to do this.
Technically, the old code really disabled _all_ interrupts, while the
new code only disables a specific list of interrupts, but that list of
interrupts includes all interrupts that are ever
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/hcd_intr.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/dwc2/hcd_intr.c b/drivers/staging/dwc2/hcd_intr.c
index 12b5a89..281c2f4 100644
--- a/drivers/staging/dwc2/hcd_intr.c
This simply defines a list of interrupts handled by the the host
interrupt handler.
Signed-off-by: Matthijs Kooijman matth...@stdin.nl
---
drivers/staging/dwc2/core.c | 4 +---
drivers/staging/dwc2/core.h | 4
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git
Before, enabling common interrupts would implicitly disable all other
interrupts and enabling host interrupts would disable all interrupts and
then enable both common and host interrupts.
Now, these two are properly separated: each enable function only enables
its own interrupts and leaves all
From: Stephen Warren swar...@wwwdotorg.org
The top-level hcd interrupt handlers already used irq_return_t, but the
functions to which it delegates the actual work and the common irq
handler returned plain ints. In addition, they used the IRQ_RETVAL in
the wrong way (but because of the values of
On Sat, Apr 06, 2013 at 12:41:02AM +0300, Felipe Balbi wrote:
Hi,
On Sat, Apr 06, 2013 at 12:21:52AM +0300, Felipe Balbi wrote:
Hi Greg,
Here's a giant pull request for v3.10. All patches have been on linux-next
for
quite a while and have gone through build and boot testing.
I
Hello.
On 04/05/2013 08:40 PM, Sergei Shtylyov wrote:
Here's the set of 4 patches against the Simon Horman's
'renesas.git' repo,
'renesas-next-20130404v2' tag and the 2 Ether patches I've reposted
yesterday.
It was created to fix the shortcomings in the R8A7779/Marzen USB
platform code
Aargh, resending as plain text.
Hi Matthijs,
Thanks for the work, this looks like a valuable set of patches.
But you really need to split this into a more manageable series of
patches. It's really difficult to review when you have so many different
things all munged together like this. It's
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Fix to return a negative error code from the error handling
case instead of 0, as returned elsewhere in this function.
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
---
drivers/usb/gadget/multi.c | 4 +++-
1 file changed, 3
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Fix to return a negative error code from the error handling
case instead of 0, as returned elsewhere in this function.
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
---
drivers/usb/gadget/f_obex.c | 1 +
1 file changed, 1 insertion(+)
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Fix to return a negative error code from the error handling
case instead of 0, as returned elsewhere in this function.
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
---
drivers/usb/gadget/cdc2.c | 4 +++-
1 file changed, 3
Hi,
On Fri, Apr 05, 2013 at 03:19:22PM -0700, Greg KH wrote:
On Sat, Apr 06, 2013 at 12:41:02AM +0300, Felipe Balbi wrote:
Hi,
On Sat, Apr 06, 2013 at 12:21:52AM +0300, Felipe Balbi wrote:
Hi Greg,
Here's a giant pull request for v3.10. All patches have been on
linux-next
On Sat, Apr 06, 2013 at 12:39:34PM +0800, Wei Yongjun wrote:
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Fix to return a negative error code from the error handling
case instead of 0, as returned elsewhere in this function.
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
93 matches
Mail list logo
