On Mon, 26 Nov 2012, Clemens Ladisch wrote:
> Alan Stern wrote:
> > On Mon, 26 Nov 2012, Oliver Neukum wrote:
> >> On Monday 26 November 2012 14:43:13 Clemens Ladisch wrote:
> >>> usb_autopm_get_interface() cannot be called from the USB probe callback.
> >>
> >> You can use usb_autopm_get_interfac
On Mon, Nov 26, 2012 at 04:07:38PM -0500, Alan Stern wrote:
> On Mon, 26 Nov 2012, Greg KH wrote:
>
> > Ah, here's the root of your problem, right? You need a way for your
> > hardware to tell the kernel that you have a regulator attached to a
> > specific device? Using the device path and hard-
On Mon, Nov 26, 2012 at 06:53:07PM +0530, Bhavik Kothari wrote:
> Hi Greg & Sarah,
>
> Would please tell us, what should be approach now?
Fix the patch based on the comments and resend it after testing that it
fixes the problem on your platform?
> If possible, Sarah, would you please give us the
On 11/27/2012 03:12 AM, the mail apparently from Alan Stern included:
On Mon, 26 Nov 2012, Andy Green wrote:
This adds a small optional API into drivers/base which deals with generating,
matching and registration of wildcard device paths.
>From a struct device * you can generate a string like
On 11/27/2012 03:16 AM, the mail apparently from Greg KH included:
On Mon, Nov 26, 2012 at 12:45:34PM +, Andy Green wrote:
+struct device_path list;
+DEFINE_MUTEX(lock);
Those are some very descriptive global variables you just created :(
I guess I can add the "static" if that will heal
On 11/27/2012 03:22 AM, the mail apparently from Greg KH included:
On Mon, Nov 26, 2012 at 12:45:34PM +, Andy Green wrote:
This adds a small optional API into drivers/base which deals with generating,
matching and registration of wildcard device paths.
>From a struct device * you can genera
On 11/27/2012 05:07 AM, the mail apparently from Alan Stern included:
On Mon, 26 Nov 2012, Greg KH wrote:
Ah, here's the root of your problem, right? You need a way for your
hardware to tell the kernel that you have a regulator attached to a
specific device? Using the device path and hard-cod
On 11/27/2012 12:20 AM, the mail apparently from Roger Quadros included:
Hi Andy,
On 11/26/2012 02:45 PM, Andy Green wrote:
This adds regulators which are controlled by the OMAP4 PandaBoard (ES)'s
EHCI logical root hub existing.
Without power control, the ULPI PHY + SMSC9614 on the Panda eats
On Wed, Nov 14, 2012 at 05:19:07PM +0100, Michael Grzeschik wrote:
> /**
> * hw_device_reset: resets chip (execute without interruption)
> * @ci: the controller
> @@ -237,6 +256,8 @@ int hw_device_reset(struct ci13xxx *ci, u32 mode)
> if (ci->platdata->flags & CI13XXX_DISABLE_STREAMING)
On Tue, Nov 27, 2012 at 4:06 AM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Nov 26, 2012 at 10:42:32AM -0800, Greg KH wrote:
>> On Mon, Nov 26, 2012 at 04:34:31PM +0200, Felipe Balbi wrote:
>> > Hi,
>> >
>> > On Mon, Nov 26, 2012 at 06:39:36AM -0800, Greg KH wrote:
>> > > On Sun, Nov 25, 2012 at 11:43:
ping
On 19 November 2012 17:03, Sachin Kamat wrote:
> linux/of.h was included twice.
>
> Signed-off-by: Sachin Kamat
> ---
> drivers/usb/musb/musb_dsps.c |1 -
> 1 files changed, 0 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/usb/musb/musb_dsps.c b/drivers/usb/musb/musb_dsps.c
> i
On Tue, Nov 27, 2012 at 5:07 AM, Alan Stern wrote:
> On Mon, 26 Nov 2012, Greg KH wrote:
>
>> Ah, here's the root of your problem, right? You need a way for your
>> hardware to tell the kernel that you have a regulator attached to a
>> specific device? Using the device path and hard-coding it in
Hi,
On Thu, Nov 22, 2012 at 10:35 AM, Ming Lei wrote:
> In the fail1~fail5 failure path, pm_runtime_disable() should
> be called to avoid 'Unbalanced pm_runtime_enable' error in
> next probe() which may be triggered by defer probe or next
> 'modprobe musb_hdrc'.
Greg/Felipe, could you queue the
On Monday 26 November 2012 13:40:28 Alan Stern wrote:
> Of course, there would still be a problem if the system was suspended
> while this program was running and using the modem. There's no way to
> tell usbfs that remote wakeup is required.
Exactly. Also there's an unavoidable window when kick
On Mon, Nov 26, 2012 at 11:22:32AM +0100, Sascha Hauer wrote:
> On Mon, Nov 26, 2012 at 05:29:31PM +0800, Peter Chen wrote:
> > On Wed, Nov 14, 2012 at 05:19:03PM +0100, Michael Grzeschik wrote:
> > > This patch adds support for a second and third clock to the chipidea
> > > driver. On
> > > moder
On Tue, Nov 27, 2012 at 02:50:26PM +0800, Peter Chen wrote:
> On Mon, Nov 26, 2012 at 11:22:32AM +0100, Sascha Hauer wrote:
> > On Mon, Nov 26, 2012 at 05:29:31PM +0800, Peter Chen wrote:
> > > On Wed, Nov 14, 2012 at 05:19:03PM +0100, Michael Grzeschik wrote:
> > > > This patch adds support for a
Dear Oliver, all,
do you please have any comments to the described issue? I'm still trying
to find the source of the problem, but I'm stuck.
Here are the tests I have done:
- gsm module on 2514b HUB connected to the DM365: cannot open two ttyACMs
- gsm module connected directly to the DM365: c
101 - 117 of 117 matches
Mail list logo
