Commit 2c06aeb2 authored by Chris Ball's avatar Chris Ball
Browse files

Merge tag 'tegra-for-3.10-fixes-for-mmc' of... 

Merge tag 'tegra-for-3.10-fixes-for-mmc' of git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra into mmc-next

ARM: tegra: DT-related fixes needed by the MMC tree

In order to convert the Tegra MMC driver to using mmc_of_parse(), some
bugs in the Tegra device-tree content need to be fixed first; it's
currently wrong but unused, and mmc_of_parse() causes that data to be
used for the first time.
parents 9665f7f2 908ab936

Documentation/00-INDEX

+2 −0
Original line number Diff line number Diff line
@@ -299,6 +299,8 @@ memory-hotplug.txt 
	- Hotpluggable memory support, how to use and current status.

memory.txt

	- info on typical Linux memory problems.

metag/

	- directory with info about Linux on Meta architecture.

mips/

	- directory with info about Linux on MIPS architecture.

misc-devices/

Documentation/ABI/testing/sysfs-bus-fcoe

+42 −3
Original line number Diff line number Diff line 
What:		/sys/bus/fcoe/ctlr_X

What:		/sys/bus/fcoe/

Date:		August 2012

KernelVersion:	TBD

Contact:	Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org

Description:	The FCoE bus. Attributes in this directory are control interfaces.

Attributes:



	ctlr_create: 'FCoE Controller' instance creation interface. Writing an

		     <ifname> to this file will allocate and populate sysfs with a

		     fcoe_ctlr_device (ctlr_X). The user can then configure any

		     per-port settings and finally write to the fcoe_ctlr_device's

		     'start' attribute to begin the kernel's discovery and login

		     process.



	ctlr_destroy: 'FCoE Controller' instance removal interface. Writing a

		       fcoe_ctlr_device's sysfs name to this file will log the

		       fcoe_ctlr_device out of the fabric or otherwise connected

		       FCoE devices. It will also free all kernel memory allocated

		       for this fcoe_ctlr_device and any structures associated

		       with it, this includes the scsi_host.



What:		/sys/bus/fcoe/devices/ctlr_X

Date:		March 2012

KernelVersion:	TBD

Contact:	Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org

Description:	'FCoE Controller' instances on the fcoe bus

Description:	'FCoE Controller' instances on the fcoe bus.

		The FCoE Controller now has a three stage creation process.

		1) Write interface name to ctlr_create 2) Configure the FCoE

		Controller (ctlr_X) 3) Enable the FCoE Controller to begin

		discovery and login. The FCoE Controller is destroyed by

		writing it's name, i.e. ctlr_X to the ctlr_delete file.



Attributes:



	fcf_dev_loss_tmo: Device loss timeout peroid (see below). Changing

			  this value will change the dev_loss_tmo for all

			  FCFs discovered by this controller.



	mode:		  Display or change the FCoE Controller's mode. Possible

			  modes are 'Fabric' and 'VN2VN'. If a FCoE Controller

			  is started in 'Fabric' mode then FIP FCF discovery is

			  initiated and ultimately a fabric login is attempted.

			  If a FCoE Controller is started in 'VN2VN' mode then

			  FIP VN2VN discovery and login is performed. A FCoE

			  Controller only supports one mode at a time.



	enabled:	  Whether an FCoE controller is enabled or disabled.

			  0 if disabled, 1 if enabled. Writing either 0 or 1

			  to this file will enable or disable the FCoE controller.



	lesb/link_fail:   Link Error Status Block (LESB) link failure count.



	lesb/vlink_fail:  Link Error Status Block (LESB) virtual link
@@ -26,7 +65,7 @@ Attributes: 


Notes: ctlr_X (global increment starting at 0)



What:		/sys/bus/fcoe/fcf_X

What:		/sys/bus/fcoe/devices/fcf_X

Date:		March 2012

KernelVersion:	TBD

Contact:	Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org

Documentation/ABI/testing/sysfs-platform-msi-laptop

0 → 100644
+83 −0
Original line number Diff line number Diff line 
What:		/sys/devices/platform/msi-laptop-pf/lcd_level

Date:		Oct 2006

KernelVersion:	2.6.19

Contact:	"Lennart Poettering <mzxreary@0pointer.de>"

Description:

		Screen brightness: contains a single integer in the range 0..8.



What:		/sys/devices/platform/msi-laptop-pf/auto_brightness

Date:		Oct 2006

KernelVersion:	2.6.19

Contact:	"Lennart Poettering <mzxreary@0pointer.de>"

Description:

		Enable automatic brightness control: contains either 0 or 1. If

		set to 1 the hardware adjusts the screen brightness

		automatically when the power cord is plugged/unplugged.



What:		/sys/devices/platform/msi-laptop-pf/wlan

Date:		Oct 2006

KernelVersion:	2.6.19

Contact:	"Lennart Poettering <mzxreary@0pointer.de>"

Description:

		WLAN subsystem enabled: contains either 0 or 1.



What:		/sys/devices/platform/msi-laptop-pf/bluetooth

Date:		Oct 2006

KernelVersion:	2.6.19

Contact:	"Lennart Poettering <mzxreary@0pointer.de>"

Description:

		Bluetooth subsystem enabled: contains either 0 or 1. Please

		note that this file is constantly 0 if no Bluetooth hardware is

		available.



What:		/sys/devices/platform/msi-laptop-pf/touchpad

Date:		Nov 2012

KernelVersion:	3.8

