formation in that
> case. If the message was specific (e.g. "can't save CLEAR_TT_BUFFER state"), I
> left it. This series saves ~4.5KB of "out of memory" permutations in .text and
> .rodata. For modified lines, (x == NULL) was replaced with (!NULL) as well.
s/!NULL/!x/
Hi,
With this setting and AHBBRST at SBUSCFG as Incremental burst of
unspecified length, each unburst size can be taken as one single transfer.
It is benefit for unburst size transfer.
What is an 'unburst'?
Lothar Waßmann
--
___
Ka
Hi,
On Wed, Jul 29, 2015 at 10:30:22AM +0200, Lothar Waßmann wrote:
Hi,
With this setting and AHBBRST at SBUSCFG as Incremental burst of
unspecified length, each unburst size can be taken as one single
transfer.
It is benefit for unburst size transfer.
What is an 'unburst
Hi,
Felipe Balbi wrote:
On Fri, Jul 18, 2014 at 11:31:30AM +0200, Lothar Waßmann wrote:
There is no need to throw the baby out with the bath due to a bad
failure analysis. The commit:
7adb5c876e9c usb: musb: Fix panic upon musb_am335x module removal
came to a wrong conclusion about
Hi,
Felipe Balbi wrote:
Hi,,
On Mon, Jul 21, 2014 at 10:03:07AM +0200, Lothar Waßmann wrote:
Hi,
On Fri, Jul 18, 2014 at 11:31:29AM +0200, Lothar Waßmann wrote:
This patch makes it possible to use the musb driver with HW that
requires external regulators or clocks.
can
Hi,
Felipe Balbi wrote:
Hi,
On Fri, Jul 18, 2014 at 01:16:36PM -0300, Ezequiel Garcia wrote:
Hi Lothar,
On 18 Jul 11:31 AM, Lothar Waßmann wrote:
The first three patches do some source code cleanup in the files that
are modified in the subsequent patches.
I've applied
Hi,
On Fri, Jul 18, 2014 at 11:31:29AM +0200, Lothar Waßmann wrote:
This patch makes it possible to use the musb driver with HW that
requires external regulators or clocks.
can you provide an example of such HW ? Are you not using the internal
PHYs ?
The Ka-Ro electronics TX48 module
will produce a compile time error rather than an
unreachable entry in the list.
- consistently use tabs for indentation
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/musb/musb_am335x.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/musb
Without this patch overriding the USBOTG_ID pin by setting the iddig
bit in the USB_MODE register doesn't work because it happens too late
to be recognized correctly.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/musb/musb_core.c | 12 +++-
1 file changed, 7
Make sure all parameters are correctly set up before registering the
PHY with the USB framework.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/phy/phy-am335x.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/phy/phy-am335x.c b
that re-loading the module after an unload had no
effect. This is also fixed in this patch.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/musb/musb_am335x.c | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/musb
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/musb/musb_core.c |4
1 file changed, 4 deletions(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
index b841ee0..8623112 100644
--- a/drivers/usb/musb/musb_core.c
+++ b/drivers/usb/musb
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/phy/phy-am335x.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/phy/phy-am335x.c b/drivers/usb/phy/phy-am335x.c
index b70e055..91c71ab 100644
--- a/drivers/usb/phy/phy-am335x.c
+++ b
The first three patches do some source code cleanup in the files that
are modified in the subsequent patches.
Patch 4 carries the proper fix reported in commit:
7adb5c876e9c (usb: musb: Fix panic upon musb_am335x module removal)
Patch 6 makes the USBOTG_ID pin override via the USB_MODE
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/musb/musb_core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/musb/musb_core.c b/drivers/usb/musb/musb_core.c
index 8623112..f867b44 100644
--- a/drivers/usb/musb/musb_core.c
+++ b
This patch fixes the real cause of the crash that was fixed by
commit 7adb5c876e9c usb: musb: Fix panic upon musb_am335x module removal
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/phy/phy-am335x-control.c | 10 ++
1 file changed, 10 insertions(+)
diff --git
This patch makes it possible to use the musb driver with HW that
requires external regulators or clocks.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/phy/phy-am335x.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/phy/phy-am335x.c b/drivers/usb/phy
The first patch cleans up the coding style of the register accessor
functions which made my eyes sore.
The second patch makes the function added in
commit 943c13971c08 usb: musb: dsps: implement -set_mode()
actually functional by using the correct base address for the register accesses.
--
To
addresses in different places to
access the same register (phy_utmi).
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/musb/musb_dsps.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/musb_dsps.c
index
There is no reason for the register accessor functions not to adhere
to the CodingStyle rules.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/musb/musb_dsps.c | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/musb
(data-phy)) {
ret = PTR_ERR(data-phy);
goto err_clk;
How about accepting the old property too and print a warning, that it is
deprecated, rather than breaking all existing DT blobs?
Lothar Waßmann
--
___
Ka-Ro
Required properties:
-- compatible: Should be fsl,imx23-usbphy
+- compatible: fsl,imx23-usbphy for imx23 and imx28, fsl,imx6q-usbphy
+for imx6dq and imx6dl, fsl,imx6sl-usbphy for imx6sl
indentation?
Lothar Waßmann
--
___
Ka-Ro electronics
,
+ Remote wakeup is enabled,
+ and device is on the port\n);
Please don't line wrap message texts, since it makes it harder to grep
the kernel source for messages found in a logfile.
Lothar Waßmann
name the sequence:
atomic_read();
...
atomic_set();
does not magically become an atomic operation.
Lothar Waßmann
--
___
Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen
Phone: +49 2408 1402-0 | Fax: +49 2408
Hi,
Peter Chen writes:
On Wed, Jul 31, 2013 at 04:21:14PM +0200, Lothar Waßmann wrote:
This prevents the USB PHY refcount to be decremented below zero upon
unloading the ci-hdrc-imx module.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/chipidea
Hi,
Peter Chen writes:
On Wed, Jul 31, 2013 at 04:21:15PM +0200, Lothar Waßmann wrote:
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/chipidea/core.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/chipidea/core.c b
Hi,
Peter Chen writes:
On Wed, Jul 31, 2013 at 04:21:16PM +0200, Lothar Waßmann wrote:
commit 40dcd0e introduced the following code to the ci_hdrc_probe()
function:
+ if (!dev-of_node dev-parent)
+ dev-of_node = dev-parent-of_node;
This inadvertently
Peter Chen writes:
On Thu, Aug 01, 2013 at 10:40:42AM +0200, Lothar Waßmann wrote:
Hi,
Peter Chen writes:
On Wed, Jul 31, 2013 at 04:21:15PM +0200, Lothar Waßmann wrote:
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/chipidea/core.c |1
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/chipidea/core.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
index a5df24c..38b0a7a 100644
--- a/drivers/usb/chipidea/core.c
+++ b/drivers
This prevents the USB PHY refcount to be decremented below zero upon
unloading the ci-hdrc-imx module.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/chipidea/ci_hdrc_imx.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/chipidea
be chosen as
'y' though USB_EHCI_HCD or USB_GADGET (or both) were 'm' leading to a
situation where USB_CHIPIDEA_HOST or USB_CHIPIDEA_UDC vanished from
the config options producing a compilable but dysfunctional driver.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb/chipidea
The pointer to a platform_device struct must not be dereferenced after
the device has been unregistered.
This bug produces a crash when unloading the ci13xxx kernel module
compiled with CONFIG_PAGE_POISONING enabled.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
drivers/usb
32 matches
Mail list logo
