Hi,
Rajesh Bhagat writes:
> [ text/plain ]
> Some freescale QorIQ platforms require to disable receiver detection
> in P3 for correct detection of USB devices. If GUSB3PIPECTL(DISRXDETINP3)
> is set, Core will change PHY power state to P2 and then perform receiver
> detection. After receiver de
On 2016-03-14 11:31, bruce m beach wrote:
Hello Greg
I believe I can change the Device descriptors in firmware, upload the new
firmware and reboot the stick but wouldn't the usb subsystem have the old
device descriptor from the previous hotplug/system boot?
Nope, the kernel reads the descrip
On Sun, Mar 13, 2016 at 09:31:39PM -0700, bruce m beach wrote:
> Hello Greg
>
> >> I believe I can change the Device descriptors in firmware, upload the new
> >> firmware and reboot the stick but wouldn't the usb subsystem have the old
> >> device descriptor from the previous hotplug/system boot?
On Mon, Mar 14, 2016 at 12:01:11AM -0400, Wade Mealing wrote:
>
> >> I'd like to extend the device audit subsystem to log some of the
> >> device additions/removals to the kernel
>
> > Why? What are you going to do with this information? What is it going
> > to be used for, are you going to act
Some freescale QorIQ platforms require to disable receiver detection
in P3 for correct detection of USB devices. If GUSB3PIPECTL(DISRXDETINP3)
is set, Core will change PHY power state to P2 and then perform receiver
detection. After receiver detection, Core will change PHY power state to
P3. Same
Hello Greg
>> I believe I can change the Device descriptors in firmware, upload the new
>> firmware and reboot the stick but wouldn't the usb subsystem have the old
>> device descriptor from the previous hotplug/system boot?
> Nope, the kernel reads the descriptor from the device when it is conne
>> I'd like to extend the device audit subsystem to log some of the
>> device additions/removals to the kernel
> Why? What are you going to do with this information? What is it going
> to be used for, are you going to act on it?
Me personally, no I'm not going to act on it. But it can be usef
On Sun, Mar 13, 2016 at 7:29 PM, Mario Limonciello
wrote:
>
>
> On 03/12/2016 02:33 PM, Andy Lutomirski wrote:
>> On Sat, Mar 12, 2016 at 11:35 AM, Andy Lutomirski
>> wrote:
>> Got it. I was barking up the wrong tree.
>>
>> Q: What happens if _Q66 runs concurrently with itself:
>>
>> A:
>>
>>
On Mon, Mar 14, 2016 at 09:09:22AM +0800, Lu Baolu wrote:
> On 03/11/2016 08:06 AM, Greg Kroah-Hartman wrote:
> > On Tue, Mar 08, 2016 at 03:53:44PM +0800, Lu Baolu wrote:
> >> +struct intel_mux_dev {
> >> + struct device *dev;
> >> + char*extcon_name;
> >> + char*cable
On 03/12/2016 02:33 PM, Andy Lutomirski wrote:
> On Sat, Mar 12, 2016 at 11:35 AM, Andy Lutomirski wrote:
> Got it. I was barking up the wrong tree.
>
> Q: What happens if _Q66 runs concurrently with itself:
>
> A:
>
> Method (_Q66, 0, NotSerialized) // _Qxx: EC Query
>
On Sun, Mar 13, 2016 at 10:14:16PM -0400, Wade Mealing wrote:
> Gday All,
>
> Seeking some advice, so I thought I'd talk to those involved about how I
> should go about this.
>
> I'd like to extend the device audit subsystem to log some of the
> device additions/removals to the kernel
Why? Wha
Gday All,
Seeking some advice, so I thought I'd talk to those involved about how I should
go about this.
I'd like to extend the device audit subsystem to log some of the device
additions/removals to the kernel
and figured that USB was a well maintained (and easily testable for me)
subsystem th
Hi,
On 03/11/2016 08:06 AM, Greg Kroah-Hartman wrote:
> On Tue, Mar 08, 2016 at 03:53:44PM +0800, Lu Baolu wrote:
>> Several Intel PCHs and SOCs have an internal mux that is used to
>> share one USB port between device controller and host controller.
>>
>> A usb port mux could be abstracted as the
On Sun, 13 Mar 2016, Oleksij Rempel wrote:
> Am 13.03.2016 um 16:30 schrieb Alan Stern:
> > On Sun, 13 Mar 2016, Oleksij Rempel wrote:
> >
> >> Hallo all,
> >>
> >> i need to sync device clock with host clock, since device will return
> >> SOF counter for each packet i need to use it as reference
Am 13.03.2016 um 16:30 schrieb Alan Stern:
> On Sun, 13 Mar 2016, Oleksij Rempel wrote:
>
>> Hallo all,
>>
>> i need to sync device clock with host clock, since device will return
>> SOF counter for each packet i need to use it as reference. Are there any
>> proper way to convert SOF to a host tim
On Sun, 13 Mar 2016, Oleksij Rempel wrote:
> Hallo all,
>
> i need to sync device clock with host clock, since device will return
> SOF counter for each packet i need to use it as reference. Are there any
> proper way to convert SOF to a host timestamp?
No, there isn't. There is no relationship
On 2016-03-01 16:32, Mathias Nyman wrote:
> On 18.02.2016 18:34, Mike Murdoch wrote:
>>
>>
>> On 2016-02-18 16:12, Mathias Nyman wrote:
>>> On 16.02.2016 23:58, main.ha...@googlemail.com wrote:
On 2016-02-08 15:31, Mathias Nyman wrote:
> Hi
>
> On 06.02.2016 19:08, Mike
17 matches
Mail list logo
