Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 0b7877d4 authored by Jens Axboe's avatar Jens Axboe
Browse files

Merge tag 'v3.4-rc5' into for-3.5/core



The core branch is behind driver commits that we want to build
on for 3.5, hence I'm pulling in a later -rc.

Linux 3.4-rc5

Conflicts:
	Documentation/feature-removal-schedule.txt

Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
parents bd1a68b5 69964ea4
Loading
Loading
Loading
Loading
+7 −7
Original line number Diff line number Diff line
What:		/sys/bus/usb/drivers/usbtmc/devices/*/interface_capabilities
What:		/sys/bus/usb/drivers/usbtmc/devices/*/device_capabilities
What:		/sys/bus/usb/drivers/usbtmc/*/interface_capabilities
What:		/sys/bus/usb/drivers/usbtmc/*/device_capabilities
Date:		August 2008
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
@@ -12,8 +12,8 @@ Description:
		The files are read only.


What:		/sys/bus/usb/drivers/usbtmc/devices/*/usb488_interface_capabilities
What:		/sys/bus/usb/drivers/usbtmc/devices/*/usb488_device_capabilities
What:		/sys/bus/usb/drivers/usbtmc/*/usb488_interface_capabilities
What:		/sys/bus/usb/drivers/usbtmc/*/usb488_device_capabilities
Date:		August 2008
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
@@ -27,7 +27,7 @@ Description:
		The files are read only.


What:		/sys/bus/usb/drivers/usbtmc/devices/*/TermChar
What:		/sys/bus/usb/drivers/usbtmc/*/TermChar
Date:		August 2008
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
@@ -40,7 +40,7 @@ Description:
		sent to the device or not.


What:		/sys/bus/usb/drivers/usbtmc/devices/*/TermCharEnabled
What:		/sys/bus/usb/drivers/usbtmc/*/TermCharEnabled
Date:		August 2008
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
@@ -51,7 +51,7 @@ Description:
		published by the USB-IF.


What:		/sys/bus/usb/drivers/usbtmc/devices/*/auto_abort
What:		/sys/bus/usb/drivers/usbtmc/*/auto_abort
Date:		August 2008
Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Description:
+18 −0
Original line number Diff line number Diff line
What:           /sys/block/rssd*/registers
Date:           March 2012
KernelVersion:  3.3
Contact:        Asai Thambi S P <asamymuthupa@micron.com>
Description:    This is a read-only file. Dumps below driver information and
                hardware registers.
                    - S ACTive
                    - Command Issue
                    - Allocated
                    - Completed
                    - PORT IRQ STAT
                    - HOST IRQ STAT

What:           /sys/block/rssd*/status
Date:           April 2012
KernelVersion:  3.4
Contact:        Asai Thambi S P <asamymuthupa@micron.com>
Description:   This is a read-only file. Indicates the status of the device.
+19 −0
Original line number Diff line number Diff line
What:		/sys/bus/hsi
Date:		April 2012
KernelVersion:	3.4
Contact:	Carlos Chinea <carlos.chinea@nokia.com>
Description:
		High Speed Synchronous Serial Interface (HSI) is a
		serial interface mainly used for connecting application
		engines (APE) with cellular modem engines (CMT) in cellular
		handsets.
		The bus will be populated with devices (hsi_clients) representing
		the protocols available in the system. Bus drivers implement
		those protocols.

What:		/sys/bus/hsi/devices/.../modalias
Date:		April 2012
KernelVersion:	3.4
Contact:	Carlos Chinea <carlos.chinea@nokia.com>
Description:	Stores the same MODALIAS value emitted by uevent
		Format: hsi:<hsi_client device name>
+8 −0
Original line number Diff line number Diff line
What:		/sys/block/<device>/iosched/target_latency
Date:		March 2012
contact:	Tao Ma <boyu.mt@taobao.com>
Description:
		The /sys/block/<device>/iosched/target_latency only exists
		when the user sets cfq to /sys/block/<device>/scheduler.
		It contains an estimated latency time for the cfq. cfq will
		use it to calculate the time slice used for every task.
+18 −0
Original line number Diff line number Diff line
@@ -31,3 +31,21 @@ may be weakly ordered, that is that reads and writes may pass each other.
Since it is optional for platforms to implement DMA_ATTR_WEAK_ORDERING,
those that do not will simply ignore the attribute and exhibit default
behavior.

DMA_ATTR_WRITE_COMBINE
----------------------

DMA_ATTR_WRITE_COMBINE specifies that writes to the mapping may be
buffered to improve performance.

Since it is optional for platforms to implement DMA_ATTR_WRITE_COMBINE,
those that do not will simply ignore the attribute and exhibit default
behavior.

DMA_ATTR_NON_CONSISTENT
-----------------------

DMA_ATTR_NON_CONSISTENT lets the platform to choose to return either
consistent or non-consistent memory as it sees fit.  By using this API,
you are guaranteeing to the platform that you have all the correct and
necessary sync points for this memory in the driver.
Loading