-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
Pulling to get some TIPC fixes that a net-next series depends upon. Signed-off-by: David S. Miller <davem@davemloft.net>
- Loading branch information
Showing
230 changed files
with
4,691 additions
and
1,852 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
TI PCI Controllers | ||
|
||
PCIe Designware Controller | ||
- compatible: Should be "ti,dra7-pcie"" | ||
- reg : Two register ranges as listed in the reg-names property | ||
- reg-names : The first entry must be "ti-conf" for the TI specific registers | ||
The second entry must be "rc-dbics" for the designware pcie | ||
registers | ||
The third entry must be "config" for the PCIe configuration space | ||
- phys : list of PHY specifiers (used by generic PHY framework) | ||
- phy-names : must be "pcie-phy0", "pcie-phy1", "pcie-phyN".. based on the | ||
number of PHYs as specified in *phys* property. | ||
- ti,hwmods : Name of the hwmod associated to the pcie, "pcie<X>", | ||
where <X> is the instance number of the pcie from the HW spec. | ||
- interrupts : Two interrupt entries must be specified. The first one is for | ||
main interrupt line and the second for MSI interrupt line. | ||
- #address-cells, | ||
#size-cells, | ||
#interrupt-cells, | ||
device_type, | ||
ranges, | ||
num-lanes, | ||
interrupt-map-mask, | ||
interrupt-map : as specified in ../designware-pcie.txt | ||
|
||
Example: | ||
axi { | ||
compatible = "simple-bus"; | ||
#size-cells = <1>; | ||
#address-cells = <1>; | ||
ranges = <0x51000000 0x51000000 0x3000 | ||
0x0 0x20000000 0x10000000>; | ||
pcie@51000000 { | ||
compatible = "ti,dra7-pcie"; | ||
reg = <0x51000000 0x2000>, <0x51002000 0x14c>, <0x1000 0x2000>; | ||
reg-names = "rc_dbics", "ti_conf", "config"; | ||
interrupts = <0 232 0x4>, <0 233 0x4>; | ||
#address-cells = <3>; | ||
#size-cells = <2>; | ||
device_type = "pci"; | ||
ranges = <0x81000000 0 0 0x03000 0 0x00010000 | ||
0x82000000 0 0x20013000 0x13000 0 0xffed000>; | ||
#interrupt-cells = <1>; | ||
num-lanes = <1>; | ||
ti,hwmods = "pcie1"; | ||
phys = <&pcie1_phy>; | ||
phy-names = "pcie-phy0"; | ||
interrupt-map-mask = <0 0 0 7>; | ||
interrupt-map = <0 0 0 1 &pcie_intc 1>, | ||
<0 0 0 2 &pcie_intc 2>, | ||
<0 0 0 3 &pcie_intc 3>, | ||
<0 0 0 4 &pcie_intc 4>; | ||
pcie_intc: interrupt-controller { | ||
interrupt-controller; | ||
#address-cells = <0>; | ||
#interrupt-cells = <1>; | ||
}; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,76 @@ | ||
Kernel driver toshiba_haps | ||
Toshiba HDD Active Protection Sensor | ||
==================================== | ||
|
||
Author: Azael Avalos <coproscefalo@gmail.com> | ||
|
||
|
||
0. Contents | ||
----------- | ||
|
||
1. Description | ||
2. Interface | ||
3. Accelerometer axes | ||
4. Supported devices | ||
5. Usage | ||
|
||
|
||
1. Description | ||
-------------- | ||
|
||
This driver provides support for the accelerometer found in various Toshiba | ||
laptops, being called "Toshiba HDD Protection - Shock Sensor" officialy, | ||
and detects laptops automatically with this device. | ||
On Windows, Toshiba provided software monitors this device and provides | ||
automatic HDD protection (head unload) on sudden moves or harsh vibrations, | ||
however, this driver only provides a notification via a sysfs file to let | ||
userspace tools or daemons act accordingly, as well as providing a sysfs | ||
file to set the desired protection level or sensor sensibility. | ||
|
||
|
||
2. Interface | ||
------------ | ||
|
||
This device comes with 3 methods: | ||
_STA - Checks existence of the device, returning Zero if the device does not | ||
exists or is not supported. | ||
PTLV - Sets the desired protection level. | ||
RSSS - Shuts down the HDD protection interface for a few seconds, | ||
then restores normal operation. | ||
|
||
Note: | ||
The presence of Solid State Drives (SSD) can make this driver to fail loading, | ||
given the fact that such drives have no movable parts, and thus, not requiring | ||
any "protection" as well as failing during the evaluation of the _STA method | ||
found under this device. | ||
|
||
|
||
3. Accelerometer axes | ||
--------------------- | ||
|
||
This device does not report any axes, however, to query the sensor position | ||
a couple HCI (Hardware Configuration Interface) calls (0x6D and 0xA6) are | ||
provided to query such information, handled by the kernel module toshiba_acpi | ||
since kernel version 3.15. | ||
|
||
|
||
4. Supported devices | ||
-------------------- | ||
|
||
This driver binds itself to the ACPI device TOS620A, and any Toshiba laptop | ||
with this device is supported, given the fact that they have the presence of | ||
conventional HDD and not only SSD, or a combination of both HDD and SSD. | ||
|
||
|
||
5. Usage | ||
-------- | ||
|
||
The sysfs files under /sys/devices/LNXSYSTM:00/LNXSYBUS:00/TOS620A:00/ are: | ||
protection_level - The protection_level is readable and writeable, and | ||
provides a way to let userspace query the current protection | ||
level, as well as set the desired protection level, the | ||
available protection levels are: | ||
0 - Disabled | 1 - Low | 2 - Medium | 3 - High | ||
reset_protection - The reset_protection entry is writeable only, being "1" | ||
the only parameter it accepts, it is used to trigger | ||
a reset of the protection interface. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.