Contact:	"Maxim Mikityanskiy <maxtram95@gmail.com>"

Description:

		Contains either 0 or 1 and indicates if touchpad is turned on.

		Touchpad state can only be toggled by pressing Fn+F3.



What:		/sys/devices/platform/msi-laptop-pf/turbo_mode

Date:		Nov 2012

KernelVersion:	3.8

Contact:	"Maxim Mikityanskiy <maxtram95@gmail.com>"

Description:

		Contains either 0 or 1 and indicates if turbo mode is turned

		on. In turbo mode power LED is orange and processor is

		overclocked. Turbo mode is available only if charging. It is

		only possible to toggle turbo mode state by pressing Fn+F10,

		and there is a few seconds cooldown between subsequent toggles.

		If user presses Fn+F10 too frequent, turbo mode state is not

		changed.



What:		/sys/devices/platform/msi-laptop-pf/eco_mode

Date:		Nov 2012

KernelVersion:	3.8

Contact:	"Maxim Mikityanskiy <maxtram95@gmail.com>"

Description:

		Contains either 0 or 1 and indicates if ECO mode is turned on.

		In ECO mode power LED is green and userspace should do some

		powersaving actions. ECO mode is available only on battery

		power. ECO mode can only be toggled by pressing Fn+F10.



What:		/sys/devices/platform/msi-laptop-pf/turbo_cooldown

Date:		Nov 2012

KernelVersion:	3.8

Contact:	"Maxim Mikityanskiy <maxtram95@gmail.com>"

Description:

		Contains value in range 0..3:

			* 0 -> Turbo mode is off

			* 1 -> Turbo mode is on, cannot be turned off yet

			* 2 -> Turbo mode is off, cannot be turned on yet

			* 3 -> Turbo mode is on



What:		/sys/devices/platform/msi-laptop-pf/auto_fan

Date:		Nov 2012

KernelVersion:	3.8

Contact:	"Maxim Mikityanskiy <maxtram95@gmail.com>"

Description:

		Contains either 0 or 1 and indicates if fan speed is controlled

		automatically (1) or fan runs at maximal speed (0). Can be

		toggled in software.

Documentation/DMA-API-HOWTO.txt

+5 −4
Original line number Diff line number Diff line
@@ -488,9 +488,10 @@ will invoke the generic mapping error check interface. Doing so will ensure 
that the mapping code will work correctly on all dma implementations without

any dependency on the specifics of the underlying implementation. Using the

returned address without checking for errors could result in failures ranging

from panics to silent data corruption. Couple of example of incorrect ways to

check for errors that make assumptions about the underlying dma implementation

are as follows and these are applicable to dma_map_page() as well.

from panics to silent data corruption. A couple of examples of incorrect ways

to check for errors that make assumptions about the underlying dma

implementation are as follows and these are applicable to dma_map_page() as

well.



Incorrect example 1:

	dma_addr_t dma_handle;
@@ -751,7 +752,7 @@ Example 1: 
		dma_unmap_single(dma_handle1);

	map_error_handling1:



Example 2: (if buffers are allocated a loop, unmap all mapped buffers when

Example 2: (if buffers are allocated in a loop, unmap all mapped buffers when

	    mapping error is detected in the middle)



	dma_addr_t dma_addr;

Documentation/IPMI.txt

+12 −6
Original line number Diff line number Diff line
@@ -348,34 +348,40 @@ You can change this at module load time (for a module) with: 


  modprobe ipmi_si.o type=<type1>,<type2>....

       ports=<port1>,<port2>... addrs=<addr1>,<addr2>...

       irqs=<irq1>,<irq2>... trydefaults=[0|1]

       irqs=<irq1>,<irq2>...

       regspacings=<sp1>,<sp2>,... regsizes=<size1>,<size2>,...

       regshifts=<shift1>,<shift2>,...

       slave_addrs=<addr1>,<addr2>,...

       force_kipmid=<enable1>,<enable2>,...

       kipmid_max_busy_us=<ustime1>,<ustime2>,...

       unload_when_empty=[0|1]

       trydefaults=[0|1] trydmi=[0|1] tryacpi=[0|1]

       tryplatform=[0|1] trypci=[0|1]



Each of these except si_trydefaults is a list, the first item for the

Each of these except try... items is a list, the first item for the

first interface, second item for the second interface, etc.



The si_type may be either "kcs", "smic", or "bt".  If you leave it blank, it

defaults to "kcs".



If you specify si_addrs as non-zero for an interface, the driver will

If you specify addrs as non-zero for an interface, the driver will

use the memory address given as the address of the device.  This

overrides si_ports.



If you specify si_ports as non-zero for an interface, the driver will

If you specify ports as non-zero for an interface, the driver will

use the I/O port given as the device address.



If you specify si_irqs as non-zero for an interface, the driver will

If you specify irqs as non-zero for an interface, the driver will

attempt to use the given interrupt for the device.



si_trydefaults sets whether the standard IPMI interface at 0xca2 and

trydefaults sets whether the standard IPMI interface at 0xca2 and

any interfaces specified by ACPE are tried.  By default, the driver

tries it, set this value to zero to turn this off.



The other try... items disable discovery by their corresponding

names.  These are all enabled by default, set them to zero to disable

them.  The tryplatform disables openfirmware.



The next three parameters have to do with register layout.  The

registers used by the interfaces may not appear at successive

locations and they may not be in 8-bit registers.  These parameters

CRA Git | Maintained and supported by SUSTech CRA and CCSE