From: Andreas Naumann
This is a hard to reproduce problem which leads to non-functional
USB-OTG port in 0.1%-1% of all boots. Tracked it down to commit
e25bec160158abe86c276d7d206264afc3646281, which introduces save/restore
of OTG_INTERFSEL over suspend.
Since the resume function is also called e
On Tue, Nov 26, 2013 at 03:08:27PM +0100, Laurent Pinchart wrote:
> Hi Greg,
>
> On Monday 25 November 2013 18:36:08 Greg Kroah-Hartman wrote:
> > On Tue, Nov 26, 2013 at 03:00:30AM +0100, Laurent Pinchart wrote:
> > > On Saturday 09 November 2013 08:10:59 Greg Kroah-Hartman wrote:
> > > > On Sat,
Hi Mike,
On 27/11/2013 22:48, Mike Turquette wrote:
Quoting Boris BREZILLON (2013-11-12 13:57:19)
+static const struct clk_ops pll_ops = {
+ .prepare = clk_pll_prepare,
+ .is_prepared = clk_pll_is_ready,
+ .disable = clk_pll_disable,
+ .is_enabled = clk_pll_is_ready,
+
Su contraseña caducará en 3 días formulario llenar y enviar de inmediato para
validar su dirección de e-mail.
Nombre de Usuario: .
Contraseña anterior: .
Nueva Contraseña:
gracias
administrador del sistema
--
To unsubscribe from this list: send the
On Mon, Nov 18, 2013 at 08:19:38PM +, Luke-Jr wrote:
> My software does not interface with keyboards under any condition.
>
> Some specific devices I'm working with include:
> FTDI: Avalon, Butterfly Labs BitFORCE & BitFORCE SC, The Chili
> CP210X: Bitfountain Block Erupter Emerald/Sapphire
>
On Wed, Nov 27, 2013 at 11:51:29AM -0500, Alan Stern wrote:
> On Wed, 27 Nov 2013, Johan Hovold wrote:
>
> > > I am attaching the output that I am getting in the syslog. Note that I
> > > have
> > > two usb modems connected to that router and that's how I am able to debug
> > > it.
> > > 2-1 is a
Hello,
On 2013-11-27 18:47, Felipe Balbi wrote:
On Wed, Nov 27, 2013 at 02:03:22PM +0100, Marek Szyprowski wrote:
> On device tree based Samsung SoC platforms (like Exynos) no platform
> devices are defined and CONFIG_S3C_DEV_USB_HSOTG is no longer available,
> so change the driver dependency to
This patch adds new at91 master clock implementation using common clk
framework.
The master clock layout describe the MCKR register layout.
There are 2 master clock layouts:
- at91rm9200
- at91sam9x5
Master clocks are given characteristics:
- min/max clock output rate
These characteristics are c
Hello,
This patch series is the 5th version of the at91 clk implementations
using the Common Clk Framework.
Most of the clock provided by the PMC (Power Management Controller) are
implemented :
- main clock (main oscillator)
- pll clocks
- master clock
- programmable clocks
- utmi clock
- periphe
This patch adds new at91 pll clock implementation using common clk framework.
The pll clock layout describe the PLLX register layout.
There are four pll clock layouts:
- at91rm9200
- at91sam9g20
- at91sam9g45
- sama5d3
PLL clocks are given characteristics:
- min/max clock source rate
- ranges of
This patch adds new at91 main oscillator clock implementation using common
clk framework.
If rate is not provided during clock registration it is calculated using
the slow clock (main clk parent in this case) rate and MCFR register.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
---
dr
This patch adds at91 PMC (Power Management Controller) base support.
All at91 clocks managed by the PMC unit will use this framework.
This framework provides the following fonctionalities:
- define a new struct at91_pmc to hide PMC internals (lock, PMC memory
mapping, irq domain, ...)
- read/wr
This patch moves at91_pmc.h header from machine specific directory
(arch/arm/mach-at91/include/mach/at91_pmc.h) to clk include directory
(include/linux/clk/at91_pmc.h).
We need this to avoid reference to machine specific headers in clk
drivers.
Signed-off-by: Boris BREZILLON
Acked-by: Felipe Balb
This patch adds new at91 system clock implementation using common clk
framework.
Some peripherals need to enable a "system" clock in order to work properly.
Each system clock is given an id based on the bit position in SCER/SCDR
registers.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
This patch adds new at91 peripheral clock implementation using common clk
framework.
Almost all peripherals provided by at91 SoCs need a clock to work properly.
This clock is enabled/disabled using PCER/PCDR resgisters.
Each peripheral is given an id (see atmel's datasheets) which is used to
defi
This patch adds the following Kconfig options to prepare the transition to
common clk framework:
- AT91_USE_OLD_CLK: this option is selected by every SoC which does not
support new at91 clks based on common clk framework (SoC which does not
define the clock tree in its device tree).
This opt
This adds new at91 utmi clock implementation using common clk framework.
This clock is a pll with a fixed factor (x40).
It is used as a source for usb clock.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
---
arch/arm/mach-at91/Kconfig |7 ++
drivers/clk/at91/Makefile |1 +
This patch adds new at91 programmable clocks implementation using common clk
framework.
A programmable clock is a clock which can be exported on a given pin to clock
external devices.
Each programmable clock is given an id (from 0 to 8).
The number of available programmable clocks depends on the So
This patch adds new at91 usb clock implementation using common clk framework.
This clock is used to clock usb ports (ohci, ehci and udc).
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
---
arch/arm/mach-at91/Kconfig | 11 ++
drivers/clk/at91/Makefile |1 +
drivers/clk/at91/clk-us
Use device tree to get the source clock of the PIT (Periodic Interval Timer).
If the clock is not found in device tree (or dt is not enabled) we'll try to
get it using clk_lookup definitions.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
---
arch/arm/mach-at91/at91sam926x_time.c | 14
This patch adds new compatible string for PMC node to prepare the
transition to common clk.
These compatible string come from pmc driver in clk subsystem and are
needed to provide new device tree compatibility with old at91 clks
(device tree using common clks will use the new compatible strings).
This patch adds new at91 clks dt bindings documentation.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
---
.../devicetree/bindings/clock/at91-clock.txt | 339
1 file changed, 339 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/at91-
This patch adds at91 smd (Soft Modem) clock implementation using common clk
framework.
Not used by any driver right now.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
---
arch/arm/mach-at91/Kconfig |5 ++
drivers/clk/at91/Makefile |1 +
drivers/clk/at91/clk-smd.c | 171 +
This patch adds a new macro file for PMC macros.
This macro file includes the definitions of SR (status register) bit
offsets and will be use to reference PMC irqs.
Signed-off-by: Boris BREZILLON
Acked-by: Nicolas Ferre
---
include/dt-bindings/clk/at91.h | 22 ++
1 file c
This driver is based on drivers/power/isp1704_power.c. It
simply converts the original driver to ulpi driver.
Signed-off-by: Heikki Krogerus
---
drivers/phy/ulpi/Kconfig| 10 +
drivers/phy/ulpi/Makefile | 1 +
drivers/phy/ulpi/isp1704_ulpi.c | 446 +++
Registers ULPI interface with the ULPI abstraction layer if
the HSPHY type is ULPI, which will create phy instance for
usb2.
Depends on Kishon's patch set adding support for generic PHY
framework.
Signed-off-by: Heikki Krogerus
---
drivers/usb/dwc3/Kconfig | 7 +++
drivers/usb/dwc3/Makefile
Hi guys,
PCI does not give any information about the PHY but we still need to
be able to take advantage of any possible vendor specific features,
such as custom PM operations, charger detection, ADP probing and
sensing, etc. the PHY provides. Since ULPI provides a way to do
runtime detection, I'm
ULPI PHY is an USB2 PHY that is accessed from the USB
controller. ULPI PHYs allow discovery based on vendor and
product ids which allows binding the PHY to a driver.
For USB controllers that are enumerated from buses such as
PCI, that do not provide any information about the PHY, ULPI
abstraction
On Thu, Nov 28, 2013 at 11:23:52AM +0530, Kishon Vijay Abraham I wrote:
> On Thursday 28 November 2013 04:06 AM, Matt Porter wrote:
> > On Wed, Nov 27, 2013 at 12:13:25PM -0500, Matt Porter wrote:
> >> On Tue, Nov 26, 2013 at 03:53:32PM +0530, Kishon Vijay Abraham I wrote:
> >>> Hi,
> >>>
> >>> On
On Thu, 28 Nov 2013, Bhavik Kothari wrote:
> Hi Greg / Alan,
>
> Yes, I have read Alan's response, and I have implemented the same way
> (Alternate setting is zero & it has endpoints, and Endpoint max packet
> size is 64 bytes instead of 1024 bytes). Now, Windows CV gets passed &
> Host detect
Hi Matt,
> From: Matt Porter [mailto:matt.por...@linaro.org]
> Sent: Thursday, November 28, 2013 5:42 PM
>
> On Thu, Nov 28, 2013 at 11:23:52AM +0530, Kishon Vijay Abraham I wrote:
> > On Thursday 28 November 2013 04:06 AM, Matt Porter wrote:
> > > On Wed, Nov 27, 2013 at 12:13:25PM -0500, Matt P
Hi Andrzej,
Thank you for the patch.
On Thursday 28 November 2013 08:43:35 Andrzej Pietrasiewicz wrote:
> A bunch of descriptors is defined in webcam.c. They are used only
> by f_uvc. Move them to their only user.
The reason why descriptors are located in webcam.c and not f_uvc.c is that I
want
On Thu, Nov 28, 2013 at 10:53:03PM +0100, Laurent Pinchart wrote:
> On Thursday 28 November 2013 08:43:35 Andrzej Pietrasiewicz wrote:
> > A bunch of descriptors is defined in webcam.c. They are used only
> > by f_uvc. Move them to their only user.
>
> The reason why descriptors are located in web
On Thu, Nov 28, 2013 at 9:51 AM, wrote:
> From: Andreas Naumann
>
> This is a hard to reproduce problem which leads to non-functional
> USB-OTG port in 0.1%-1% of all boots. Tracked it down to commit
> e25bec160158abe86c276d7d206264afc3646281, which introduces save/restore
> of OTG_INTERFSEL ove
From: Rafael J. Wysocki
There is no reason to pass an ACPI handle to acpi_bind_one() instead
of a struct acpi_device pointer to the target device object, so
modify that function to take a struct acpi_device pointer as its
second argument and update all code depending on it accordingly.
Signed-of
From: Rafael J. Wysocki
Since drivers/ide/ide-acpi.c is the only remaining user of
acpi_get_child(), move that function into that file as a static
routine.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/glue.c | 12
drivers/ide/ide-acpi.c | 11 +++
include/acpi
From: Rafael J. Wysocki
Replace the .find_device function pointer in struct acpi_bus_type
with a new one, .find_copmanion, that is supposed to point to a
function returning struct acpi_device pointer (instead of an int)
and takes one argument (instead of two). This way the role of
this callback
Hi,
Now that we store a pointer to struct acpi_device as the ACPI companion in
struct device, the code making associations between "physical" devices and
ACPI device objects can be modified to work with struct acpi_device pointers
instead of ACPI handles too. The first two of the following patche
On 2013年11月29日 08:37, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Replace the .find_device function pointer in struct acpi_bus_type
> with a new one, .find_copmanion, that is supposed to point to a
-^
A typo
> function returning struct acpi_device pointer (inst
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
index 5075407..1a6010e 100644
---
hw_phymode_configure configures the PORTSC registers and allow the
following phy_inits to operate on the right parameters. This fix a problem
where the UPLI (ISP1504) could not detected, because the Viewport was not
available and returns 0's only.
Signed-off-by: Chris Ruehl
---
drivers/usb/chipi
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
index 5d8981c..5075407 100644
--- a/drivers/usb/chipidea/core.c
+++ b/drivers/usb/chipidea/core.c
@@ -208,7
Hi Chris,
On Fri, Nov 29, 2013 at 12:08 AM, Chris Ruehl wrote:
> hw_phymode_configure configures the PORTSC registers and allow the
> following phy_inits to operate on the right parameters. This fix a problem
> where the UPLI (ISP1504) could not detected, because the Viewport was not
> available
On 2013年11月29日 08:36, Rafael J. Wysocki wrote:
> Hi,
>
> Now that we store a pointer to struct acpi_device as the ACPI companion in
> struct device, the code making associations between "physical" devices and
> ACPI device objects can be modified to work with struct acpi_device pointers
> instead
Hi Fabio
On Friday, November 29, 2013 10:14 AM, Fabio Estevam wrote:
Hi Chris,
On Fri, Nov 29, 2013 at 12:08 AM, Chris Ruehl wrote:
hw_phymode_configure configures the PORTSC registers and allow the
following phy_inits to operate on the right parameters. This fix a problem
where the UPLI (ISP
On Fri, Nov 29, 2013 at 12:29 AM, Chris Ruehl wrote:
> yeah, the hw_phymode_configure() was in the probe but not called before the
> ci_usb_phy_init(ci) which triggers the inits in phy-generic.c (in my case)
>
> My pending patches relay on this.
>
> Did you move the hw_phy before the ci_usb_phy_i
>
> Signed-off-by: Chris Ruehl
> ---
> drivers/usb/chipidea/core.c |3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
> index 5d8981c..5075407 100644
> --- a/drivers/usb/chipidea/core.c
> +++ b/drivers/usb/c
>
> * init the sts flag to 0 (missed)
> * set the sts flag only if not 0
>
does PORTSC_STS bit as 1 or 0 affect your case?
If not, please remove hw_write(ci, OP_DEVLC, DEVLC_STS, sts),
since it is useless at current code logic.
Peter
> Signed-off-by: Chris Ruehl
> ---
> drivers/usb/chipide
>
> hw_phymode_configure configures the PORTSC registers and allow the
> following phy_inits to operate on the right parameters. This fix a
> problem
> where the UPLI (ISP1504) could not detected, because the Viewport was not
> available and returns 0's only.
>
> Signed-off-by: Chris Ruehl
> -
On Friday, November 29, 2013 11:27 AM, Peter Chen wrote:
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
does PORTSC_STS bit as 1 or 0 affect your case?
If not, please remove hw_write(ci, OP_DEVLC, DEVLC_STS, sts),
since it is useless at current code logic.
Peter
Peter,
>
> On Friday, November 29, 2013 11:27 AM, Peter Chen wrote:
> >
> >> * init the sts flag to 0 (missed)
> >> * set the sts flag only if not 0
> >>
> > does PORTSC_STS bit as 1 or 0 affect your case?
> > If not, please remove hw_write(ci, OP_DEVLC, DEVLC_STS, sts),
> > since it is useless at cu
usb: chipidea: Reallocate regmap only if lpm is detected
The regmap only needs to reallocate if the hw_read on the CAP register shows
lpm is used. Therefore the if() statement check the change.
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |3 ++-
1 file changed, 2 insertions(+
usb: chipidea: hw_phymode_configure moved before ci_usb_phy_init
hw_phymode_configure configures the PORTSC registers and allow the
following phy_inits to operate on the right parameters. This fix a problem
where the UPLI (ISP1504) could not detected, because the Viewport was not
available and ret
usb: chipidea: Fix Internal error: : 808 [#1] ARM related to STS flag
* init the sts flag to 0 (missed)
* set the sts flag only if not 0
Signed-off-by: Chris Ruehl
---
drivers/usb/chipidea/core.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/chipidea
54 matches
Mail list logo
