On 04/14/2014 06:11 PM, Timur Tabi wrote:
On 04/14/2014 02:52 AM, Mathias Nyman wrote:
This was the conclusion we reached after some discussion with Linus W.
Initially this was just a GPIO driver, but Linus correctly spotted that
Baytrail has many pinctrl-like features (like pin muxing, etc
On 04/12/2014 01:54 AM, Timur Tabi wrote:
On Tue, Jun 18, 2013 at 6:33 AM, Mathias Nyman
wrote:
Pins may be muxed to alternate function instead of gpio by firmware.
This driver does not touch the pin muxing and expect firmare
to set pin muxing and pullup/down properties properly.
Signed-off
o-op
right away.
All these changes allows us to remove the entire cancel_cmd_list code.
The functions waiting for a command to finish no longer have their own timeouts.
They will wait either until the command completes normally,
or until the whole command abortion is done.
Signed-off-by: Mat
are freed in the command completion event handler.
Also add a check that prevents queuing commands if host is dying
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-mem.c | 2 ++
drivers/usb/host/xhci-ring.c | 34 ++
drivers/usb/host/xhci.c | 2
Remove the per-device command list and handle_cmd_in_cmd_wait_list()
and use the completion and status variables found in the
command structure in the global command list.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 --
drivers/usb/host/xhci-mem.c | 1 -
drivers/usb
ommand queue up.(Just so that we won't leak
memory in the middle of the patch set)
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 21 +++--
drivers/usb/host/xhci-ring.c | 106 ---
drivers/usb/host/xhci.c | 194
ring abortion process. Functions waiting for an aborted command to finish
are
called after the command abortion is completed.
Mathias Nyman (4):
xhci: Use command structures when queuing commands on the command ring
xhci: Add a global command queue
xhci: Use completion and status in global comman
Hi
On 04/03/2014 12:29 AM, Julius Werner wrote:
Hi Mathias,
The patch looks fine. Mathias is taking over for xHCI driver
maintainership in 3.15. He's currently handling queuing bug fix patches
for 3.14 while I finish queueing feature patches for 3.15. Mathias,
will you test and queue this u
On 04/02/2014 02:41 PM, Alexander Gordeev wrote:
On Tue, Mar 25, 2014 at 03:27:30PM +0100, Alexander Gordeev wrote:
On Thu, Mar 06, 2014 at 01:56:46PM -0800, Sarah Sharp wrote:
What do you mean by this sentence? Are you fixing some bug in those two
functions, or just cleaning up how they look?
On 03/25/2014 08:42 PM, Julius Werner wrote:
The current XHCI driver recalculates the Context Entries field in the
Slot Context on every add_endpoint() and drop_endpoint() call. In the
case of drop_endpoint(), it seems to assume that the add_flags will
always contain every endpoint for the new co
Don't return the IN_LVL_BIT directly, a high gpio line returned
value "1073741824" intestead of "1" because IN_LVL_BIT is BIT(30)
Tested-by: Jerome Blin
Signed-off-by: Mathias Nyman
---
drivers/gpio/gpio-lynxpoint.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
On 03/21/2014 11:41 PM, David Cohen wrote:
Hi Mathias,
Thanks for commenting. That would be actually the v1 of my patch :)
I changed after I see the proper function has __maybe_unused flag.
But I'm fine with Sarah picking any of the patch's versions.
Guess you're handling the review of this
On 03/21/2014 11:35 AM, Mathias Nyman wrote:
+void xhci_handle_command_timeout(unsigned long data)
+{
+ struct xhci_hcd *xhci;
+ int ret;
+ unsigned long flags;
+ xhci = (struct xhci_hcd *) data;
+ /* mark this command to be cancelled
On 03/21/2014 12:01 PM, Denis Turischev wrote:
The same issue like with Panther Point chipsets. If the USB ports are
switched to xHCI on shutdown, the xHCI host will send a spurious interrupt,
which will wake the system. Some BIOS have work around for this, but not all.
One example is Compulab's
ommand queue up.(Just so that we won't leak
memory in the middle of the patch set)
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 21 +++--
drivers/usb/host/xhci-ring.c | 106 ---
drivers/usb/host/xhci.c | 194
are freed in the command completion event handler.
Also add a check that prevents queuing commands if host is dying
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-mem.c | 2 ++
drivers/usb/host/xhci-ring.c | 34 ++
drivers/usb/host/xhci.c | 2
will wait either until the command completes normally,
or until the whole command abortion is done.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 +-
drivers/usb/host/xhci-mem.c | 15 +-
drivers/usb/host/xhci-ring.c | 337 +--
d
Remove the per-device command list and handle_cmd_in_cmd_wait_list()
and use the completion and status variables found in the
command structure in the global command list.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 --
drivers/usb/host/xhci-mem.c | 1 -
drivers/usb
s "ABORTED" and start
the ring abortion process. Functions waiting for an aborted command to finish
are
called after the command abortion is completed.
Mathias Nyman (4):
xhci: Use command structures when queuing commands on the command ring
xhci: Add a global command queue
xhci: Use
rface side of this hardware forever. ;-)
Hate to admit it but so it seems :)
Mika/Mathias: any comments?
Patch looks fine
Acked-by: Mathias Nyman
-Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.
e TD fragment rules for xHCI 1.0 hosts,
but for now, revert this patch until scatter gather can be properly supported.
Signed-off-by: Mathias Nyman
Cc: stable
---
drivers/net/usb/ax88179_178a.c | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/net/usb/ax88179_178a.c b/dr
ux-usb&m=139411871213253&w=2
http://marc.info/?l=linux-usb&m=139361293103188&w=2
-Mathias
Mathias Nyman (2):
Revert "xhci 1.0: Limit arbitrarily-aligned scatter gather."
Revert "USBNET: ax88179_178a: enable tso if usb host supports sg dma"
drivers
lement the TD fragment rules required, but for now
this patch needs to be reverted to get USB 3.0 mass storage devices working at
the
level they used to.
Signed-off-by: Mathias Nyman
Cc: stable
---
drivers/usb/host/xhci.c | 14 +++---
1 file changed, 3 insertions(+), 11 deletions(-)
On 03/03/2014 08:37 PM, Greg KH wrote:
On Mon, Mar 03, 2014 at 07:30:17PM +0200, Mathias Nyman wrote:
xHCI driver has its own pci probe function that will call usb_hcd_pci_probe
to register its usb-2 bus, and then continue to manually register the
usb-3 bus. usb_hcd_pci_probe does a
the runtime suspend by increasing the usage count in the
beginning of xhci_pci_probe, and decrease it once the usb-3 bus is
ready.
xhci-platform driver is not using usb_hcd_pci_probe to set up
busses and should not need to have it's usage count increased during probe.
Signed-off-by: Mathias
ycle.
-Mathias
Mathias Nyman (1):
xhci: Prevent runtime pm from autosuspending during initialization
drivers/usb/host/xhci-pci.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
--
1.8.1.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Remove the per-device command list and handle_cmd_in_cmd_wait_list()
and use the completion and status variables found in the
command structure in the global command list.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 ---
drivers/usb/host/xhci-mem.c | 1 -
drivers
ommand queue up.(Just so that we won't leak
memory in the middle of the patch set)
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 21 +++--
drivers/usb/host/xhci-ring.c | 105 ---
drivers/usb/host/xhci.c | 194
are freed in the command completion event handler.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-mem.c | 8
drivers/usb/host/xhci-ring.c | 21 +
drivers/usb/host/xhci.c | 2 --
drivers/usb/host/xhci.h | 1 +
4 files changed, 26 insertions(+), 6
will wait either until the command completes normally,
or until the whole command abortion is done.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 +-
drivers/usb/host/xhci-mem.c | 15 +-
drivers/usb/host/xhci-ring.c | 335 +--
d
y tag the current command as "ABORTED" and start
the ring abortion process. Functions waiting for an aborted command to finish
are
called after the command abortion is completed.
Mathias Nyman (4):
xhci: Use command structures when queuing commands on the command ring
xhci: Add
the runtime suspend by increasing the usage count in the
beginning of xhci_pci_probe, and decrease it once the usb-3 bus is
ready.
xhci-platform driver is not using usb_hcd_pci_probe to set up
busses and should not need to have it's usage count increased during probe.
Signed-off-by: Mathias
On 01/08/2014 09:53 PM, David Cohen wrote:
On Wed, Jan 08, 2014 at 10:48:06AM -0500, Alan Stern wrote:
On Tue, 7 Jan 2014, Greg KH wrote:
On Tue, Jan 07, 2014 at 05:44:26PM -0800, David Cohen wrote:
From: jianqian
There is a possible kernel panic faced on xhci_suspend().
Due to kernel modif
On 02/05/2014 04:21 AM, Dan Williams wrote:
Hi Mathias, comments below:
s/xhci_check_bandwith/xhci_check_bandwidth/
s/strucure/structure/
s/strucure/structure/
s/requre/require/
s/strucure/structure/
Thanks
I guess I need to start using a spell checker for commit messages.
One cleanup we m
inish
are
called after the command abortion is completed.
Mathias Nyman (10):
xhci: Use command structures when calling xhci_configure_endpoint
xhci: use a command structure internally in xhci_address_device()
xhci: use command structures for xhci_queue_slot_control()
xhci: use command stru
Preparing for the global command queue by changing functions calling
xhci_queue_slot_control() to internally use command structures
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci.c | 34 +-
1 file changed, 29 insertions(+), 5 deletions(-)
diff --git a
Prepare for the global command ring by using command structures
internally in functions calling xhci_queue_stop_endpoint()
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 15 +--
drivers/usb/host/xhci.c | 3 +++
2 files changed, 16 insertions(+), 2 deletions
)
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 10 ++---
drivers/usb/host/xhci.c | 97
2 files changed, 56 insertions(+), 51 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index 1e2f3f4
ive a "command handled" event
in a later patch.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 8 ++--
drivers/usb/host/xhci-ring.c | 94 ++--
drivers/usb/host/xhci.c | 47 +++---
drivers/usb/host/x
Create a list to store command structures, add a strucure to it every time
a command is submitted, and remove it from the list once we get a
command completion event matching the command.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-mem.c | 8
drivers/usb/host/xhci-ring.c
They will wait either until the command completes normally,
or until the whole command abortion is done.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 +-
drivers/usb/host/xhci-mem.c | 15 +-
drivers/usb/host/xhci-ring.c | 336 +--
d
Remove the per-device command list and handle_cmd_in_cmd_wait_list()
and use the completion and status variables found in the
command structure in the global command list.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 --
drivers/usb/host/xhci-mem.c | 1 -
drivers/usb
Prepare for the global command ring by using command structures
internally in functions calling xhci_queue_reset_ep()
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 5 +
drivers/usb/host/xhci.c | 6 ++
2 files changed, 11 insertions(+)
diff --git a/drivers/usb
Prepare for the global command ring by using command structures
internally in functions calling xhci_queue_new_dequeue_state()
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 3 +++
drivers/usb/host/xhci.c | 6 ++
2 files changed, 9 insertions(+)
diff --git a/drivers
Preparing for the global command queue by using command strucure
in xhci_address_device
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci.c | 22 +-
1 file changed, 17 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index
On 01/14/2014 02:37 PM, David Laight wrote:
From: Mathias Nyman
...
The fact that you are having to allocate memory ion an ISR ought also to be
ringing alarm bells.
It did.
Other options are as you said to use a 'software command ring'. Either
just pre-allocate a full command rin
IMHO the xhci driver is already far too complicated, and this probably just
makes
it even worse.
This is an attempt to make it cleaner and less complicated.
In the end this series removes far more more code than it adds:
5 files changed, 373 insertions(+), 530 deletions(-)
The timers are also
)
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 10 ++---
drivers/usb/host/xhci.c | 95 +++-
2 files changed, 54 insertions(+), 51 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index 1e2f3f4
Prepare for the global command ring by using command structures
internally in functions calling xhci_queue_reset_ep()
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 5 +
drivers/usb/host/xhci.c | 6 ++
2 files changed, 11 insertions(+)
diff --git a/drivers/usb
Prepare for the global command ring by using command structures
internally in functions calling xhci_queue_new_dequeue_state()
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ring.c | 3 +++
drivers/usb/host/xhci.c | 6 ++
2 files changed, 9 insertions(+)
diff --git a/drivers
Preparing for the global command queue by changing functions calling
xhci_queue_slot_control() to internally use command structures
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci.c | 34 +-
1 file changed, 29 insertions(+), 5 deletions(-)
diff --git a
Create a list to store command structures, add a strucure to it every time
a command is submitted, and remove it from the list once we get a
command completion event matching the command.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-mem.c | 8
drivers/usb/host/xhci-ring.c
Preparing for the global command queue by using command strucure
in xhci_address_device
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci.c | 22 +-
1 file changed, 17 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
index
They will wait either until the command completes normally,
or until the whole command abortion is done.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 +-
drivers/usb/host/xhci-mem.c | 15 +-
drivers/usb/host/xhci-ring.c | 336 +--
d
Remove the per-device command list and handle_cmd_in_cmd_wait_list()
and use the completion and status variables found in the
command structure in the global command list.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 11 --
drivers/usb/host/xhci-mem.c | 1 -
drivers/usb
Prepare for the global command ring by using command structures
internally in functions calling xhci_queue_stop_endpoint()
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 14 --
drivers/usb/host/xhci.c | 3 +++
2 files changed, 15 insertions(+), 2 deletions
ive a "command handled" event
in a later patch.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 8 ++--
drivers/usb/host/xhci-ring.c | 94 ++--
drivers/usb/host/xhci.c | 47 +++---
drivers/usb/host/x
nd to finish
are
called after the command abortion is completed.
Mathias Nyman (10):
xhci: Use command structures when calling xhci_configure_endpoint
xhci: use a command structure internally in xhci_address_device()
xhci: use command structures for xhci_queue_slot_control()
xh
On 12/03/2013 05:00 PM, Linus Walleij wrote:
This uses the new API for tagging GPIO lines as in use by
IRQs. This enforces a few semantic checks on how the underlying
GPIO line is used.
Cc: Andy Shevchenko
Cc: Mika Westerberg
Cc: Mathias Nyman
Signed-off-by: Linus Walleij
---
ChangeLog v1
interrupt enable bit for the pin as well.
Signed-off-by: Mika Westerberg
Acked-by: Mathias Nyman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
Commit-ID: 0f531431d3de88efb4234d6c0ce22089ec035a38
Gitweb: http://git.kernel.org/tip/0f531431d3de88efb4234d6c0ce22089ec035a38
Author: Mathias Nyman
AuthorDate: Fri, 13 Sep 2013 17:02:29 +0300
Committer: Ingo Molnar
CommitDate: Sat, 14 Sep 2013 08:06:28 +0200
x86/intel/lpss: Add pin
are possible to add later.
Signed-off-by: Mathias Nyman
---
arch/x86/Kconfig |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 30c40f0..91f72b5 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -482,11 +482,12 @@ config
Missing pm_runtime_disable call in driver remove path caused
an unbalanaced pm_runtime_enable warning when driver was reloaded
Signed-off-by: Mathias Nyman
---
drivers/gpio/gpio-lynxpoint.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/gpio/gpio-lynxpoint.c b
On 06/18/2013 06:17 PM, Linus Walleij wrote:
On Tue, Jun 18, 2013 at 1:33 PM, Mathias Nyman
wrote:
Add support for gpio on Intel BayTrail platforms. BayTrail supports 3 banks
of gpios called SCORE, NCORE ans SUS with 102, 28 and 44 gpio pins.
Supports gpio interrupts and ACPI gpio events
uctures from pinctrl instead of custom
gpio_banks
Changes since v1:
- generic cleanups suggested by Andy S.
- removed text about pin muxing
- added missing 44:th pin to SUS controller
- added level triggering option
- prevent "forever loop" in case pin is stuck in "interrupt trigger
muxing and expect firmare
to set pin muxing and pullup/down properties properly.
Signed-off-by: Mathias Nyman
---
drivers/pinctrl/Kconfig| 12 +
drivers/pinctrl/Makefile |1 +
drivers/pinctrl/pinctrl-baytrail.c | 543
3 files changed
On 06/13/2013 06:45 PM, Linus Walleij wrote:
On Thu, Jun 13, 2013 at 5:06 PM, Mathias Nyman
wrote:
After looking at the pinctrl subsystem that Linus W. suggested I think
pinctrl suits platforms that don't have firmware configuring the pins
before the operating system is started, or when
ps suggested by Andy S.
- removed text about pin muxing
- added missing 44:th pin to SUS controller
- added level triggering option
- prevent "forever loop" in case pin is stuck in "interrupt triggered" status,
Mathias Nyman (1):
gpio: add Intel BayTrail gpio driver
Add support for gpio on Intel BayTrail platforms. BayTrail supports 3 banks
of gpios called SCORE, NCORE ans SUS with 102, 28 and 44 gpio pins.
Supports gpio interrupts and ACPI gpio events.
Signed-off-by: Mathias Nyman
---
drivers/gpio/Kconfig | 12 +
drivers/gpio/Makefile
On 05/30/2013 10:26 PM, Linus Walleij wrote:
On Wed, May 29, 2013 at 10:01 AM, Mathias Nyman
wrote:
Add support for gpio on Intel BayTrail platforms. BayTrail supports 3 banks
of gpios called SCORE, NCORE ans SUS with 102, 28 and 43 gpio pins.
Supports gpio interrupts
Pins may be muxed to
firmare
to set pin muxing and pullup/down properties properly.
Signed-off-by: Mathias Nyman
---
drivers/gpio/Kconfig | 12 +
drivers/gpio/Makefile|1 +
drivers/gpio/gpio-baytrail.c | 539 ++
3 files changed, 552 insertions(+), 0 deletions
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 16 +++-
drivers/usb/host/xhci.c |4 ++--
drivers/usb/host/xhci.h |5 +
3 files changed, 14 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/host/xhci-hub.c b/drivers/usb/host/xhci-hub.c
names.
Changes since v1:
-Use kstrto* and unsigned values in sysfs functions as Alan Stern suggested
Changes since v2:
- Add Documentation/ABI/testing/sysfs-bus-usb entries for new sysfs attributes
- store l1_timeout value in microseconds instead of xHCI specific values
Mathias Nyman (4):
usb
USB 3.0 link PM code does.
The same xhci_change_max_exit_latency() function is used as with USB3
but code is pulled out from #ifdef CONFIG_PM as USB2.0 BESL LPM
funcionality does not depend on CONFIG_PM.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ext-caps.h |1 +
drivers/usb/host
Adds abitilty to tune L1 timeout (inactivity timer for usb2 link sleep)
and BESL (best effort service latency)via sysfs.
This also adds a new usb2_lpm_parameters structure with those variables to
struct usb_device.
Signed-off-by: Mathias Nyman
---
Documentation/ABI/testing/sysfs-bus-usb | 27
Hardware link powermanagement in usb2 is a per-port capability.
Previously support for hw lpm was enabled for all ports if any usb2 port
supported it.
Now instead cache the capability values and check them for each port
individually
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci
On 05/21/2013 04:48 PM, Greg KH wrote:
On Tue, May 21, 2013 at 01:43:37PM +0300, Mathias Nyman wrote:
Adds abitilty to tune L1 timeout (inactivity timer for usb2 link sleep)
and BESL (best effort service latency)via sysfs.
If you add/remove/change sysfs files, you also need to do the same in
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-hub.c | 16 +++-
drivers/usb/host/xhci.c |4 ++--
drivers/usb/host/xhci.h |5 +
3 files changed, 14 insertions(+), 11 deletions(-)
diff --git a/drivers/usb/host/xhci-hub.c b/drivers/usb/host/xhci-hub.c
Hardware link powermanagement in usb2 is a per-port capability.
Previously support for hw lpm was enabled for all ports if any usb2 port
supported it.
Now instead cache the capability values and check them for each port
individually
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci
Adds abitilty to tune L1 timeout (inactivity timer for usb2 link sleep)
and BESL (best effort service latency)via sysfs.
This also adds a new usb2_lpm_parameters structure with those variables to
struct usb_device.
Signed-off-by: Mathias Nyman
---
drivers/usb/core/sysfs.c | 54
USB 3.0 link PM code does.
The same xhci_change_max_exit_latency() function is used as with USB3
but code is pulled out from #ifdef CONFIG_PM as USB2.0 BESL LPM
funcionality does not depend on CONFIG_PM.
Signed-off-by: Mathias Nyman
---
drivers/usb/host/xhci-ext-caps.h |1 +
drivers/usb/host
.
Changes since v1:
-Use kstrto* and unsigned values in sysfs functions as Alan Stern suggested
Mathias Nyman (4):
usb: xhci: check usb2 port capabilities before adding hw link PM
support
usb: xhci: define port register names and use them instead of magic
numbers
usb: xhci: add
NULL);
return 0;
}
Acked-by: Mathias Nyman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 04/10/2013 10:53 AM, Mika Westerberg wrote:
On Tue, Apr 09, 2013 at 03:57:25PM +0200, Rafael J. Wysocki wrote:
+void acpi_gpiochip_free_interrupts(struct gpio_chip *chip)
+{
+ acpi_handle handle;
+ acpi_status status;
+ struct list_head *evt_pins;
+ struct acpi_gpio_ev
Lynxpoint gpio driver uses X86 specific io-ports to control gpios
Signed-off-by: Mathias Nyman
---
drivers/gpio/Kconfig |2 +-
drivers/gpio/gpio-lynxpoint.c |1 +
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
index
pins have acpi event methods and assigns interrupt handlers that calls
the acpi event methods for those pins.
Partially based on work by Rui Zhang
Signed-off-by: Mathias Nyman
---
drivers/gpio/gpiolib-acpi.c | 82 +++
include/linux/acpi_gpio.h |4
On 01/25/2013 02:54 PM, Linus Walleij wrote:
On Fri, Jan 25, 2013 at 12:48 PM, Mathias Nyman
wrote:
Add ability to handle ACPI events signalled by GPIO interrupts.
ACPI5 platforms can use GPIO signaled ACPI events. These GPIO interrupts are
handled by ACPI event methods which need to be
pins have acpi event methods and assigns interrupt handlers that calls
the acpi event methods for those pins.
Partially based on work by Rui Zhang
Signed-off-by: Mathias Nyman
---
drivers/gpio/gpiolib-acpi.c | 80 +++
include/linux/acpi_gpio.h |4
Add gpio support for Intel Lynxpoint chipset.
Lynxpoint supports 94 gpio pins which can generate interrupts.
Driver will fail requests for pins that are marked as owned by ACPI, or
set in an alternate mode (non-gpio).
Signed-off-by: Mathias Nyman
---
drivers/gpio/Kconfig |8
gpio_reg() to lp_gpio_reg()
- renamed gpio variable to offset or hwirq where needed.
- added comments about register layout
- removed __devexit/__devinit macros
- removed #ifdefs and added ACPI dependancy instead
- added simple runtime pm support
- added lp_gpio_free()
Mathias Nyman (1):
gpio: add
On 12/11/2012 01:07 AM, Grant Likely wrote:
On Fri, 7 Dec 2012 16:01:39 +0200, Mathias
Nyman wrote:
Add gpio support for Intel Lynxpoint chipset.
Lynxpoint supports 94 gpio pins which can generate interrupts.
Driver will fail requests for pins that are marked as owned by ACPI, or
set in an
On 12/10/2012 11:48 AM, Linus Walleij wrote:
On Fri, Dec 7, 2012 at 3:01 PM, Mathias Nyman
wrote:
Add gpio support for Intel Lynxpoint chipset.
Lynxpoint supports 94 gpio pins which can generate interrupts.
Driver will fail requests for pins that are marked as owned by ACPI, or
set in an
Add gpio support for Intel Lynxpoint chipset.
Lynxpoint supports 94 gpio pins which can generate interrupts.
Driver will fail requests for pins that are marked as owned by ACPI, or
set in an alternate mode (non-gpio).
Signed-off-by: Mathias Nyman
---
drivers/gpio/Kconfig |7
This gpio controller driver for the Intel Lynxpoint LP PCH chipset is
designed to work with the new ACPI 5 enumeration model and ACPI 5
GpioIo/GpioInt
resource translation recently added to linux-acpi.
Mathias Nyman (1):
gpio: add Lynxpoint chipset gpio driver.
drivers/gpio/Kconfig
On 11/09/2012 04:18 PM, Grant Likely wrote:
On Fri, Nov 9, 2012 at 2:11 PM, Mathias Nyman
wrote:
On 11/08/2012 09:38 PM, Mika Westerberg wrote:
...
+#include
+#include
+#include
+#include
+#include
+
+static int acpi_gpiochip_find(struct gpio_chip *gc, void *data)
+{
+ acpi_handle
On 11/08/2012 09:38 PM, Mika Westerberg wrote:
...
+#include
+#include
+#include
+#include
+#include
+
+static int acpi_gpiochip_find(struct gpio_chip *gc, void *data)
+{
+ acpi_handle handle = data;
+ acpi_handle gc_handle;
+
+ if (!gc->dev)
+ return false;
+
+
On 11/05/2012 01:53 PM, Linus Walleij wrote:
On Sat, Nov 3, 2012 at 8:46 AM, Mika Westerberg
wrote:
+/**
+ * acpi_get_gpio() - Translate ACPI GPIO pin to GPIO number usable with GPIO
API
+ * @path: ACPI GPIO controller full path name, (e.g. "\\_SB.GPO1")
+ * @pin: ACPI GPIO pin nu
gpios requested with invalid numbers, or gpios requested from userspace via
sysfs
should not try to be deferred on failure.
Signed-off-by: Mathias Nyman
---
drivers/gpio/gpiolib.c | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers
.
Signed-off-by: Mathias Nyman
---
drivers/gpio/gpiolib.c | 38 +-
include/asm-generic/gpio.h |5 -
2 files changed, 41 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index de0213c..141f793 100644
--- a
On 10/23/2012 01:23 AM, Linus Walleij wrote:
On Mon, Oct 22, 2012 at 3:44 PM, Mathias Nyman
wrote:
If the .get_direction callback is set, then gpiolib will use it
for showing correct gpio direction in sysfs and debug. If not set
then it will work the old way; e.g. guessing everything is
401 - 500 of 502 matches
Mail list logo
