https://github.com/rntmancuso/linux-xlnx-prof
- HEAD
- refs/heads/2017.1_video_ea
- refs/heads/2017.2_video_ea
- refs/heads/2017.3_video_ea
- refs/heads/2017.4_video_ea
- refs/heads/master
- refs/heads/petalinux-v12.12
- refs/heads/petalinux-v2013.04
- refs/heads/xilinx/versal
- refs/heads/xlnx_3.14
- refs/heads/xlnx_3.17
- refs/heads/xlnx_3.8
- refs/heads/xlnx_rebase_v4.14
- refs/heads/xlnx_rebase_v4.19
- refs/heads/xlnx_rebase_v4.9
- refs/heads/xlnx_rebase_v5.4
- refs/heads/zynq/cleanup
- refs/heads/zynq/clk
- refs/heads/zynq/defconfig
- refs/heads/zynq/dt
- refs/heads/zynq/fixes
- refs/heads/zynq/soc
- refs/heads/zynqmp/dt
- refs/heads/zynqmp/soc
- refs/heads/zynqmp/soc-next
- refs/tags/2.6.13.4-drv-20070112-sp3e-ear.patch
- refs/tags/2.6.13.4-initramfs.patch
- refs/tags/2.6.13.4-mb-20070112-sp3e-ear.patch
- refs/tags/2.6.20-xlnx-initial-release
- refs/tags/bad_commit_john
- refs/tags/bad_head
- refs/tags/before_3.0
- refs/tags/edk_10.1.1
- refs/tags/initial-version
- refs/tags/last-arch-ppc
- refs/tags/linux-xlnx_3.8-r1
- refs/tags/pele-alpha2-release
- refs/tags/pele-alpha2-validation1
- refs/tags/pele-alpha2_2.0-release
- refs/tags/pele-alpha2_3.0-release
- refs/tags/pele-beta1_1.0
- refs/tags/pele-beta1_1.0-peep9
- refs/tags/pele-beta1_1.1
- refs/tags/pele-beta1_1.15
- refs/tags/pele-beta1_1.20
- refs/tags/pele-beta2_2.0
- refs/tags/pele_before_device_tree
- refs/tags/v2.6.26-merge
- refs/tags/xilinx-14.1-build1
- refs/tags/xilinx-14.1-build2
- refs/tags/xilinx-14.1-build3
- refs/tags/xilinx-14.1-build3-trd
- refs/tags/xilinx-14.2-build1
- refs/tags/xilinx-14.2-build1-trd
- refs/tags/xilinx-14.3-build1
- refs/tags/xilinx-14.3-build2
- refs/tags/xilinx-14.3-build2-trd
- refs/tags/xilinx_before_2.6.39
- refs/tags/xilinx_temp
- refs/tags/xilinx_v2.6.26
- refs/tags/xilinx_v2.6.27-rc9
- refs/tags/xilinx_v2.6.28
- refs/tags/xilinx_v2.6.29
- refs/tags/xilinx_v2.6.29-rc5
- refs/tags/xilinx_v2.6.30
- refs/tags/xilinx_v2.6.31
- refs/tags/xilinx_v2.6.32
- refs/tags/xilinx_v2.6.33
- refs/tags/xilinx_v2.6.33-rc8
- refs/tags/xilinx_v2.6.34
- refs/tags/xilinx_v2.6.35
- refs/tags/xilinx_v2.6.37
- refs/tags/xilinx_v2.6.37-rc4
- refs/tags/xilinx_v2.6.38
- refs/tags/xilinx_v3.0
- refs/tags/xmb_beta_v1
- refs/tags/xmb_beta_v2
- refs/tags/xmb_beta_v3
- zynqmp-soc-for-v5.9-v2
- zynqmp-soc-for-v5.9
- zynqmp-soc-for-v5.7-rc3
- zynqmp-soc-for-v5.7
- zynqmp-soc-for-v5.6
- zynqmp-soc-for-v5.5
- zynqmp-soc-for-v5.2
- zynqmp-soc-for-v5.12
- zynqmp-soc-for-v5.11-v2
- zynqmp-soc-for-v5.11
- zynqmp-soc-for-v5.1
- zynqmp-soc-fixes-for-v5.10-rc6
- zynqmp-dt-for-v5.9
- zynqmp-dt-for-v5.8
- zynqmp-dt-for-v5.6
- zynqmp-dt-for-v5.5
- zynqmp-dt-for-v5.2
- zynqmp-dt-for-v5.12
- zynqmp-dt-for-v5.11
- zynqmp-dt-for-v5.10
- zynqmp-dt-for-v5.1
- zynq-soc-for-v5.7
- zynq-soc-for-v5.6
- zynq-soc-for-v5.4
- zynq-dt-for-v5.6-v2
- zynq-dt-for-v5.6
- zynq-dt-for-v5.10
- zynq-dt-for-v5.1
- zynmp-dt-fixes-for-4.10
- xlnx_rebase_v5.4_2020.2
- xlnx_rebase_v5.4_2020.1
- xlnx_rebase_v4.9_2017.4
- xlnx_rebase_v4.9_2017.3
- xlnx_rebase_v4.19_2019.2
- xlnx_rebase_v4.19_2019.1
- xlnx_rebase_v4.14_2018.3
- xlnx_rebase_v4.14_2018.2
- xlnx_rebase_v4.14_2018.1
- xilinx-v2020.2
- xilinx-v2020.1
- xilinx-v2019.2.01
- xilinx-v2019.1
- xilinx-v2018.3
- xilinx-v2018.2
- xilinx-v2018.1
- xilinx-v2017.4
- xilinx-v2017.3
- xilinx-v2017.2
- xilinx-v2017.1
- xilinx-v2016.4-sdsoc
- xilinx-v2016.4
- xilinx-v2016.3-trd
- xilinx-v2016.3-sdsoc
- xilinx-v2016.3
- xilinx-v2016.2-trd
- xilinx-v2016.2-sdsoc
- xilinx-v2016.2
- xilinx-v2016.1.01
- xilinx-v2016.1-trd
- xilinx-v2016.1
- xilinx-v2015.4.01
- xilinx-v2015.4
- xilinx-v2015.3
- xilinx-v2015.2.03
- xilinx-v2015.2.02
- xilinx-v2015.2.01
- xilinx-v2015.2
- xilinx-v2015.1
- xilinx-v2014.4-trd
- xilinx-v2014.4
- xilinx-v2014.3
- xilinx-v2014.2.01
- xilinx-v2014.2-trd
- xilinx-v2014.2
- xilinx-v2014.1
- xilinx-v2013.4-trd
- xilinx-v2013.4
- xilinx-v14.7
- xilinx-v14.6.02
- xilinx-v14.6.01
- xilinx-v14.6
- xilinx-v14.5.01
- xilinx-v14.5
- xilinx-v14.4
- xilinx-dt-for-4.17
- xilinx-14.5-build-trd
- v2.6.11-tree
- phase0a
- petalinux-v2014.2-final
- petalinux-v2013.10-final
- petalinux-v2013.04-final
- petalinux-v12.12-final
Take a new snapshot of a software origin
If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.
Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.
Processing "take a new snapshot" request ...
Permalinks
To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.
| Revision | Author | Date | Message | Commit Date |
|---|---|---|---|---|
| 2b48a8a | Thomas Gleixner | 25 April 2014, 15:32:12 UTC | time: Fixup fallout from recent clockevent/tick changes Make the stub function static inline instead of static and move the clockevents related function into the proper ifdeffed section. Reported-by: Fengguang Wu <fengguang.wu@intel.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: Soren Brinkmann <soren.brinkmann@xilinx.com> Cc: Preeti U Murthy <preeti@linux.vnet.ibm.com> (cherry picked from commit f1689bb7abec8e2e670d8ad11eaa86d54bad8cfd) Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 13 May 2014, 13:16:49 UTC |
| ecb9543 | Punnaiah Choudary Kalluri | 13 May 2014, 04:42:35 UTC | usb: gadget: zynq: Fix usb ethernet gadget probe error This patch is based on the below commit "usb: gadget: add "maxpacket_limit" field to struct usb_ep" (sha1:e117e742d310683b410951faeab4b13b6c3c609f) Value of "maxpacket_limit" should be set in UDC driver probe function, using usb_ep_set_maxpacket_limit() function, defined in gadget.h. This function set choosen value to both "maxpacket_limit" and "maxpacket" fields. Signed-off-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com> Tested-by: Nathan Rossi <nathan.rossi@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 13 May 2014, 12:41:40 UTC |
| bc39f69 | Michal Simek | 01 May 2014, 11:03:36 UTC | jffs: Fix locking issue in readdir jffs2_readdir is holding f->sem lock when page fault handler is executed and jffs2_readpage wants to unlock one page. Release f->sem lock before data is copyied back to the user space via filldir(). [ 4.619653] ====================================================== [ 4.625815] [ INFO: possible circular locking dependency detected ] [ 4.632068] 3.14.2-xilinx-03769-g5faf151-dirty #43 Not tainted [ 4.637879] ------------------------------------------------------- [ 4.644130] rc/607 is trying to acquire lock: [ 4.648469] (&mm->mmap_sem){++++++}, at: [<c00b686c>] might_fault+0x4c/0xa4 [ 4.655500] [ 4.655500] but task is already holding lock: [ 4.661314] (&f->sem){+.+.+.}, at: [<c01be540>] jffs2_readdir+0x24/0x1ac [ 4.668086] [ 4.668086] which lock already depends on the new lock. [ 4.668086] [ 4.676245] [ 4.676245] the existing dependency chain (in reverse order) is: [ 4.683709] -> #1 (&f->sem){+.+.+.}: [ 4.687442] [<c00602b0>] lock_acquire+0x90/0xa4 [ 4.692563] [<c0475c50>] mutex_lock_nested+0x64/0x42c [ 4.698204] [<c01bfd64>] jffs2_readpage+0x20/0x44 [ 4.703499] [<c00a57b8>] __do_page_cache_readahead+0x2c8/0x330 [ 4.709923] [<c00a5a2c>] ra_submit+0x20/0x28 [ 4.714783] [<c009cd40>] filemap_fault+0x1d8/0x4a8 [ 4.720165] [<c00b63b8>] __do_fault+0xa0/0x448 [ 4.725199] [<c00b9770>] handle_mm_fault+0x20c/0x7f0 [ 4.730754] [<c0019d6c>] do_page_fault+0x124/0x384 [ 4.736136] [<c00083f8>] do_DataAbort+0x34/0x98 [ 4.741257] [<c001231c>] __dabt_svc+0x3c/0x60 [ 4.746205] [<c01f657c>] __clear_user_std+0x34/0x64 [ 4.751674] -> #0 (&mm->mmap_sem){++++++}: [ 4.755926] [<c005f648>] __lock_acquire+0x1398/0x1ae4 [ 4.761568] [<c00602b0>] lock_acquire+0x90/0xa4 [ 4.766690] [<c00b6890>] might_fault+0x70/0xa4 [ 4.771724] [<c00e16f4>] filldir+0x64/0x16c [ 4.776498] [<c01be580>] jffs2_readdir+0x64/0x1ac [ 4.781793] [<c00e1658>] iterate_dir+0x64/0x9c [ 4.786827] [<c00e19e8>] SyS_getdents+0x78/0xec [ 4.791948] [<c000e5a0>] ret_fast_syscall+0x0/0x48 [ 4.797331] [ 4.797331] other info that might help us debug this: [ 4.797331] [ 4.805316] Possible unsafe locking scenario: [ 4.805316] [ 4.811219] CPU0 CPU1 [ 4.815732] ---- ---- [ 4.820245] lock(&f->sem); [ 4.823110] lock(&mm->mmap_sem); [ 4.829012] lock(&f->sem); [ 4.834393] lock(&mm->mmap_sem); [ 4.837779] [ 4.837779] *** DEADLOCK *** Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 09 May 2014, 13:28:31 UTC |
| a469fd9 | Hyun Kwon | 06 May 2014, 02:52:47 UTC | drm: xylon: irq: replace DRM_WAKEUP() with wake_up() DRM_WAKEUP() has been removed, so replace DRM_WAKEUP() call with wake_up(). Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:30 UTC |
| 2c5ace6 | Hyun Kwon | 06 May 2014, 02:52:46 UTC | Documentation: devicetree: drm: xilinx: DisplayPort(dp) Add the devicetree bindings documentation for Xilinx DisplayPort driver. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:29 UTC |
| 21eb213 | Hyun Kwon | 06 May 2014, 02:52:45 UTC | drm: xilinx: dp: Add the DisplayPort driver This patch adds a driver for the DisplayPort soft IP core. The DisplayPort IP core supports transmission of serial-digital video for display devices. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:28 UTC |
| e87a485 | Hyun Kwon | 06 May 2014, 02:52:44 UTC | Documentation: devicetree: bindings: drm: xilinx: Add the plane manager format Add the property to specify the format of plane manager. This allows to configure the format instead of using the fixed value. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:27 UTC |
| 0afdc62 | Hyun Kwon | 06 May 2014, 02:52:43 UTC | drm: xilinx: plane: Add the format property in the planes node Add the format property in the planes node. This allows to configure the pixel format properly as the format can differ depending on configuration. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:27 UTC |
| e52f114 | Hyun Kwon | 06 May 2014, 02:52:42 UTC | drm: xilinx: drv: Fix the format descriptor Fix the Xilinx RGB format to be 24 bit RGB format, and add one more descriptor for XRGB format with 24 bit depth and 32 bit pixel. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:26 UTC |
| 8ef8a0e | Hyun Kwon | 06 May 2014, 02:52:41 UTC | drm: xilinx: drv: Remove explicit call of destroy functions drm_mode_config_cleanup() clean up drm objects, so no need to call destroy functions in the error exit. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:25 UTC |
| 6e9ab31 | Hyun Kwon | 06 May 2014, 02:52:40 UTC | Documentation: devicetree: bindings: drm: xilinx: Add the connector type Add the connector type property in the node. User can specify the type of connector to use, and the value is used to initialize the drm connector in the connector driver. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:25 UTC |
| a80e921 | Hyun Kwon | 06 May 2014, 02:52:39 UTC | drm: xilinx: connector: Configure the type from DT property The connector can be either HDMI or DisplayPort depending on which encoder slave is used. Add the struct xilinx_drm_connector_type to have supported connector types, and decide the type based on DT. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:24 UTC |
| a28312b | Hyun Kwon | 06 May 2014, 02:52:38 UTC | Documentation: devicetree: bindings: drm: xilinx: Add 'xlnx' prefix Add 'xlnx' prefix to Xilinx IP core specific properties. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:23 UTC |
| d0a4151 | Hyun Kwon | 06 May 2014, 02:52:37 UTC | drm: xilinx: Add the 'xlnx' prefix to dt properties Add the 'xlnx' prefix to Xilinx IP core specific properties. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:22 UTC |
| 372a7e9 | Hyun Kwon | 06 May 2014, 02:52:36 UTC | drm: xilinx: encoder: Initialize the drm encoder before the encoder slave drm_encoder_init() and drm_encoder_helper_add() need to be called before initializing the encoder slave. The encoder slave can generate interrupts right after initalization, which may result in error from not initialized drm device. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:22 UTC |
| d9c474c | Hyun Kwon | 06 May 2014, 02:52:35 UTC | drm: xilinx: encoder: Support encoder slaves on a platform bus The Xilinx display pipeline can have encoder slaves on a platform bus, so encoder slaves on a platform bus support is added in addition to i2c encoder slaves. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:21 UTC |
| 371e079 | Hyun Kwon | 06 May 2014, 02:52:34 UTC | drm: xilinx: encoder: Change the name 'i2c_slave' to 'i2c_slv' This is needed to improve consistency of naming when 'platform_slv' will be added, as the name is long. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:20 UTC |
| ec423e3 | Hyun Kwon | 06 May 2014, 02:52:33 UTC | drm: platform encoder driver support Add struct drm_platform_encoder_driver. This structure can be used for the encoder slave drivers on a platform bus. The i2c specific assumption better be removed, and other drm encoder slave interfaces would be updated to be more generic. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:19 UTC |
| 0d0148d | Hyun Kwon | 06 May 2014, 02:52:32 UTC | drm: xylon: connector: Call the encoder slave's mode_valid() function Call the mode valid function of the necoder slave, and let the encoder slave driver check validity of given mode. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:19 UTC |
| 5df95a2 | Hyun Kwon | 06 May 2014, 02:52:31 UTC | drm: xilinx: connector: Call the encoder slave's mode_valid() function Call the mode valid function of the encoder slave, and let the encoder slave driver check validity of given mode. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:18 UTC |
| 9505088 | Hyun Kwon | 06 May 2014, 02:52:30 UTC | drm: adv7511: Add adv7511_encoder_mode_valid() function Add adv7511_encoder_mode_valid() function. This valid check code was implemented in the drm connector driver, but this check should be done in the adv7511 driver. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:17 UTC |
| 503d7a3 | Hyun Kwon | 06 May 2014, 02:52:29 UTC | drm: xilinx: encoder: Remove dependency on adv7511 The previous adv7511 patch moves the dependency code to inside the adv7511 driver. This makes the xilinx encoder more generic to have other encoders. Do not call encoder_sfuncs->set_config() when a mode is set, as the adv7511 driver handles it internally. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:16 UTC |
| 180560f | Hyun Kwon | 06 May 2014, 02:52:28 UTC | drm: adv7511: Configure adv7511 with default values This patch adds adv7511_set_default_config() which configures adv7511 device with default values. This configuration can be overwritten with custom values when client driver calls adv7511_set_config() explicitly. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:16 UTC |
| c0141c8 | Hyun Kwon | 06 May 2014, 02:52:27 UTC | drm: adv7511: Add the rgb format flag to adv7511_link_config Add the rgb format boolean flag to struct adv7511_link_config. This was in the drm encoder driver, but having it in the adv7511 driver would remove direct dependency. The flag is copied to the struct adv7511 to be used for the transmitter configuration. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:15 UTC |
| 6180d8f | Lars-Peter Clausen | 16 October 2013, 12:52:21 UTC | DRM: adv7511: Avoid uneccessary disconnected events Only insert a delayed disconnected event when we transition from connected to connect. If we transition from disconnected to connected there is no need for this since the system will already assume that the monitor was disconnected. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> | 08 May 2014, 16:01:14 UTC |
| 053112a | Lars-Peter Clausen | 16 October 2013, 12:50:16 UTC | DRM: adv7511: Properly initialize dpms_mode and status Set dpms_mode to DRM_MODE_DPMS_OFF and status to connector_status_disconnected to make sure that they match the state of the chip. This fixes an issue where the monitor was incorrectly reported as disconnected during cold boot. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> | 08 May 2014, 16:01:14 UTC |
| e06d0e7 | Lars-Peter Clausen | 04 September 2013, 15:35:05 UTC | drm: adv7511: Fix use after free We need to use the free the old edid buffer not the new one. Reported-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> | 08 May 2014, 16:01:13 UTC |
| c80437c | Harini Katakam | 05 May 2014, 09:33:14 UTC | spi: zynq-qspi: Dont write more than requested bytes to rxbuf In case of dual parallel odd byte transfer, write even bytes and read bytes accordingly but write only the requested number of bytes to rxbuf. Otherwise any user data adjacent to rxbuf might be corrupted. Improve related comments. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 08 May 2014, 16:01:12 UTC |
| 6ea220c | Michal Simek | 06 May 2014, 10:33:27 UTC | spi: cadence: Final syncup with mainline driver Trivial changes. Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:33:27 UTC |
| f6a6857 | Harini Katakam | 06 May 2014, 09:29:12 UTC | Documentation: devicetree: Update spi cadence bindings doc Add xilinx compatible string along with cadence. Compatible string should be first in the node. Make num-cs optional property. Add is-decoded-cs property. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:46 UTC |
| e232a36 | Harini Katakam | 06 May 2014, 09:29:11 UTC | spi: cadence: Add ARM dependency In Kconfig, add ARM dependency because readl/writel_relaxed are used. Remove dependency on SPI_MASTER as this is already under "if SPI_MASTER". Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:44 UTC |
| 251fc13 | Harini Katakam | 06 May 2014, 09:29:10 UTC | spi: cadence: Remove MODULE_ALIAS; add xilinx compatible string too Remove MODULE_ALIAS. Add xilinx specific compatible string along with IP compatible string according to mainline suggestions. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:42 UTC |
| dfb14ba | Harini Katakam | 06 May 2014, 09:29:09 UTC | spi: cadence: Rename remaining_byte and requested_bytes Rename to tx_bytes and rx_bytes to be clear. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:41 UTC |
| 01f7fc8 | Harini Katakam | 06 May 2014, 09:29:08 UTC | spi: cadence: Probe and remove cleanup Remove unbalanced master_put(). Remove unecessary prints. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:39 UTC |
| 5590618 | Harini Katakam | 06 May 2014, 09:29:07 UTC | spi: cadence: Chip select related changes Change chip select property name to "num-cs". Use a default value instead of giving error when num-cs is not found. Add "is-decoded-cs" property for using extended slave select; make necessary changes in cdns_spi_chipselect function. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:37 UTC |
| 42583de | Harini Katakam | 06 May 2014, 09:29:06 UTC | spi: cadence: Suspend/Resume cleanup Remove use of driver state in probe, suspend, resume and prep_transfer_hw. Just call master suspend/resume and disable_unprepare or prepare_enable clocks as required in suspend/resume. Remove debug prints in suspend/resume. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:36 UTC |
| 4f18a15 | Harini Katakam | 06 May 2014, 09:29:05 UTC | spi: cadence: setup cleanup Make CPOL/CPHA configuration a separate function. Since these dont vary between transfers and need to be set when preparing hw before enabling spi, call from prep_transfer_hw. Remove spi_setup as this is no longer required. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:34 UTC |
| db2a9e2 | Harini Katakam | 06 May 2014, 09:29:04 UTC | spi: cadence: Use transfer_one hook Implement transfer_one and set_cs functions. Change initialization, completion and irq handling accordingly. Remove timeout check as core does this. Remove reset function as it is no longer used. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:33 UTC |
| f585ba0 | Harini Katakam | 06 May 2014, 09:29:03 UTC | spi: cadence: Make register read and write operations static inline functions Make cdns_spi_read and cdns_spi_write static inline functions which take driver instance pointer, offset, data as inputs and perform necessary read/write operation. Modify init_hw function to pass instance pointer instead of register base address. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:31 UTC |
| 52d8f2e | Harini Katakam | 06 May 2014, 09:29:02 UTC | spi: cadence: irq related cleanup Request irq after init_hw in probe. Check for irq<=0 as 0 is also considered error condition. Return IRQ_HANDLED only when interrupt is handled, otherwise return IRQ_NONE. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:29 UTC |
| a1e2766 | Harini Katakam | 06 May 2014, 09:29:01 UTC | spi: cadence: Use bits per word checks in core Set master->bits_per_word_mask. Remove checks in driver. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:28 UTC |
| cd67650 | Harini Katakam | 06 May 2014, 09:29:00 UTC | spi: cadence: Use max speed checks in the core Set master->max_speed_hz to let core perform necessary checks. Remove checks in the driver. If transfer speed is requested as zero after checks in the core, dont set max speed, default to min speed. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 06 May 2014, 10:32:26 UTC |
| 91b7b1d | Michal Simek | 05 May 2014, 14:03:55 UTC | tty: serial: uartlite: Specify time for sending chars Xilinx MDM (Microblaze Debug Module) also contains uart interface via JTAG which is compatible with uartlite driver. This interface is really slow that's why timeout is setup to 1s. Make this time delay not to be cpu speed dependent. Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 05 May 2014, 14:43:44 UTC |
| 9cbf15c | Michal Simek | 12 March 2014, 09:18:30 UTC | microblaze: Wire-up new system calls sched_setattr/getattr Wire-up sched_setattr/getattr syscalls. Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 05 May 2014, 14:43:04 UTC |
| 2854a57 | Michal Simek | 01 May 2014, 07:23:08 UTC | net: gem: Do not probe phy if phy-handle is not setup Driver doesn't support automatic phy detection as macb driver that's why don't crash when phy is not found. Signed-off-by: Michal Simek <michal.simek@xilinx.com> Tested-by: Nathan Rossi <nathan.rossi@xilinx.com> | 01 May 2014, 09:57:58 UTC |
| db4f470 | Wang Guoli | 12 February 2014, 20:44:54 UTC | jffs2: unlock f->sem on error in jffs2_new_inode() If jffs2_new_inode() succeeds, it returns with f->sem held, and the caller is responsible for releasing the lock. If it fails, it still returns with the lock held, but the caller won't release the lock, which will lead to deadlock. Fix it by releasing the lock in jffs2_new_inode() on error. Signed-off-by: Wang Guoli <andy.wangguoli@huawei.com> Signed-off-by: Wang Nan <wangnan0@huawei.com> Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Cc: David Woodhouse <dwmw2@infradead.org> Cc: Wang Guoli <andy.wangguoli@huawei.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> [Brian: not marked for stable; no one observed deadlock, and I don't think it can happen here] Signed-off-by: Brian Norris <computersforpeace@gmail.com> | 01 May 2014, 09:57:57 UTC |
| a883d66 | Michal Simek | 30 April 2014, 06:09:13 UTC | Merge tag '3.14.2' into xlnx_3.14 commit 798d3c532b82dce20bcdc512572f542093142d02 Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Linux 3.14.2 Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 30 April 2014, 06:10:03 UTC |
| db9f423 | Hyun Kwon | 25 April 2014, 02:38:59 UTC | media: xilinx: dma: Stop entity chain walk at the entity with no sink pad When starting or stopping the pipeline, the pipeline driver walks the entities chain, and starts or stops all of them. When the walk reaches the entity with no sink pad, walk needs to stop. xvip_get_entity_sink() returns either the valid sink pad, or NULL when the entity doesn't have any sink pad. When NULL is returned, stop the walk. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Acked-by: Radhey Shyam Pandey <radheys@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 28 April 2014, 05:16:22 UTC |
| 75dd174 | Hyun Kwon | 26 April 2014, 02:38:42 UTC | drm: i2c: adv7511: Initialize the DPMS value in adv7511_probe() Initialize the DPMS value to DRM_MODE_DPMS_OFF in adv7511_probe() function. Otherwise, the value is set to DRM_MODE_DPMS_ON(=0) which doesn't reflect the actual device's DPMS state. This also results in not turning on the device properly. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 28 April 2014, 05:01:37 UTC |
| 682b763 | Hyun Kwon | 26 April 2014, 02:38:41 UTC | drm: xilinx: vtc: Return IRQ_NONE for no interrupt Return IRQ_NONE in the interrupt handler, when there's no interrupt. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 28 April 2014, 05:01:36 UTC |
| 6d72b0b | Hyun Kwon | 26 April 2014, 02:38:40 UTC | drm: xilinx: drv: Set bpp and color depth to drm_framebuffer The drm crtc helper doesn't set bpp and color depth for non RGB format drm_framebuffer, and that results in not supporting YUV format planes properly. This patch fixes and the YUV format drm_framebuffer can be allocated and used for planes. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 28 April 2014, 05:01:34 UTC |
| 04553a3 | Hyun Kwon | 26 April 2014, 02:38:39 UTC | drm: xilinx: drv: Add color depth info to the format descriptor Add color depth info to the the format descriptor. xilinx_drm_format_depth() can be used to retrieve the color depth value corresponding to the given drm format code. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 28 April 2014, 05:01:33 UTC |
| 5f84aca | Hyun Kwon | 26 April 2014, 02:38:38 UTC | drm: xilinx: Use the correct drm format code for yuv422 format Use the correct drm format code, DRM_FORMAT_YUYV, for Xilinx yuv422 format. Signed-off-by: Hyun Kwon <hyunk@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 28 April 2014, 05:00:57 UTC |
| 798d3c5 | Greg Kroah-Hartman | 27 April 2014, 00:19:26 UTC | Linux 3.14.2 | 27 April 2014, 00:19:26 UTC |
| 0af8322 | Oleg Nesterov | 07 April 2014, 22:38:29 UTC | exit: call disassociate_ctty() before exit_task_namespaces() commit c39df5fa37b0623589508c95515b4aa1531c524e upstream. Commit 8aac62706ada ("move exit_task_namespaces() outside of exit_notify()") breaks pppd and the exiting service crashes the kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000028 IP: ppp_register_channel+0x13/0x20 [ppp_generic] Call Trace: ppp_asynctty_open+0x12b/0x170 [ppp_async] tty_ldisc_open.isra.2+0x27/0x60 tty_ldisc_hangup+0x1e3/0x220 __tty_hangup+0x2c4/0x440 disassociate_ctty+0x61/0x270 do_exit+0x7f2/0xa50 ppp_register_channel() needs ->net_ns and current->nsproxy == NULL. Move disassociate_ctty() before exit_task_namespaces(), it doesn't make sense to delay it after perf_event_exit_task() or cgroup_exit(). This also allows to use task_work_add() inside the (nontrivial) code paths in disassociate_ctty(). Investigated by Peter Hurley. Signed-off-by: Oleg Nesterov <oleg@redhat.com> Reported-by: Sree Harsha Totakura <sreeharsha@totakura.in> Cc: Peter Hurley <peter@hurleysoftware.com> Cc: Sree Harsha Totakura <sreeharsha@totakura.in> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Jeff Dike <jdike@addtoit.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: Andrey Vagin <avagin@openvz.org> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:07 UTC |
| de661df | Oleg Nesterov | 07 April 2014, 22:38:41 UTC | wait: fix reparent_leader() vs EXIT_DEAD->EXIT_ZOMBIE race commit dfccbb5e49a621c1b21a62527d61fc4305617aca upstream. wait_task_zombie() first does EXIT_ZOMBIE->EXIT_DEAD transition and drops tasklist_lock. If this task is not the natural child and it is traced, we change its state back to EXIT_ZOMBIE for ->real_parent. The last transition is racy, this is even documented in 50b8d257486a "ptrace: partially fix the do_wait(WEXITED) vs EXIT_DEAD->EXIT_ZOMBIE race". wait_consider_task() tries to detect this transition and clear ->notask_error but we can't rely on ptrace_reparented(), debugger can exit and do ptrace_unlink() before its sub-thread sets EXIT_ZOMBIE. And there is another problem which were missed before: this transition can also race with reparent_leader() which doesn't reset >exit_signal if EXIT_DEAD, assuming that this task must be reaped by someone else. So the tracee can be re-parented with ->exit_signal != SIGCHLD, and if /sbin/init doesn't use __WALL it becomes unreapable. Change reparent_leader() to update ->exit_signal even if EXIT_DEAD. Note: this is the simple temporary hack for -stable, it doesn't try to solve all problems, it will be reverted by the next changes. Signed-off-by: Oleg Nesterov <oleg@redhat.com> Reported-by: Jan Kratochvil <jan.kratochvil@redhat.com> Reported-by: Michal Schmidt <mschmidt@redhat.com> Tested-by: Michal Schmidt <mschmidt@redhat.com> Cc: Al Viro <viro@ZenIV.linux.org.uk> Cc: Lennart Poettering <lpoetter@redhat.com> Cc: Roland McGrath <roland@hack.frob.com> Cc: Tejun Heo <tj@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:07 UTC |
| 5e7d38d | Li Zefan | 12 February 2014, 20:44:57 UTC | jffs2: remove from wait queue after schedule() commit 3ead9578443b66ddb3d50ed4f53af8a0c0298ec5 upstream. @wait is a local variable, so if we don't remove it from the wait queue list, later wake_up() may end up accessing invalid memory. This was spotted by eyes. Signed-off-by: Li Zefan <lizefan@huawei.com> Cc: David Woodhouse <dwmw2@infradead.org> Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:06 UTC |
| bd82a0a | Li Zefan | 12 February 2014, 20:44:56 UTC | jffs2: avoid soft-lockup in jffs2_reserve_space_gc() commit 13b546d96207c131eeae15dc7b26c6e7d0f1cad7 upstream. We triggered soft-lockup under stress test on 2.6.34 kernel. BUG: soft lockup - CPU#1 stuck for 60009ms! [lockf2.test:14488] ... [<bf09a4d4>] (jffs2_do_reserve_space+0x420/0x440 [jffs2]) [<bf09a528>] (jffs2_reserve_space_gc+0x34/0x78 [jffs2]) [<bf0a1350>] (jffs2_garbage_collect_dnode.isra.3+0x264/0x478 [jffs2]) [<bf0a2078>] (jffs2_garbage_collect_pass+0x9c0/0xe4c [jffs2]) [<bf09a670>] (jffs2_reserve_space+0x104/0x2a8 [jffs2]) [<bf09dc48>] (jffs2_write_inode_range+0x5c/0x4d4 [jffs2]) [<bf097d8c>] (jffs2_write_end+0x198/0x2c0 [jffs2]) [<c00e00a4>] (generic_file_buffered_write+0x158/0x200) [<c00e14f4>] (__generic_file_aio_write+0x3a4/0x414) [<c00e15c0>] (generic_file_aio_write+0x5c/0xbc) [<c012334c>] (do_sync_write+0x98/0xd4) [<c0123a84>] (vfs_write+0xa8/0x150) [<c0123d74>] (sys_write+0x3c/0xc0)] Fix this by adding a cond_resched() in the while loop. [akpm@linux-foundation.org: don't initialize `ret'] Signed-off-by: Li Zefan <lizefan@huawei.com> Cc: David Woodhouse <dwmw2@infradead.org> Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:06 UTC |
| a29cb38 | Ajesh Kunhipurayil Vijayan | 06 January 2014, 13:36:55 UTC | jffs2: Fix crash due to truncation of csize commit 41bf1a24c1001f4d0d41a78e1ac575d2f14789d7 upstream. mounting JFFS2 partition sometimes crashes with this call trace: [ 1322.240000] Kernel bug detected[#1]: [ 1322.244000] Cpu 2 [ 1322.244000] $ 0 : 0000000000000000 0000000000000018 000000003ff00070 0000000000000001 [ 1322.252000] $ 4 : 0000000000000000 c0000000f3980150 0000000000000000 0000000000010000 [ 1322.260000] $ 8 : ffffffffc09cd5f8 0000000000000001 0000000000000088 c0000000ed300de8 [ 1322.268000] $12 : e5e19d9c5f613a45 ffffffffc046d464 0000000000000000 66227ba5ea67b74e [ 1322.276000] $16 : c0000000f1769c00 c0000000ed1e0200 c0000000f3980150 0000000000000000 [ 1322.284000] $20 : c0000000f3a80000 00000000fffffffc c0000000ed2cfbd8 c0000000f39818f0 [ 1322.292000] $24 : 0000000000000004 0000000000000000 [ 1322.300000] $28 : c0000000ed2c0000 c0000000ed2cfab8 0000000000010000 ffffffffc039c0b0 [ 1322.308000] Hi : 000000000000023c [ 1322.312000] Lo : 000000000003f802 [ 1322.316000] epc : ffffffffc039a9f8 check_tn_node+0x88/0x3b0 [ 1322.320000] Not tainted [ 1322.324000] ra : ffffffffc039c0b0 jffs2_do_read_inode_internal+0x1250/0x1e48 [ 1322.332000] Status: 5400f8e3 KX SX UX KERNEL EXL IE [ 1322.336000] Cause : 00800034 [ 1322.340000] PrId : 000c1004 (Netlogic XLP) [ 1322.344000] Modules linked in: [ 1322.348000] Process jffs2_gcd_mtd7 (pid: 264, threadinfo=c0000000ed2c0000, task=c0000000f0e68dd8, tls=0000000000000000) [ 1322.356000] Stack : c0000000f1769e30 c0000000ed010780 c0000000ed010780 c0000000ed300000 c0000000f1769c00 c0000000f3980150 c0000000f3a80000 00000000fffffffc c0000000ed2cfbd8 ffffffffc039c0b0 ffffffffc09c6340 0000000000001000 0000000000000dec ffffffffc016c9d8 c0000000f39805a0 c0000000f3980180 0000008600000000 0000000000000000 0000000000000000 0000000000000000 0001000000000dec c0000000f1769d98 c0000000ed2cfb18 0000000000010000 0000000000010000 0000000000000044 c0000000f3a80000 c0000000f1769c00 c0000000f3d207a8 c0000000f1769d98 c0000000f1769de0 ffffffffc076f9c0 0000000000000009 0000000000000000 0000000000000000 ffffffffc039cf90 0000000000000017 ffffffffc013fbdc 0000000000000001 000000010003e61c ... [ 1322.424000] Call Trace: [ 1322.428000] [<ffffffffc039a9f8>] check_tn_node+0x88/0x3b0 [ 1322.432000] [<ffffffffc039c0b0>] jffs2_do_read_inode_internal+0x1250/0x1e48 [ 1322.440000] [<ffffffffc039cf90>] jffs2_do_crccheck_inode+0x70/0xd0 [ 1322.448000] [<ffffffffc03a1b80>] jffs2_garbage_collect_pass+0x160/0x870 [ 1322.452000] [<ffffffffc03a392c>] jffs2_garbage_collect_thread+0xdc/0x1f0 [ 1322.460000] [<ffffffffc01541c8>] kthread+0xb8/0xc0 [ 1322.464000] [<ffffffffc0106d18>] kernel_thread_helper+0x10/0x18 [ 1322.472000] [ 1322.472000] Code: 67bd0050 94a4002c 2c830001 <00038036> de050218 2403fffc 0080a82d 00431824 24630044 [ 1322.480000] ---[ end trace b052bb90e97dfbf5 ]--- The variable csize in structure jffs2_tmp_dnode_info is of type uint16_t, but it is used to hold the compressed data length(csize) which is declared as uint32_t. So, when the value of csize exceeds 16bits, it gets truncated when assigned to tn->csize. This is causing a kernel BUG. Changing the definition of csize in jffs2_tmp_dnode_info to uint32_t fixes the issue. Signed-off-by: Ajesh Kunhipurayil Vijayan <ajesh@broadcom.com> Signed-off-by: Kamlakant Patel <kamlakant.patel@broadcom.com> Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:06 UTC |
| 882b3a9 | Kamlakant Patel | 06 January 2014, 13:36:54 UTC | jffs2: Fix segmentation fault found in stress test commit 3367da5610c50e6b83f86d366d72b41b350b06a2 upstream. Creating a large file on a JFFS2 partition sometimes crashes with this call trace: [ 306.476000] CPU 13 Unable to handle kernel paging request at virtual address c0000000dfff8002, epc == ffffffffc03a80a8, ra == ffffffffc03a8044 [ 306.488000] Oops[#1]: [ 306.488000] Cpu 13 [ 306.492000] $ 0 : 0000000000000000 0000000000000000 0000000000008008 0000000000008007 [ 306.500000] $ 4 : c0000000dfff8002 000000000000009f c0000000e0007cde c0000000ee95fa58 [ 306.508000] $ 8 : 0000000000000001 0000000000008008 0000000000010000 ffffffffffff8002 [ 306.516000] $12 : 0000000000007fa9 000000000000ff0e 000000000000ff0f 80e55930aebb92bb [ 306.524000] $16 : c0000000e0000000 c0000000ee95fa5c c0000000efc80000 ffffffffc09edd70 [ 306.532000] $20 : ffffffffc2b60000 c0000000ee95fa58 0000000000000000 c0000000efc80000 [ 306.540000] $24 : 0000000000000000 0000000000000004 [ 306.548000] $28 : c0000000ee950000 c0000000ee95f738 0000000000000000 ffffffffc03a8044 [ 306.556000] Hi : 00000000000574a5 [ 306.560000] Lo : 6193b7a7e903d8c9 [ 306.564000] epc : ffffffffc03a80a8 jffs2_rtime_compress+0x98/0x198 [ 306.568000] Tainted: G W [ 306.572000] ra : ffffffffc03a8044 jffs2_rtime_compress+0x34/0x198 [ 306.580000] Status: 5000f8e3 KX SX UX KERNEL EXL IE [ 306.584000] Cause : 00800008 [ 306.588000] BadVA : c0000000dfff8002 [ 306.592000] PrId : 000c1100 (Netlogic XLP) [ 306.596000] Modules linked in: [ 306.596000] Process dd (pid: 170, threadinfo=c0000000ee950000, task=c0000000ee6e0858, tls=0000000000c47490) [ 306.608000] Stack : 7c547f377ddc7ee4 7ffc7f967f5d7fae 7f617f507fc37ff4 7e7d7f817f487f5f 7d8e7fec7ee87eb3 7e977ff27eec7f9e 7d677ec67f917f67 7f3d7e457f017ed7 7fd37f517f867eb2 7fed7fd17ca57e1d 7e5f7fe87f257f77 7fd77f0d7ede7fdb 7fba7fef7e197f99 7fde7fe07ee37eb5 7f5c7f8c7fc67f65 7f457fb87f847e93 7f737f3e7d137cd9 7f8e7e9c7fc47d25 7dbb7fac7fb67e52 7ff17f627da97f64 7f6b7df77ffa7ec5 80057ef17f357fb3 7f767fa27dfc7fd5 7fe37e8e7fd07e53 7e227fcf7efb7fa1 7f547e787fa87fcc 7fcb7fc57f5a7ffb 7fc07f6c7ea97e80 7e2d7ed17e587ee0 7fb17f9d7feb7f31 7f607e797e887faa 7f757fdd7c607ff3 7e877e657ef37fbd 7ec17fd67fe67ff7 7ff67f797ff87dc4 7eef7f3a7c337fa6 7fe57fc97ed87f4b 7ebe7f097f0b8003 7fe97e2a7d997cba 7f587f987f3c7fa9 ... [ 306.676000] Call Trace: [ 306.680000] [<ffffffffc03a80a8>] jffs2_rtime_compress+0x98/0x198 [ 306.684000] [<ffffffffc0394f10>] jffs2_selected_compress+0x110/0x230 [ 306.692000] [<ffffffffc039508c>] jffs2_compress+0x5c/0x388 [ 306.696000] [<ffffffffc039dc58>] jffs2_write_inode_range+0xd8/0x388 [ 306.704000] [<ffffffffc03971bc>] jffs2_write_end+0x16c/0x2d0 [ 306.708000] [<ffffffffc01d3d90>] generic_file_buffered_write+0xf8/0x2b8 [ 306.716000] [<ffffffffc01d4e7c>] __generic_file_aio_write+0x1ac/0x350 [ 306.720000] [<ffffffffc01d50a0>] generic_file_aio_write+0x80/0x168 [ 306.728000] [<ffffffffc021f7dc>] do_sync_write+0x94/0xf8 [ 306.732000] [<ffffffffc021ff6c>] vfs_write+0xa4/0x1a0 [ 306.736000] [<ffffffffc02202e8>] SyS_write+0x50/0x90 [ 306.744000] [<ffffffffc0116cc0>] handle_sys+0x180/0x1a0 [ 306.748000] [ 306.748000] Code: 020b202d 0205282d 90a50000 <90840000> 14a40038 00000000 0060602d 0000282d 016c5823 [ 306.760000] ---[ end trace 79dd088435be02d0 ]--- Segmentation fault This crash is caused because the 'positions' is declared as an array of signed short. The value of position is in the range 0..65535, and will be converted to a negative number when the position is greater than 32767 and causes a corruption and crash. Changing the definition to 'unsigned short' fixes this issue Signed-off-by: Jayachandran C <jchandra@broadcom.com> Signed-off-by: Kamlakant Patel <kamlakant.patel@broadcom.com> Signed-off-by: Brian Norris <computersforpeace@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:06 UTC |
| d465455 | Dan Carpenter | 14 February 2014, 09:05:49 UTC | fs: NULL dereference in posix_acl_to_xattr() commit 47ba9734403770a4c5e685b01f0a72b835dd4fff upstream. This patch moves the dereference of "buffer" after the check for NULL. The only place which passes a NULL parameter is gfs2_set_acl(). Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:06 UTC |
| c80e9ae | Eric Whitney | 01 April 2014, 23:49:30 UTC | ext4: fix premature freeing of partial clusters split across leaf blocks commit ad6599ab3ac98a4474544086e048ce86ec15a4d1 upstream. Xfstests generic/311 and shared/298 fail when run on a bigalloc file system. Kernel error messages produced during the tests report that blocks to be freed are already on the to-be-freed list. When e2fsck is run at the end of the tests, it typically reports bad i_blocks and bad free blocks counts. The bug that causes these failures is located in ext4_ext_rm_leaf(). Code at the end of the function frees a partial cluster if it's not shared with an extent remaining in the leaf. However, if all the extents in the leaf have been removed, the code dereferences an invalid extent pointer (off the front of the leaf) when the check for sharing is made. This generally has the effect of unconditionally freeing the partial cluster, which leads to the observed failures when the partial cluster is shared with the last extent in the next leaf. Fix this by attempting to free the cluster only if extents remain in the leaf. Any remaining partial cluster will be freed if possible when the next leaf is processed or when leaf removal is complete. Signed-off-by: Eric Whitney <enwlinux@gmail.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:06 UTC |
| 5ffaffe | Eric Whitney | 14 March 2014, 03:34:16 UTC | ext4: fix partial cluster handling for bigalloc file systems commit c06344939422bbd032ac967223a7863de57496b5 upstream. Commit 9cb00419fa, which enables hole punching for bigalloc file systems, exposed a bug introduced by commit 6ae06ff51e in an earlier release. When run on a bigalloc file system, xfstests generic/013, 068, 075, 083, 091, 100, 112, 127, 263, 269, and 270 fail with e2fsck errors or cause kernel error messages indicating that previously freed blocks are being freed again. The latter commit optimizes the selection of the starting extent in ext4_ext_rm_leaf() when hole punching by beginning with the extent supplied in the path argument rather than with the last extent in the leaf node (as is still done when truncating). However, the code in rm_leaf that initially sets partial_cluster to track cluster sharing on extent boundaries is only guaranteed to run if rm_leaf starts with the last node in the leaf. Consequently, partial_cluster is not correctly initialized when hole punching, and a cluster on the boundary of a punched region that should be retained may instead be deallocated. Signed-off-by: Eric Whitney <enwlinux@gmail.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:06 UTC |
| dc5af0f | Eric Whitney | 19 February 2014, 23:52:39 UTC | ext4: fix error return from ext4_ext_handle_uninitialized_extents() commit ce37c42919608e96ade3748fe23c3062a0a966c5 upstream. Commit 3779473246 breaks the return of error codes from ext4_ext_handle_uninitialized_extents() in ext4_ext_map_blocks(). A portion of the patch assigns that function's signed integer return value to an unsigned int. Consequently, negatively valued error codes are lost and can be treated as a bogus allocated block count. Signed-off-by: Eric Whitney <enwlinux@gmail.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:05 UTC |
| 2891d0f | Josef Bacik | 27 March 2014, 23:41:34 UTC | Btrfs: check for an extent_op on the locked ref commit 573a075567f0174551e2fad2a3164afd2af788f2 upstream. We could have possibly added an extent_op to the locked_ref while we dropped locked_ref->lock, so check for this case as well and loop around. Otherwise we could lose flag updates which would lead to extent tree corruption. Thanks, Signed-off-by: Josef Bacik <jbacik@fb.com> Signed-off-by: Chris Mason <clm@fb.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:05 UTC |
| 50b51ee | Josef Bacik | 07 March 2014, 00:01:07 UTC | Btrfs: fix deadlock with nested trans handles commit 3bbb24b20a8800158c33eca8564f432dd14d0bf3 upstream. Zach found this deadlock that would happen like this btrfs_end_transaction <- reduce trans->use_count to 0 btrfs_run_delayed_refs btrfs_cow_block find_free_extent btrfs_start_transaction <- increase trans->use_count to 1 allocate chunk btrfs_end_transaction <- decrease trans->use_count to 0 btrfs_run_delayed_refs lock tree block we are cowing above ^^ We need to only decrease trans->use_count if it is above 1, otherwise leave it alone. This will make nested trans be the only ones who decrease their added ref, and will let us get rid of the trans->use_count++ hack if we have to commit the transaction. Thanks, Reported-by: Zach Brown <zab@redhat.com> Signed-off-by: Josef Bacik <jbacik@fb.com> Tested-by: Zach Brown <zab@redhat.com> Signed-off-by: Chris Mason <clm@fb.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:05 UTC |
| 53dcb28 | Hidetoshi Seto | 05 February 2014, 07:34:38 UTC | Btrfs: skip submitting barrier for missing device commit f88ba6a2a44ee98e8d59654463dc157bb6d13c43 upstream. I got an error on v3.13: BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure (errors while submitting device barriers.) how to reproduce: > mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2 > wipefs -a /dev/sdf2 > mount -o degraded /dev/sdf1 /mnt > btrfs balance start -f -sconvert=single -mconvert=single -dconvert=single /mnt The reason of the error is that barrier_all_devices() failed to submit barrier to the missing device. However it is clear that we cannot do anything on missing device, and also it is not necessary to care chunks on the missing device. This patch stops sending/waiting barrier if device is missing. Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> Signed-off-by: Josef Bacik <jbacik@fb.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:05 UTC |
| 7de24f7 | Mark Tinguely | 03 April 2014, 20:10:49 UTC | xfs: fix directory hash ordering bug commit c88547a8119e3b581318ab65e9b72f27f23e641d upstream. Commit f5ea1100 ("xfs: add CRCs to dir2/da node blocks") introduced in 3.10 incorrectly converted the btree hash index array pointer in xfs_da3_fixhashpath(). It resulted in the the current hash always being compared against the first entry in the btree rather than the current block index into the btree block's hash entry array. As a result, it was comparing the wrong hashes, and so could misorder the entries in the btree. For most cases, this doesn't cause any problems as it requires hash collisions to expose the ordering problem. However, when there are hash collisions within a directory there is a very good probability that the entries will be ordered incorrectly and that actually matters when duplicate hashes are placed into or removed from the btree block hash entry array. This bug results in an on-disk directory corruption and that results in directory verifier functions throwing corruption warnings into the logs. While no data or directory entries are lost, access to them may be compromised, and attempts to remove entries from a directory that has suffered from this corruption may result in a filesystem shutdown. xfs_repair will fix the directory hash ordering without data loss occuring. [dchinner: wrote useful a commit message] Reported-by: Hannes Frederic Sowa <hannes@stressinduktion.org> Signed-off-by: Mark Tinguely <tinguely@sgi.com> Reviewed-by: Ben Myers <bpm@sgi.com> Signed-off-by: Dave Chinner <david@fromorbit.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:05 UTC |
| 1c23ab6 | Jan Kara | 03 April 2014, 21:46:23 UTC | bdi: avoid oops on device removal commit 5acda9d12dcf1ad0d9a5a2a7c646de3472fa7555 upstream. After commit 839a8e8660b6 ("writeback: replace custom worker pool implementation with unbound workqueue") when device is removed while we are writing to it we crash in bdi_writeback_workfn() -> set_worker_desc() because bdi->dev is NULL. This can happen because even though bdi_unregister() cancels all pending flushing work, nothing really prevents new ones from being queued from balance_dirty_pages() or other places. Fix the problem by clearing BDI_registered bit in bdi_unregister() and checking it before scheduling of any flushing work. Fixes: 839a8e8660b6777e7fe4e80af1a048aebe2b5977 Reviewed-by: Tejun Heo <tj@kernel.org> Signed-off-by: Jan Kara <jack@suse.cz> Cc: Derek Basehore <dbasehore@chromium.org> Cc: Jens Axboe <axboe@kernel.dk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:05 UTC |
| 67001f3 | Derek Basehore | 03 April 2014, 21:46:22 UTC | backing_dev: fix hung task on sync commit 6ca738d60c563d5c6cf6253ee4b8e76fa77b2b9e upstream. bdi_wakeup_thread_delayed() used the mod_delayed_work() function to schedule work to writeback dirty inodes. The problem with this is that it can delay work that is scheduled for immediate execution, such as the work from sync_inodes_sb(). This can happen since mod_delayed_work() can now steal work from a work_queue. This fixes the problem by using queue_delayed_work() instead. This is a regression caused by commit 839a8e8660b6 ("writeback: replace custom worker pool implementation with unbound workqueue"). The reason that this causes a problem is that laptop-mode will change the delay, dirty_writeback_centisecs, to 60000 (10 minutes) by default. In the case that bdi_wakeup_thread_delayed() races with sync_inodes_sb(), sync will be stopped for 10 minutes and trigger a hung task. Even if dirty_writeback_centisecs is not long enough to cause a hung task, we still don't want to delay sync for that long. We fix the problem by using queue_delayed_work() when we want to schedule writeback sometime in future. This function doesn't change the timer if it is already armed. For the same reason, we also change bdi_writeback_workfn() to immediately queue the work again in the case that the work_list is not empty. The same problem can happen if the sync work is run on the rescue worker. [jack@suse.cz: update changelog, add comment, use bdi_wakeup_thread_delayed()] Signed-off-by: Derek Basehore <dbasehore@chromium.org> Reviewed-by: Jan Kara <jack@suse.cz> Cc: Alexander Viro <viro@zento.linux.org.uk> Reviewed-by: Tejun Heo <tj@kernel.org> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: "Darrick J. Wong" <darrick.wong@oracle.com> Cc: Derek Basehore <dbasehore@chromium.org> Cc: Kees Cook <keescook@chromium.org> Cc: Benson Leung <bleung@chromium.org> Cc: Sonny Rao <sonnyrao@chromium.org> Cc: Luigi Semenzato <semenzato@chromium.org> Cc: Jens Axboe <axboe@kernel.dk> Cc: Dave Chinner <david@fromorbit.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:05 UTC |
| e5cf61c | Roberto Sassu | 03 February 2014, 12:56:04 UTC | ima: restore the original behavior for sending data with ima template commit c019e307ad82a8ee652b8ccbacf69ae94263b07b upstream. With the new template mechanism introduced in IMA since kernel 3.13, the format of data sent through the binary_runtime_measurements interface is slightly changed. Now, for a generic measurement, the format of template data (after the template name) is: template_len | field1_len | field1 | ... | fieldN_len | fieldN In addition, fields containing a string now include the '\0' termination character. Instead, the format for the 'ima' template should be: SHA1 digest | event name length | event name It must be noted that while in the IMA 3.13 code 'event name length' is 'IMA_EVENT_NAME_LEN_MAX + 1' (256 bytes), so that the template digest is calculated correctly, and 'event name' contains '\0', in the pre 3.13 code 'event name length' is exactly the string length and 'event name' does not contain the termination character. The patch restores the behavior of the IMA code pre 3.13 for the 'ima' template so that legacy userspace tools obtain a consistent behavior when receiving data from the binary_runtime_measurements interface regardless of which kernel version is used. Signed-off-by: Roberto Sassu <roberto.sassu@polito.it> Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:04 UTC |
| cf151ce | Claudio Takahasi | 25 July 2013, 19:34:24 UTC | Bluetooth: Fix removing Long Term Key commit 5981a8821b774ada0be512fd9bad7c241e17657e upstream. This patch fixes authentication failure on LE link re-connection when BlueZ acts as slave (peripheral). LTK is removed from the internal list after its first use causing PIN or Key missing reply when re-connecting the link. The LE Long Term Key Request event indicates that the master is attempting to encrypt or re-encrypt the link. Pre-condition: BlueZ host paired and running as slave. How to reproduce(master): 1) Establish an ACL LE encrypted link 2) Disconnect the link 3) Try to re-establish the ACL LE encrypted link (fails) > HCI Event: LE Meta Event (0x3e) plen 19 LE Connection Complete (0x01) Status: Success (0x00) Handle: 64 Role: Slave (0x01) ... @ Device Connected: 00:02:72:DC:29:C9 (1) flags 0x0000 > HCI Event: LE Meta Event (0x3e) plen 13 LE Long Term Key Request (0x05) Handle: 64 Random number: 875be18439d9aa37 Encryption diversifier: 0x76ed < HCI Command: LE Long Term Key Request Reply (0x08|0x001a) plen 18 Handle: 64 Long term key: 2aa531db2fce9f00a0569c7d23d17409 > HCI Event: Command Complete (0x0e) plen 6 LE Long Term Key Request Reply (0x08|0x001a) ncmd 1 Status: Success (0x00) Handle: 64 > HCI Event: Encryption Change (0x08) plen 4 Status: Success (0x00) Handle: 64 Encryption: Enabled with AES-CCM (0x01) ... @ Device Disconnected: 00:02:72:DC:29:C9 (1) reason 3 < HCI Command: LE Set Advertise Enable (0x08|0x000a) plen 1 Advertising: Enabled (0x01) > HCI Event: Command Complete (0x0e) plen 4 LE Set Advertise Enable (0x08|0x000a) ncmd 1 Status: Success (0x00) > HCI Event: LE Meta Event (0x3e) plen 19 LE Connection Complete (0x01) Status: Success (0x00) Handle: 64 Role: Slave (0x01) ... @ Device Connected: 00:02:72:DC:29:C9 (1) flags 0x0000 > HCI Event: LE Meta Event (0x3e) plen 13 LE Long Term Key Request (0x05) Handle: 64 Random number: 875be18439d9aa37 Encryption diversifier: 0x76ed < HCI Command: LE Long Term Key Request Neg Reply (0x08|0x001b) plen 2 Handle: 64 > HCI Event: Command Complete (0x0e) plen 6 LE Long Term Key Request Neg Reply (0x08|0x001b) ncmd 1 Status: Success (0x00) Handle: 64 > HCI Event: Disconnect Complete (0x05) plen 4 Status: Success (0x00) Handle: 64 Reason: Authentication Failure (0x05) @ Device Disconnected: 00:02:72:DC:29:C9 (1) reason 0 Signed-off-by: Claudio Takahasi <claudio.takahasi@openbossa.org> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:04 UTC |
| d0aed5c | Oleg Nesterov | 02 April 2014, 15:45:05 UTC | pid_namespace: pidns_get() should check task_active_pid_ns() != NULL commit d23082257d83e4bc89727d5aedee197e907999d2 upstream. pidns_get()->get_pid_ns() can hit ns == NULL. This task_struct can't go away, but task_active_pid_ns(task) is NULL if release_task(task) was already called. Alternatively we could change get_pid_ns(ns) to check ns != NULL, but it seems that other callers are fine. Signed-off-by: Oleg Nesterov <oleg@redhat.com> Cc: Eric W. Biederman ebiederm@xmission.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:04 UTC |
| 0561b77 | Alan Stern | 15 January 2014, 20:37:04 UTC | SCSI: sd: don't fail if the device doesn't recognize SYNCHRONIZE CACHE commit 7aae51347b21eb738dc1981df1365b57a6c5ee4e upstream. Evidently some wacky USB-ATA bridges don't recognize the SYNCHRONIZE CACHE command, as shown in this email thread: http://marc.info/?t=138978356200002&r=1&w=2 The fact that we can't tell them to drain their caches shouldn't prevent the system from going into suspend. Therefore sd_sync_cache() shouldn't return an error if the device replies with an Invalid Command ASC. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Reported-by: Sven Neumann <s.neumann@raumfeld.com> Tested-by: Daniel Mack <zonque@gmail.com> Signed-off-by: James Bottomley <JBottomley@Parallels.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:04 UTC |
| 4f1f4df | Peter Hurley | 22 February 2014, 12:31:21 UTC | tty: Fix low_latency BUG commit a9c3f68f3cd8d55f809fbdb0c138ed061ea1bd25 upstream. The user-settable knob, low_latency, has been the source of several BUG reports which stem from flush_to_ldisc() running in interrupt context. Since 3.12, which added several sleeping locks (termios_rwsem and buf->lock) to the input processing path, the frequency of these BUG reports has increased. Note that changes in 3.12 did not introduce this regression; sleeping locks were first added to the input processing path with the removal of the BKL from N_TTY in commit a88a69c91256418c5907c2f1f8a0ec0a36f9e6cc, 'n_tty: Fix loss of echoed characters and remove bkl from n_tty' and later in commit 38db89799bdf11625a831c5af33938dcb11908b6, 'tty: throttling race fix'. Since those changes, executing flush_to_ldisc() in interrupt_context (ie, low_latency set), is unsafe. However, since most devices do not validate if the low_latency setting is appropriate for the context (process or interrupt) in which they receive data, some reports are due to misconfiguration. Further, serial dma devices for which dma fails, resort to interrupt receiving as a backup without resetting low_latency. Historically, low_latency was used to force wake-up the reading process rather than wait for the next scheduler tick. The effect was to trim multiple milliseconds of latency from when the process would receive new data. Recent tests [1] have shown that the reading process now receives data with only 10's of microseconds latency without low_latency set. Remove the low_latency rx steering from tty_flip_buffer_push(); however, leave the knob as an optional hint to drivers that can tune their rx fifos and such like. Cleanup stale code comments regarding low_latency. [1] https://lkml.org/lkml/2014/2/20/434 "Yay.. thats an annoying historical pain in the butt gone." -- Alan Cox Reported-by: Beat Bolli <bbolli@ewanet.ch> Reported-by: Pavel Roskin <proski@gnu.org> Acked-by: David Sterba <dsterba@suse.cz> Cc: Grant Edwards <grant.b.edwards@gmail.com> Cc: Stanislaw Gruszka <sgruszka@redhat.com> Cc: Hal Murray <murray+fedora@ip-64-139-1-69.sjc.megapath.net> Signed-off-by: Peter Hurley <peter@hurleysoftware.com> Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:04 UTC |
| 192ae81 | Hannes Reinecke | 27 February 2014, 11:30:51 UTC | tty: Set correct tty name in 'active' sysfs attribute commit 723abd87f6e536f1353c8f64f621520bc29523a3 upstream. The 'active' sysfs attribute should refer to the currently active tty devices the console is running on, not the currently active console. The console structure doesn't refer to any device in sysfs, only the tty the console is running on has. So we need to print out the tty names in 'active', not the console names. There is one special-case, which is tty0. If the console is directed to it, we want 'tty0' to show up in the file, so user-space knows that the messages get forwarded to the active VT. The ->device() callback would resolve tty0, though. Hence, treat it special and don't call into the VT layer to resolve it (plymouth is known to depend on it). Cc: Lennart Poettering <lennart@poettering.net> Cc: Kay Sievers <kay@vrfy.org> Cc: Jiri Slaby <jslaby@suse.cz> Signed-off-by: Werner Fink <werner@suse.de> Signed-off-by: Hannes Reinecke <hare@suse.de> Signed-off-by: David Herrmann <dh.herrmann@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:04 UTC |
| 29b3118 | Tejun Heo | 02 April 2014, 20:40:52 UTC | kernfs: protect lazy kernfs_iattrs allocation with mutex commit 4afddd60a770560d370d6f85c5aef57c16bf7502 upstream. kernfs_iattrs is allocated lazily when operations which require it take place; unfortunately, the lazy allocation and returning weren't properly synchronized and when there are multiple concurrent operations, it might end up returning kernfs_iattrs which hasn't finished initialization yet or different copies to different callers. Fix it by synchronizing with a mutex. This can be smarter with memory barriers but let's go there if it actually turns out to be necessary. Signed-off-by: Tejun Heo <tj@kernel.org> Link: http://lkml.kernel.org/g/533ABA32.9080602@oracle.com Reported-by: Sasha Levin <sasha.levin@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:04 UTC |
| 52d6c48 | Richard Cochran | 05 March 2014, 16:10:52 UTC | kernfs: fix off by one error. commit 88391d49abb7d8dee91d405f96bd9e003cb6798d upstream. The hash values 0 and 1 are reserved for magic directory entries, but the code only prevents names hashing to 0. This patch fixes the test to also prevent hash value 1. Signed-off-by: Richard Cochran <richardcochran@gmail.com> Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:03 UTC |
| 541d5f2 | Ian Abbott | 10 April 2014, 18:41:57 UTC | staging: comedi: fix circular locking dependency in comedi_mmap() commit b34aa86f12e8848ba453215602c8c50fa63c4cb3 upstream. Mmapping a comedi data buffer with lockdep checking enabled produced the following kernel debug messages: ====================================================== [ INFO: possible circular locking dependency detected ] 3.5.0-rc3-ija1+ #9 Tainted: G C ------------------------------------------------------- comedi_test/4160 is trying to acquire lock: (&dev->mutex#2){+.+.+.}, at: [<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi] but task is already holding lock: (&mm->mmap_sem){++++++}, at: [<ffffffff810c96fe>] vm_mmap_pgoff+0x41/0x76 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&mm->mmap_sem){++++++}: [<ffffffff8106d0e8>] lock_acquire+0x97/0x105 [<ffffffff810ce3bc>] might_fault+0x6d/0x90 [<ffffffffa0031ffb>] do_devinfo_ioctl.isra.7+0x11e/0x14c [comedi] [<ffffffffa003227f>] comedi_unlocked_ioctl+0x256/0xe48 [comedi] [<ffffffff810f7fcd>] vfs_ioctl+0x18/0x34 [<ffffffff810f87fd>] do_vfs_ioctl+0x382/0x43c [<ffffffff810f88f9>] sys_ioctl+0x42/0x65 [<ffffffff81415c62>] system_call_fastpath+0x16/0x1b -> #0 (&dev->mutex#2){+.+.+.}: [<ffffffff8106c528>] __lock_acquire+0x101d/0x1591 [<ffffffff8106d0e8>] lock_acquire+0x97/0x105 [<ffffffff8140c894>] mutex_lock_nested+0x46/0x2a4 [<ffffffffa00313f4>] comedi_mmap+0x57/0x1d9 [comedi] [<ffffffff810d5816>] mmap_region+0x281/0x492 [<ffffffff810d5c92>] do_mmap_pgoff+0x26b/0x2a7 [<ffffffff810c971a>] vm_mmap_pgoff+0x5d/0x76 [<ffffffff810d493f>] sys_mmap_pgoff+0xc7/0x10d [<ffffffff81004d36>] sys_mmap+0x16/0x20 [<ffffffff81415c62>] system_call_fastpath+0x16/0x1b other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&mm->mmap_sem); lock(&dev->mutex#2); lock(&mm->mmap_sem); lock(&dev->mutex#2); *** DEADLOCK *** To avoid the circular dependency, just try to get the lock in `comedi_mmap()` instead of blocking. Since the comedi device's main mutex is heavily used, do a down-read of its `attach_lock` rwsemaphore instead. Trying to down-read `attach_lock` should only fail if some task has down-write locked it, and that is only done while the comedi device is being attached to or detached from a low-level hardware device. Unfortunately, acquiring the `attach_lock` doesn't prevent another task replacing the comedi data buffer we are trying to mmap. The details of the buffer are held in a `struct comedi_buf_map` and pointed to by `s->async->buf_map` where `s` is the comedi subdevice whose buffer we are trying to map. The `struct comedi_buf_map` is already reference counted with a `struct kref`, so we can stop it being freed prematurely. Modify `comedi_mmap()` to call new function `comedi_buf_map_from_subdev_get()` to read the subdevice's current buffer map pointer and increment its reference instead of accessing `async->buf_map` directly. Call `comedi_buf_map_put()` to decrement the reference once the buffer map structure has been dealt with. (Note that `comedi_buf_map_put()` does nothing if passed a NULL pointer.) `comedi_buf_map_from_subdev_get()` checks the subdevice's buffer map pointer has been set and the buffer map has been initialized enough for `comedi_mmap()` to deal with it (specifically, check the `n_pages` member has been set to a non-zero value). If all is well, the buffer map's reference is incremented and a pointer to it is returned. The comedi subdevice's spin-lock is used to protect the checks. Also use the spin-lock in `__comedi_buf_alloc()` and `__comedi_buf_free()` to protect changes to the subdevice's buffer map structure pointer and the buffer map structure's `n_pages` member. (This checking of `n_pages` is a bit clunky and I [Ian Abbott] plan to deal with it in the future.) Signed-off-by: Ian Abbott <abbotti@mev.co.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:03 UTC |
| a040978 | Ian Abbott | 13 March 2014, 15:30:39 UTC | staging: comedi: 8255_pci: initialize MITE data window commit 268d1e799663b795cba15c64f5d29407786a9dd4 upstream. According to National Instruments' PCI-DIO-96/PXI-6508/PCI-6503 User Manual, the physical address in PCI BAR1 needs to be OR'ed with 0x80 and written to register offset 0xC0 in the "MITE" registers (BAR0). Do so during initialization of the National Instruments boards handled by the "8255_pci" driver. The boards were previously handled by the "ni_pcidio" driver, where the initialization was done by `mite_setup()` in the "mite" module. The "mite" module comes with too much extra baggage for the "8255_pci" driver to deal with so use a local, simpler initialization function. Signed-off-by: Ian Abbott <abbotti@mev.co.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:03 UTC |
| 0313284 | Lan Tianyu | 15 March 2014, 17:37:13 UTC | ACPI / button: Add ACPI Button event via netlink routine commit 0bf6368ee8f25826d0645c0f7a4f17c8845356a4 upstream. Commit 1696d9d (ACPI: Remove the old /proc/acpi/event interface) removed ACPI Button event which originally was sent to userspace via /proc/acpi/event. This caused ACPI shutdown regression on gentoo in VirtualBox. Now ACPI events are sent to userspace via netlink, so add ACPI Button event back via netlink routine. References: https://bugzilla.kernel.org/show_bug.cgi?id=71721 Reported-and-tested-by: Richard Musil <richard.musil@gmail.com> Signed-off-by: Lan Tianyu <tianyu.lan@intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:03 UTC |
| 6b3ad94 | Mohit Kumar | 16 April 2014, 16:23:34 UTC | PCI: designware: Fix iATU programming for cfg1, io and mem viewport commit 017fcdc30cdae18c0946eef1ece1f14b4c7897ba upstream. This patch corrects iATU programming for cfg1, io and mem viewport. Enable ATU only after configuring it. Signed-off-by: Mohit Kumar <mohit.kumar@st.com> Signed-off-by: Ajay Khandelwal <ajay.khandelwal@st.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Acked-by: Jingoo Han <jg1.han@samsung.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:03 UTC |
| 3bbf168 | Mohit Kumar | 19 February 2014, 12:04:35 UTC | PCI: designware: Fix RC BAR to be single 64-bit non-prefetchable memory BAR commit dbffdd6862e67d60703f2df66c558bf448f81d6e upstream. The Synopsys PCIe core provides one pair of 32-bit BARs (BAR 0 and BAR 1). The BARs can be configured as follows: - One 64-bit BAR: BARs 0 and 1 are combined to form a single 64-bit BAR - Two 32-bit BARs: BARs 0 and 1 are two independent 32-bit BARs This patch corrects 64-bit, non-prefetchable memory BAR configuration implemented in dw driver. Signed-off-by: Mohit Kumar <mohit.kumar@st.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Cc: Pratyush Anand <pratyush.anand@st.com> Cc: Jingoo Han <jg1.han@samsung.com> Cc: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:03 UTC |
| 91800e9 | Neil Horman | 12 March 2014, 18:44:33 UTC | x86: Adjust irq remapping quirk for older revisions of 5500/5520 chipsets commit 6f8a1b335fde143b7407036e2368d3cd6eb55674 upstream. Commit 03bbcb2e7e2 (iommu/vt-d: add quirk for broken interrupt remapping on 55XX chipsets) properly disables irq remapping on the 5500/5520 chipsets that don't correctly perform that feature. However, when I wrote it, I followed the errata sheet linked in that commit too closely, and explicitly tied the activation of the quirk to revision 0x13 of the chip, under the assumption that earlier revisions were not in the field. Recently a system was reported to be suffering from this remap bug and the quirk hadn't triggered, because the revision id register read at a lower value that 0x13, so the quirk test failed improperly. Given this, it seems only prudent to adjust this quirk so that any revision less than 0x13 has the quirk asserted. [ tglx: Removed the 0x12 comparison of pci id 3405 as this is covered by the <= 0x13 check already ] Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Cc: Ingo Molnar <mingo@redhat.com> Cc: "H. Peter Anvin" <hpa@zytor.com> Cc: x86@kernel.org Link: http://lkml.kernel.org/r/1394649873-14913-1-git-send-email-nhorman@tuxdriver.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:02 UTC |
| f2355ea | Jason Wang | 28 February 2014, 03:30:29 UTC | x86, hyperv: Bypass the timer_irq_works() check commit ca3ba2a2f4a49a308e7d78c784d51b2332064f15 upstream. This patch bypass the timer_irq_works() check for hyperv guest since: - It was guaranteed to work. - timer_irq_works() may fail sometime due to the lpj calibration were inaccurate in a hyperv guest or a buggy host. In the future, we should get the tsc frequency from hypervisor and use preset lpj instead. [ hpa: I would prefer to not defer things to "the future" in the future... ] Cc: K. Y. Srinivasan <kys@microsoft.com> Cc: Haiyang Zhang <haiyangz@microsoft.com> Acked-by: K. Y. Srinivasan <kys@microsoft.com> Signed-off-by: Jason Wang <jasowang@redhat.com> Link: http://lkml.kernel.org/r/1393558229-14755-1-git-send-email-jasowang@redhat.com Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:02 UTC |
| d202b01 | Jiri Slaby | 14 April 2014, 14:46:50 UTC | Char: ipmi_bt_sm, fix infinite loop commit a94cdd1f4d30f12904ab528152731fb13a812a16 upstream. In read_all_bytes, we do unsigned char i; ... bt->read_data[0] = BMC2HOST; bt->read_count = bt->read_data[0]; ... for (i = 1; i <= bt->read_count; i++) bt->read_data[i] = BMC2HOST; If bt->read_data[0] == bt->read_count == 255, we loop infinitely in the 'for' loop. Make 'i' an 'int' instead of 'char' to get rid of the overflow and finish the loop after 255 iterations every time. Signed-off-by: Jiri Slaby <jslaby@suse.cz> Reported-and-debugged-by: Rui Hui Dian <rhdian@novell.com> Cc: Tomas Cech <tcech@suse.cz> Cc: Corey Minyard <minyard@acm.org> Cc: <openipmi-developer@lists.sourceforge.net> Signed-off-by: Corey Minyard <cminyard@mvista.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:02 UTC |
| 99c3556 | Mikulas Patocka | 14 April 2014, 20:58:55 UTC | user namespace: fix incorrect memory barriers commit e79323bd87808fdfbc68ce6c5371bd224d9672ee upstream. smp_read_barrier_depends() can be used if there is data dependency between the readers - i.e. if the read operation after the barrier uses address that was obtained from the read operation before the barrier. In this file, there is only control dependency, no data dependecy, so the use of smp_read_barrier_depends() is incorrect. The code could fail in the following way: * the cpu predicts that idx < entries is true and starts executing the body of the for loop * the cpu fetches map->extent[0].first and map->extent[0].count * the cpu fetches map->nr_extents * the cpu verifies that idx < extents is true, so it commits the instructions in the body of the for loop The problem is that in this scenario, the cpu read map->extent[0].first and map->nr_extents in the wrong order. We need a full read memory barrier to prevent it. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 27 April 2014, 00:19:02 UTC |
| 77301da | Hyun Kwon | 18 March 2014, 16:18:13 UTC | media: xilinx: dma: Change vdma configuration to cyclic-mode VDMA in non-cyclic mode doesn't work with fsync enabled. Fsync is needed to synchronize the pipeline with external input. So VDMA is configured to cyclic mode in this patch, with fsync enabled at synthesis. This patch is the only way to run the pipeline with external input, and it will be revisited after IP level investigation. Signed-off-by: Hyun Kwon <hyun.kwon@xilinx.com> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 25 April 2014, 05:06:35 UTC |
| e71aaa8 | Punnaiah Choudary Kalluri | 22 April 2014, 15:28:46 UTC | net: xilinx_emacps: Release receive BDs when there is a resource error Driver should clean/release the BDs when it detects a resource error to ensure the proper cleanup and allow the controller to recover from rx lockdown issue. Signed-off-by: Punnaiah Choudary Kalluri <punnaia@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 23 April 2014, 05:33:21 UTC |
| 4cd3f16 | Soren Brinkmann | 17 April 2014, 18:40:52 UTC | clk: zynq: Leave debug clocks in bootup state Make sure debug clocks stay enabled if the bootloader enabled them. Otherwise debug HW may crash due to bus-hangs caused by stopped clocks. Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 17:14:01 UTC |
| 9915fc2 | Harini Katakam | 18 April 2014, 05:42:39 UTC | spi: zynq-qspi: Changes to support dual parallel in new driver implementation This patch implements support for dual parallel on top of the recent changes to qspi driver which implements transfer->one. In parallel configuration, all commands are sent to both flash devices but the data is split into odd and even bits between lower and upper flash. As a result of this data should be of even length for write/read operations. For Ex., A program operation for 3 bytes will ideally be: CMD + 3 ADDR BYTES + 3 DATA BYTES In dual parallel case, this means 8 + 24 + (3*8/2) = 44 clock cycles will be sent. From the flash perspective, it only received 1 and 1/2 bytes' cycles. To avoid this error, when odd number of data bytes are asked to be transmitted, an extra byte is sent to compensate for the nibble flash devices will be expecting. Checks for bytes_to_receive/transmit < 0 were removed where not required. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 11:44:17 UTC |
| 46e79c6 | Harini Katakam | 18 April 2014, 05:42:38 UTC | mtd: m25p80: Cleanup after merge In the changed m25p80.c from mainline, quad read opcode is set based on flags in device table. This also takes care of dummy bytes. Make use of this. Added this flag to all devices known to support quad read. Updated m25p80.c from mainline calls spansion_quad_enable by default when quad mode is supported. This command is only required (supported) for spansion and winbond. Even in that case, it's a non-volatile setting. This implementation is not guaranteed to work when flash devices are connected in parallel/stacked configuration. Hence remove it and revisit if required. Updated m25p80.c from mainline uses "mode" in spi device structure to select quad read. This, in turn, is set by spi core based on dts properties. Hence, update tx and rx bus width in dts for above purpose. The flags M25P80_QUAD_READ and SECT_32 both have the same value - correct this. Remove unused variables in flash structure. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 11:44:16 UTC |
| 7ee1a97 | Harini Katakam | 18 April 2014, 05:42:37 UTC | spi: zynq-qspi: Dual stacked fixes Add configuration of U_PAGE/L_PAGE before asserting chip select. (This was removed earlier when subsystem workqueue, set_cs and transfer_one hooks were used) Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 11:44:15 UTC |
| 4f7eae8 | Harini Katakam | 11 April 2014, 06:36:28 UTC | spi: core: Increase timeout value The existing timeout value in wait_for_completion_timeout is calculated from the transfer length and speed with tolerance of 10msec. This is too low because this is used for error conditions such as hardware hang etc. The xfer->speed_hz considered may not be the actual speed set because the best clock divisor is chosen from a limited set such that the actual speed <= requested speed. This will lead to timeout being less than actual transfer time. Considering acceptable latencies, this timeout can be set to a value double the expected transfer plus 100 msecs. This patch adds the same in the core. Signed-off-by: Harini Katakam <harinik@xilinx.com> Signed-off-by: Mark Brown <broonie@linaro.org> | 22 April 2014, 11:44:15 UTC |
| b6e7001 | Mark Brown | 30 January 2014, 22:16:41 UTC | spi: Add a timeout when waiting for transfers Don't wait indefinitely for transfers to complete but time out after 10ms more than we expect the transfer to take on the wire. Signed-off-by: Mark Brown <broonie@linaro.org> | 22 April 2014, 11:44:14 UTC |
| 93f1d37 | S Mohan | 09 April 2014, 00:34:47 UTC | APF: Clean up on exit for xilinx-dma-apf Add an empty release function, and cleanup the remove function to ensure clean exit Signed-off-by: S Mohan <s.mohan@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 07:53:49 UTC |
| 356cbde | Soren Brinkmann | 11 April 2014, 16:24:03 UTC | clocksource/cadence_ttc: Adjust timer frequency on clock changes Implement a clock notifier to handle changes of the timer's input clock frequency. This syncs up the driver with mainline squashing the following commits into this one: Revert "clocksource/cadence_ttc: Remove clocksource clock notifier" This reverts commit 1fae768cc7e0f09eb0a173c3c2e8e51acce4e13c. Remove this work around in order to be able to cherry-pick the updates for the TTC from mainline. Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com> clocksource/cadence_ttc: Call clockevents_update_freq() with IRQs enabled The timer core takes care of serialization and IRQs. Hence the driver is no longer required to disable interrupts when calling clockevents_update_freq(). Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org> Acked-by: Michal Simek <michal.simek@xilinx.com> (cherry picked from commit 5f0ba3b462b2d36b3c28748863747fb1050f40d0) clocksource/cadence_ttc: Overhaul clocksource frequency adjustment The currently used method adjusting the clocksource to a changing input frequency does not work on kernels from 3.11 on. The new approach is to keep the timer frequency as constant as possible. I.e. - due to the TTC's prescaler limitations, allow frequency changes only if the frequency scales by a power of 2 - adjust the counter's divider on the fly when a frequency change occurs This limits cpufreq to scale by certain factors only. But we may keep the time base somewhat constant, so that sleep() & co keep working as expected, while supporting cpufreq. Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org> Acked-by: Michal Simek <michal.simek@xilinx.com> (cherry picked from commit b3e90722f6f53fa457a88146a877e34ea71d25ea) Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 07:06:38 UTC |
| 9166259 | Soren Brinkmann | 11 April 2014, 16:24:02 UTC | clockevents: Adjust timer interval when frequency changes clockevent devices in periodic mode are not updated when the frequency of the device changes. Issue a dev->set_mode() callback which forces the device to reevaluate the timer settings. Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com> Cc: linux-arm-kernel@lists.infradead.org Cc: Daniel Lezcano <daniel.lezcano@linaro.org> Cc: Michal Simek <michal.simek@xilinx.com> Link: http://lkml.kernel.org/r/1391466877-28908-3-git-send-email-soren.brinkmann@xilinx.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> (cherry picked from commit fe79a9ba11962a603fb6af68fcb476e64031e46c) Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 07:06:36 UTC |
| 41f66d9 | Thomas Gleixner | 11 April 2014, 16:24:01 UTC | clockevents: Serialize calls to clockevents_update_freq() in the core We can identify the broadcast device in the core and serialize all callers including interrupts on a different CPU against the update. Also, disabling interrupts is moved into the core allowing callers to leave interrutps enabled when calling clockevents_update_freq(). Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com> Cc: linux-arm-kernel@lists.infradead.org Cc: Soeren Brinkmann <soren.brinkmann@xilinx.com> Cc: Daniel Lezcano <daniel.lezcano@linaro.org> Cc: Michal Simek <michal.simek@xilinx.com> Link: http://lkml.kernel.org/r/1391466877-28908-2-git-send-email-soren.brinkmann@xilinx.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> (cherry picked from commit 627ee7947e2e83ba565c31c5c9373d6e364b1ecd) Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 07:06:34 UTC |
| 0efab15 | Michal Simek | 11 April 2014, 13:10:20 UTC | ARM: zynq: Sort Kconfig options Based on discussion on ARM mailing list options should be sorted. Signed-off-by: Michal Simek <michal.simek@xilinx.com> | 22 April 2014, 06:50:50 UTC |
