Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GIT 30a727e4802f48182d33e2bdaca586bfb6a62868 commit 6d4e81ed89c092cb156c8d19cb68c8733cd502b3 Author: Tomeu Vizoso <[email protected]> Date: Mon Nov 24 10:08:03 2014 +0100 cpufreq: Ref the policy object sooner Do it before it's assigned to cpufreq_cpu_data, otherwise when a driver tries to get the cpu frequency during initialization the policy kobj is referenced and we get this warning: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 64 at include/linux/kref.h:47 kobject_get+0x64/0x70() Modules linked in: CPU: 1 PID: 64 Comm: irq/77-tegra-ac Not tainted 3.18.0-rc4-next-20141114ccu-00050-g3eff942 #326 [<c0016fac>] (unwind_backtrace) from [<c001272c>] (show_stack+0x10/0x14) [<c001272c>] (show_stack) from [<c06085d8>] (dump_stack+0x98/0xd8) [<c06085d8>] (dump_stack) from [<c002892c>] (warn_slowpath_common+0x84/0xb4) [<c002892c>] (warn_slowpath_common) from [<c00289f8>] (warn_slowpath_null+0x1c/0x24) [<c00289f8>] (warn_slowpath_null) from [<c0220290>] (kobject_get+0x64/0x70) [<c0220290>] (kobject_get) from [<c03e944c>] (cpufreq_cpu_get+0x88/0xc8) [<c03e944c>] (cpufreq_cpu_get) from [<c03e9500>] (cpufreq_get+0xc/0x64) [<c03e9500>] (cpufreq_get) from [<c0285288>] (actmon_thread_isr+0x134/0x198) [<c0285288>] (actmon_thread_isr) from [<c0069008>] (irq_thread_fn+0x1c/0x40) [<c0069008>] (irq_thread_fn) from [<c0069324>] (irq_thread+0x134/0x174) [<c0069324>] (irq_thread) from [<c0040290>] (kthread+0xdc/0xf4) [<c0040290>] (kthread) from [<c000f4b8>] (ret_from_fork+0x14/0x3c) ---[ end trace b7bd64a81b340c59 ]--- Signed-off-by: Tomeu Vizoso <[email protected]> Acked-by: Viresh Kumar <[email protected]> Signed-off-by: Rafael J. Wysocki <[email protected]> commit e874bf5f7647a9fdf14d72dbb376ec95327e3a81 Author: Lars-Peter Clausen <[email protected]> Date: Tue Nov 25 21:41:03 2014 +0100 ASoC: Disable regmap helpers if regmap is disabled If regmap is disabled there will be no users of the ASoC regmap helpers. Furthermore regmap_exit() will no be defined causing the following compile error: sound/soc/soc-core.c: In function 'snd_soc_component_exit_regmap': sound/soc/soc-core.c:2645:2: error: implicit declaration of function 'regmap_exit' [-Werror=implicit-function-declaration] So disable the helpers if regmap is disabled. Reported-by: kbuild test robot <[email protected]> Fixes: 20feb881988c ASoC: Add helper functions for deferred regmap setup") Signed-off-by: Lars-Peter Clausen <[email protected]> Signed-off-by: Mark Brown <[email protected]> commit a5e9ab291c608c62691b9d565104a30d931998bf Author: Greg Kroah-Hartman <[email protected]> Date: Tue Nov 25 12:46:39 2014 -0800 Revert "serial: of-serial: add PM suspend/resume support" This reverts commit 2dea53bf57783f243c892e99c10c6921e956aa7e. Turns out to be broken :( Cc: Jingchang Lu <[email protected]> Cc: Arnd Bergmann <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 86261fdd65ce076c0aa05dbf3f5f5fe10aab1bcf Author: Petr Cvek <[email protected]> Date: Tue Nov 25 06:05:33 2014 +0100 i2c: pxa: add support for SCCB devices Add support for SCCB by implementing I2C_M_IGNORE_NAK and I2C_M_STOP flags and advertising functionality flag I2C_FUNC_PROTOCOL_MANGLING. Also fixed missing functionality flag I2C_FUNC_NOSTART. Signed-off-by: Petr Cvek <[email protected]> Signed-off-by: Wolfram Sang <[email protected]> commit 23173eae7b9a5389d3f7031b77cde34f63b814a2 Author: Alexander Kochetkov <[email protected]> Date: Tue Nov 25 02:20:55 2014 +0400 omap: i2c: don't check bus state IP rev3.3 and earlier Commit 0f5768bf894f ("i2c: omap: implement workaround for handling invalid BB-bit values") introduce the error result in boot test fault on OMAP3530 boards. The patch fix the error (disable i2c bus test for OMAP3530). Reported-by: Kevin Hilman <[email protected]> Signed-off-by: Alexander Kochetkov <[email protected]> Fixes: 0f5768bf894f ("i2c: omap: implement workaround for handling invalid BB-bit values") Tested-by: Tony Lindgren <[email protected]> Tested-by: Kevin Hilman <[email protected]> Signed-off-by: Wolfram Sang <[email protected]> commit a620a6bc1c94c22d6c312892be1e0ae171523125 Author: Thadeu Lima de Souza Cascardo <[email protected]> Date: Tue Nov 25 14:21:11 2014 -0200 tg3: fix ring init when there are more TX than RX channels If TX channels are set to 4 and RX channels are set to less than 4, using ethtool -L, the driver will try to initialize more RX channels than it has allocated, causing an oops. This fix only initializes the RX ring if it has been allocated. Signed-off-by: Thadeu Lima de Souza Cascardo <[email protected]> Signed-off-by: David S. Miller <[email protected]> commit 69b93607a9862b1db2f0f2e078e1396f8e20fa9b Author: Lars-Peter Clausen <[email protected]> Date: Tue Nov 25 20:29:40 2014 +0100 ASoC: qi_lb60: Pass flags to gpiod_get() Pass flags to gpiod_get() to automatically configure the GPIOs. This is shorter and not passing any flags to gpiod_get() will eventually no longer be supported. Signed-off-by: Lars-Peter Clausen <[email protected]> Signed-off-by: Mark Brown <[email protected]> commit c3658e8d0f10147fc86018be7f11668246c156d3 Author: Eric Dumazet <[email protected]> Date: Tue Nov 25 07:40:04 2014 -0800 tcp: fix possible NULL dereference in tcp_vX_send_reset() After commit ca777eff51f7 ("tcp: remove dst refcount false sharing for prequeue mode") we have to relax check against skb dst in tcp_v[46]_send_reset() if prequeue dropped the dst. If a socket is provided, a full lookup was done to find this socket, so the dst test can be skipped. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=88191 Reported-by: Jaša Bartelj <[email protected]> Signed-off-by: Eric Dumazet <[email protected]> Reported-by: Daniel Borkmann <[email protected]> Fixes: ca777eff51f7 ("tcp: remove dst refcount false sharing for prequeue mode") Signed-off-by: David S. Miller <[email protected]> commit 7d63a5f9b25ba6b130da8eb2d32a72b1462d0249 Author: Larry Finger <[email protected]> Date: Tue Nov 25 10:32:07 2014 -0600 rtlwifi: Change order in device startup The existing order of steps when starting the PCI devices works for 2.4G devices, but fails to initialize the 5G section of the RTL8821AE hardware. This patch is needed to fix the regression reported in Bug #88811 (https://bugzilla.kernel.org/show_bug.cgi?id=88811). Reported-by: Valerio Passini <[email protected]> Tested-by: Valerio Passini <[email protected]> Signed-off-by: Larry Finger <[email protected]> Cc: Valerio Passini <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit a91ed1901a80b401afa1b718d941d3450d868151 Author: Larry Finger <[email protected]> Date: Tue Nov 25 10:32:06 2014 -0600 rtlwifi: rtl8821ae: Fix 5G detection problem The changes associated with moving this driver from staging to the regular tree missed one section setting the allowable rates for the 5GHz band. This patch is needed to fix the regression reported in Bug #88811 (https://bugzilla.kernel.org/show_bug.cgi?id=88811). Reported-by: Valerio Passini <[email protected]> Tested-by: Valerio Passini <[email protected]> Signed-off-by: Larry Finger <[email protected]> Cc: Valerio Passini <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 43612d7c04f1a4f5e60104143918fcdf018b66ee Author: Pablo Neira <[email protected]> Date: Tue Nov 25 19:54:47 2014 +0100 Revert "netfilter: conntrack: fix race in __nf_conntrack_confirm against get_next_corpse" This reverts commit 5195c14c8b27cc0b18220ddbf0e5ad3328a04187. If the conntrack clashes with an existing one, it is left out of the unconfirmed list, thus, crashing when dropping the packet and releasing the conntrack since golden rule is that conntracks are always placed in any of the existing lists for traceability reasons. Reported-by: Daniel Borkmann <[email protected]> Fixes: https://bugzilla.kernel.org/show_bug.cgi?id=88841 Signed-off-by: Pablo Neira Ayuso <[email protected]> Signed-off-by: David S. Miller <[email protected]> commit 3dc2b6a8d38cf6c7604ec25f3d50d6ec8da04435 Author: Alexander Duyck <[email protected]> Date: Mon Nov 24 20:08:38 2014 -0800 vxlan: Fix boolean flip in VXLAN_F_UDP_ZERO_CSUM6_[TX|RX] In "vxlan: Call udp_sock_create" there was a logic error that resulted in the default for IPv6 VXLAN tunnels going from using checksums to not using checksums. Since there is currently no support in iproute2 for setting these values it means that a kernel after the change cannot talk over a IPv6 VXLAN tunnel to a kernel prior the change. Fixes: 3ee64f3 ("vxlan: Call udp_sock_create") Cc: Tom Herbert <[email protected]> Signed-off-by: Alexander Duyck <[email protected]> Acked-by: Tom Herbert <[email protected]> Signed-off-by: David S. Miller <[email protected]> commit f3750817a9034bd8cbb5ba583cd544e7cf14c7d8 Author: Alexander Duyck <[email protected]> Date: Mon Nov 24 20:08:32 2014 -0800 ip6_udp_tunnel: Fix checksum calculation The UDP checksum calculation for VXLAN tunnels is currently using the socket addresses instead of the actual packet source and destination addresses. As a result the checksum calculated is incorrect in some cases. Also uh->check was being set twice, first it was set to 0, and then it is set again in udp6_set_csum. This change removes the redundant assignment to 0. Fixes: acbf74a7 ("vxlan: Refactor vxlan driver to make use of the common UDP tunnel functions.") Cc: Andy Zhou <[email protected]> Signed-off-by: Alexander Duyck <[email protected]> Signed-off-by: David S. Miller <[email protected]> commit 18ca43823f3ce111c6efb8cc90d9f35246527727 Author: Amitkumar Karwar <[email protected]> Date: Tue Nov 25 06:43:06 2014 -0800 mwifiex: add Tx status support for ACTION frames ACK status (0/1) for ACTION frames is informed to cfg80211. We will extend existing logic used for EAPOL frames. The cfg80211 API is different here. Also, we need to explicitly free cloned skb. Signed-off-by: Cathy Luo <[email protected]> Signed-off-by: Avinash Patil <[email protected]> Signed-off-by: Amitkumar Karwar <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 808bbebcc8fcbcb2b93aefd8b181a0fdccb407c6 Author: Amitkumar Karwar <[email protected]> Date: Tue Nov 25 06:43:05 2014 -0800 mwifiex: add Tx status support for EAPOL packets Firmware notifies the driver through event if EAPOL data packet has been acked or not. We will inform this status to userspace listening on a socket. Signed-off-by: Cathy Luo <[email protected]> Signed-off-by: Avinash Patil <[email protected]> Signed-off-by: Amitkumar Karwar <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 381e9fffe6b8343c2479939178ef7ded50bf32d3 Author: Amitkumar Karwar <[email protected]> Date: Tue Nov 25 06:43:04 2014 -0800 mwifiex: skip delay main work logic for USB interface. We had introduced delay main work logic to avoid processing interrupts when Rx pending packet count reaches high threshold. interrupt processing is restarted later when packet count reduces lower threashold. This helped to reduce unnecessary overhead and improve throughput for SD and PCIe chipsets. As there are no interrupts for USB, we will skip this logic for USB chipsets. Signed-off-by: Cathy Luo <[email protected]> Signed-off-by: Avinash Patil <[email protected]> Signed-off-by: Amitkumar Karwar <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 798ea8eec16d33e0553b6be7175a23e8ddf60eee Author: Amitkumar Karwar <[email protected]> Date: Tue Nov 25 06:43:03 2014 -0800 mwifiex: fix scan problem on big endian platforms This patch adds missing endian conversion for beacon size while processing scan response. Reported-by: Daniel Mosquera <[email protected]> Tested-by: Daniel Mosquera <[email protected]> Signed-off-by: Avinash Patil <[email protected]> Signed-off-by: Amitkumar Karwar <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 51974611154038f1aaf6ce843bdc6445d5684ee3 Author: Amitkumar Karwar <[email protected]> Date: Tue Nov 25 06:43:02 2014 -0800 mwifiex: fix sparse warning This patch fixes following sparse warnings: drivers/net/wireless/mwifiex/util.c:152:19: warning: cast from restricted __le16 drivers/net/wireless/mwifiex/util.c:152:19: warning: restricted __le16 degrades to integer Signed-off-by: Amitkumar Karwar <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 8b537686a116b060475d94b6f548c78289935fef Author: Lorenzo Bianconi <[email protected]> Date: Tue Nov 25 00:21:41 2014 +0100 ath9k: add TPC capability to TX descriptor path Add TPC capability to TX descriptor path. Cap per-packet TX power according to TX power per-rate tables. Currently TPC is supported just by AR9003 based chips Signed-off-by: Lorenzo Bianconi <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 23f53dd3062628d2215cab810e4cfc22c29d47ee Author: Lorenzo Bianconi <[email protected]> Date: Tue Nov 25 00:21:40 2014 +0100 ath9k: add TX power per-rate tables Add TX power per-rate tables for different MIMO modes (e.g STBC) in order to cap the maximum TX power value per-rate in the TX descriptor path. Cap TX power for self generated frames (ACK, RTS/CTS). Currently TPC is supported just by AR9003 based chips Signed-off-by: Lorenzo Bianconi <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 4f3fff148679d5850994e53c57eb798cd201c88c Author: Arend van Spriel <[email protected]> Date: Thu Nov 20 22:27:02 2014 +0100 brcmfmac: correct .disconnect() callback while connecting When the driver has sent a join iovar to the firmware it waits for the events to report result of the connection. However, the wpa_supplicant will request a .disconnect() after a timeout. So upon calling .disconnect() the interface state may still be CONNECTING. Clear the CONNECTING bit as well. Reviewed-by: Hante Meuleman <[email protected]> Reviewed-by: Pieter-Paul Giesberts <[email protected]> Signed-off-by: Arend van Spriel <[email protected]> Signed-off-by: John W. Linville <[email protected]> commit 3fedeab10b3bb09744a6467fe7cd157f055137c3 Author: Hariprasad Shenai <[email protected]> Date: Tue Nov 25 08:33:58 2014 +0530 cxgb4/cxgb4vf/csiostor: Add T4/T5 PCI ID Table Add a new file t4_pci_id_tbl.h that contains T4/T5 PCI ID Table so that for all drivers that uses T4/T5 PCI functions changes can be done in one place. checkpatch.pl script reports following error, which if tried to fix ends up in compilation error. ERROR: Macros with complex values should be enclosed in parentheses +#define CH_PCI_DEVICE_ID_TABLE_DEFINE_END \ + { 0, } \ + } WARNING: added, moved or deleted file(s), does MAINTAINERS need updating? new file mode 100644 ERROR: Macros with complex values should be enclosed in parentheses +#define CH_PCI_ID_TABLE_FENTRY(devid) \ + CH_PCI_ID_TABLE_ENTRY((devid) | \ + ((CH_PCI_DEVICE_ID_FUNCTION) << 8)), \ + CH_PCI_ID_TABLE_ENTRY((devid) | \ + ((CH_PCI_DEVICE_ID_FUNCTION2) << 8)) ERROR: Macros with complex values should be enclosed in parentheses +#define CH_PCI_DEVICE_ID_TABLE_DEFINE_END { 0, } } ERROR: Macros with complex values should be enclosed in parentheses +#define CH_PCI_DEVICE_ID_TABLE_DEFINE_END { 0, } } Signed-off-by: Hariprasad Shenai <[email protected]> Signed-off-by: David S. Miller <[email protected]> commit 138a7f49270fde7547afe976a01cef2b9fbf3a0e Author: Andrew Lutomirski <[email protected]> Date: Mon Nov 24 12:02:29 2014 -0800 net-timestamp: Fix a documentation typo SOF_TIMESTAMPING_OPT_ID puts the id in ee_data, not ee_info. Cc: Willem de Bruijn <[email protected]> Signed-off-by: Andy Lutomirski <[email protected]> Acked-by: Willem de Bruijn <[email protected]> Signed-off-by: David S. Miller <[email protected]> commit c2d00875c151087c41e23a5afd6bd807019c9a53 Author: Dmitry Monakhov <[email protected]> Date: Tue Nov 25 13:18:39 2014 -0500 ext4: fix potential use after free during resize We need some sort of synchronization while updating ->s_group_desc because there are a lot of users which can access old ->s_group_desc array after it was released. It is reasonable to use lightweight seqcount_t here instead of RCU. Signed-off-by: Dmitry Monakhov <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit d6d12b85f7daa15a02cabfc9026225b6e16d9aad Author: Dmitry Monakhov <[email protected]> Date: Tue Nov 25 13:08:04 2014 -0500 ext4: cleanup GFP flags inside resize path We must use GFP_NOFS instead GFP_KERNEL inside ext4_mb_add_groupinfo and ext4_calculate_overhead() because they are called from inside a journal transaction. Call trace: ioctl ->ext4_group_add ->journal_start ->ext4_setup_new_descs ->ext4_mb_add_groupinfo -> GFP_KERNEL ->ext4_flex_group_add ->ext4_update_super ->ext4_calculate_overhead -> GFP_KERNEL ->journal_stop Signed-off-by: Dmitry Monakhov <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit 2193dda5eec60373c7a061c129c6ab9d658f78e9 Author: Alan Stern <[email protected]> Date: Tue Nov 25 12:28:46 2014 +0100 USB: host: Remove ehci-octeon and ohci-octeon drivers Remove special-purpose octeon drivers and instead use ehci-platform and ohci-platform as suggested with http://marc.info/?l=linux-mips&m=140139694721623&w=2 [andreas.herrmann: fixed compile error] Cc: David Daney <[email protected]> Cc: Alex Smith <[email protected]> Signed-off-by: Alan Stern <[email protected]> Signed-off-by: Andreas Herrmann <[email protected]> Acked-by: Ralf Baechle <[email protected]> Tested-by: Aaro Koskinen <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit f83b050b3c223278c4299d8736ffdafceb2c6c7c Author: Jan Kara <[email protected]> Date: Tue Nov 25 11:55:24 2014 -0500 ext4: introduce aging to extent status tree Introduce a simple aging to extent status tree. Each extent has a REFERENCED bit which gets set when the extent is used. Shrinker then skips entries with referenced bit set and clears the bit. Thus frequently used extents have higher chances of staying in memory. Signed-off-by: Jan Kara <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit ee4bb47d2bc8149b11e4d1dc2378730cb166d5a8 Author: Jan Kara <[email protected]> Date: Tue Nov 25 11:53:47 2014 -0500 ext4: cleanup flag definitions for extent status tree Currently flags for extent status tree are defined twice, once shifted and once without a being shifted. Consolidate these definitions into one place and make some computations automatic to make adding flags less error prone. Compiler should be clever enough to figure out these are constants and generate the same code. Signed-off-by: Jan Kara <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit 9915b75359e3cc99a4dd3b39f83f394395f8f1aa Author: Jan Kara <[email protected]> Date: Tue Nov 25 11:51:23 2014 -0500 ext4: limit number of scanned extents in status tree shrinker Currently we scan extent status trees of inodes until we reclaim nr_to_scan extents. This can however require a lot of scanning when there are lots of delayed extents (as those cannot be reclaimed). Change shrinker to work as shrinkers are supposed to and *scan* only nr_to_scan extents regardless of how many extents did we actually reclaim. We however need to be careful and avoid scanning each status tree from the beginning - that could lead to a situation where we would not be able to reclaim anything at all when first nr_to_scan extents in the tree are always unreclaimable. We remember with each inode offset where we stopped scanning and continue from there when we next come across the inode. Note that we also need to update places calling __es_shrink() manually to pass reasonable nr_to_scan to have a chance of reclaiming anything and not just 1. Signed-off-by: Jan Kara <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit 149f510220f5df2e3eada0dfc8a0b18208ffaf65 Author: Jan Kara <[email protected]> Date: Tue Nov 25 11:49:25 2014 -0500 ext4: move handling of list of shrinkable inodes into extent status code Currently callers adding extents to extent status tree were responsible for adding the inode to the list of inodes with freeable extents. This is error prone and puts list handling in unnecessarily many places. Just add inode to the list automatically when the first non-delay extent is added to the tree and remove inode from the list when the last non-delay extent is removed. Signed-off-by: Jan Kara <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit aaf3ce623d42e534492c19e3b314c800e8d97b84 Author: Zheng Liu <[email protected]> Date: Tue Nov 25 11:47:01 2014 -0500 ext4: change LRU to round-robin in extent status tree shrinker In this commit we discard the lru algorithm for inodes with extent status tree because it takes significant effort to maintain a lru list in extent status tree shrinker and the shrinker can take a long time to scan this lru list in order to reclaim some objects. We replace the lru ordering with a simple round-robin. After that we never need to keep a lru list. That means that the list needn't be sorted if the shrinker can not reclaim any objects in the first round. Cc: Andreas Dilger <[email protected]> Signed-off-by: Zheng Liu <[email protected]> Signed-off-by: Jan Kara <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit 036d4c3764f230f39fba5b2574a6c29b00a48bf9 Author: Zheng Liu <[email protected]> Date: Tue Nov 25 11:44:37 2014 -0500 ext4: cache extent hole in extent status tree for ext4_da_map_blocks() Currently extent status tree doesn't cache extent hole when a write looks up in extent tree to make sure whether a block has been allocated or not. In this case, we don't put extent hole in extent cache because later this extent might be removed and a new delayed extent might be added back. But it will cause a defect when we do a lot of writes. If we don't put extent hole in extent cache, the following writes also need to access extent tree to look at whether or not a block has been allocated. It brings a cache miss. This commit fixes this defect. Also if the inode doesn't have any extent, this extent hole will be cached as well. Cc: Andreas Dilger <[email protected]> Signed-off-by: Zheng Liu <[email protected]> Signed-off-by: Jan Kara <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit f3c08e9bdc8b51aa941aed2fedb4ab468ce7588e Author: Jan Kara <[email protected]> Date: Tue Nov 25 11:41:49 2014 -0500 ext4: fix block reservation for bigalloc filesystems For bigalloc filesystems we have to check whether newly requested inode block isn't already part of a cluster for which we already have delayed allocation reservation. This check happens in ext4_ext_map_blocks() and that function sets EXT4_MAP_FROM_CLUSTER if that's the case. However if ext4_da_map_blocks() finds in extent cache information about the block, we don't call into ext4_ext_map_blocks() and thus we always end up getting new reservation even if the space for cluster is already reserved. This results in overreservation and premature ENOSPC reports. Fix the problem by checking for existing cluster reservation already in ext4_da_map_blocks(). That simplifies the logic and actually allows us to get rid of the EXT4_MAP_FROM_CLUSTER flag completely. Signed-off-by: Jan Kara <[email protected]> Signed-off-by: Theodore Ts'o <[email protected]> commit 439b8bddaa1ebed9f9f8fb2f6f33f5e639d76ab8 Author: Dmitry Lavnikevich <[email protected]> Date: Fri Nov 21 18:29:07 2014 +0300 mfd: da9063: Get irq base dynamically before registering device After registering mfd device with proper irq_base platform_get_irq_byname() calls will return VIRQ instead of local IRQ. This fixes da9063 rtc registration issue: da9063-rtc da9063-rtc: Failed to request ALARM IRQ 1: -22 Signed-off-by: Dmitry Lavnikevich <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 2c20f6de95afef89127163d16c88cd0456c48077 Author: Krzysztof Kozlowski <[email protected]> Date: Wed Nov 12 16:28:02 2014 +0100 mfd: max14577: Fix obvious typo in company name in copyright Fix a typo in name of company in copyright comment. Signed-off-by: Krzysztof Kozlowski <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 0e50e92669357e4702fcd6a85e2f0d6e92295664 Author: Lee Jones <[email protected]> Date: Tue Nov 11 12:36:46 2014 +0000 mfd: axp20x: Constify axp20x_acpi_match and rid unused warning axp20x.c:239:30: warning: ‘axp20x_acpi_match’ defined but not used [-Wunused-variable] Signed-off-by: Lee Jones <[email protected]> commit 71d679b84ce8ca3207e547488f70c259575d2f2f Author: Dmitry Eremin-Solenikov <[email protected]> Date: Mon Nov 17 18:07:42 2014 +0300 mfd: t7l66xb: prepare/unprepare clocks Change clk_enable/disable() calls to clk_prepare_enable() and clk_disable_unprepare(). Signed-off-by: Dmitry Eremin-Solenikov <[email protected]> commit 7263bd39251e6926ca7fa5591679b26577fdaccb Author: Dmitry Eremin-Solenikov <[email protected]> Date: Mon Nov 17 18:07:43 2014 +0300 mfd: tc6387xb: prepare/unprepare clocks Change clk_enable/disable() calls to clk_prepare_enable() and clk_disable_unprepare(). Signed-off-by: Dmitry Eremin-Solenikov <[email protected]> commit 21cf3318d675b6ceeb5a3ed82ffe467a2b6eaee4 Author: Laurentiu Palcu <[email protected]> Date: Fri Nov 7 14:45:14 2014 +0200 mfd: dln2: add support for USB-SPI module Signed-off-by: Laurentiu Palcu <[email protected]> commit 783f6fc4cecd770dfdb1418c7c890dbeb3bf3c91 Author: Charles Keepax <[email protected]> Date: Tue Nov 4 13:04:07 2014 +0000 mfd: wm5110: Add missing registers for AIF2 channels 3-6 When the extra 4 channels were added to AIF2 the necessary frame control registers were not given defaults and marked readable. This patch fixes this. Signed-off-by: Charles Keepax <[email protected]> commit 90f2d0f7bf069b1a2798156b7dcc8e7d1e874406 Author: Linus Walleij <[email protected]> Date: Tue Oct 28 11:06:56 2014 +0100 mfd: tc3589x: get rid of static base The TC3589x driver is now a device tree-only driver, so we want only dynamic IRQs and GPIO numbers from the tc3589x, no static assignments. Signed-off-by: Linus Walleij <[email protected]> commit 47958c5ab4035bd91f05598f76a61cd9f7f2934c Author: Charles Keepax <[email protected]> Date: Tue Nov 4 15:24:36 2014 +0000 mfd: arizona: Document HP_CTRL_1L and HP_CTRL_1R registers These registers are documented in the datasheet and used as part of the extcon driver. Expose them properly through regmap as the datasheet notes they should be treated as volatile do so. Signed-off-by: Charles Keepax <[email protected]> commit e62cace7b602b29cc9226e64dfb2c47ddfb9558e Author: Charles Keepax <[email protected]> Date: Tue Nov 4 15:26:22 2014 +0000 mfd: wm8997: Mark INTERRUPT_STATUS_2_MASK as readable Technically this register is not used on wm8997 however the regmap core requires a continuous block of IRQs. The simplest solution is just to add the register. Signed-off-by: Charles Keepax <[email protected]> commit a64ab6b4cd098f6c2ea959fe9bf1fd3f8b13b1f3 Author: Dmitry Eremin-Solenikov <[email protected]> Date: Thu Nov 6 11:52:38 2014 +0300 mfd: tc6393xb: Prepare/unprepare clocks Change clk_enable/disable() calls to clk_prepare_enable() and clk_disable_unrepapre(). Signed-off-by: Dmitry Eremin-Solenikov <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 12849b63a4e9e22fb63d0fc967726e8cdf2a19c2 Author: Lee Jones <[email protected]> Date: Mon Nov 10 12:28:36 2014 +0000 mfd: tps65090: Fix bonkers indenting strategy First spotted pointless (incorrect) indent of 'if (ret)', then double indentations of a struct attribute 'mask'. Decided to go through the whole file and make amendments instead and this is the result. Signed-off-by: Lee Jones <[email protected]> commit 1a5fb99de4850cba710d91becfa2c65653048589 Author: Dmitry Eremin-Solenikov <[email protected]> Date: Fri Oct 24 21:19:57 2014 +0400 mfd: tc6393xb: Fail ohci suspend if full state restore is required Some boards with TC6393XB chip require full state restore during system resume thanks to chip's VCC being cut off during suspend (Sharp SL-6000 tosa is one of them). Failing to do so would result in ohci Oops on resume due to internal memory contentes being changed. Fail ohci suspend on tc6393xb is full state restore is required. Recommended workaround is to unbind tmio-ohci driver before suspend and rebind it after resume. Cc: [email protected] Signed-off-by: Dmitry Eremin-Solenikov <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit bde3e706a63d5c258b3e4f5e327bcf032fb1adfe Author: Andy Shevchenko <[email protected]> Date: Mon Nov 3 19:29:23 2014 +0200 mfd: lpc_sch: Don't call mfd_remove_devices() MFD core already cares about failing registration. It will remove successfully registered devices in case of error. Thus, no need to repeatedly call mfd_remove_devices(). Fixes: 5829e9b64e65 (mfd: lpc_sch: Accomodate partial population of the MFD devices) Signed-off-by: Andy Shevchenko <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 1753b40f5c97e0d0bf2f0a562603cfc592945a5e Author: Joe Perches <[email protected]> Date: Sun Oct 26 22:25:02 2014 -0700 mfd: wm8350-core: Fix probable mask then right shift defect Precedence of & and >> is not the same and is not left to right. shift has higher precedence and should be done after the mask. Add parentheses around the mask. Signed-off-by: Joe Perches <[email protected]> Acked-by: Charles Keepax <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 7d082baa349e59ce3de6452abc05e5de6436aad4 Author: Guenter Roeck <[email protected]> Date: Thu Oct 9 09:18:38 2014 -0700 mfd: ab8500-sysctrl: Drop ab8500_restart ab8500_restart is not called from anywhere in the kernel, so drop it. Signed-off-by: Guenter Roeck <[email protected]> Acked-by: Linus Walleij <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 6bdf891a17148a1b91beb603b09c599dc98eb4fb Author: Lee Jones <[email protected]> Date: Mon Nov 3 16:12:26 2014 +0000 mfd: db8500-prcmu: Provide sane error path values Also rid superfluous gotos and label. Cc: Linus Walleij <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 51a7e02bb629498c32915881ed4fb61ef778282a Author: Pramod Gurav <[email protected]> Date: Thu Oct 30 14:51:35 2014 +0530 mfd: db8500-prcmu: Check return of devm_ioremap for error Error check around return value of devm_ioremap is missing. Add the same to avoid NULL pointer dereference. Signed-off-by: Pramod Gurav <[email protected]> Acked-by: Linus Walleij <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 1b9b46d05f887aec418b3a5f4f55abf79316fcda Author: Tony Lindgren <[email protected]> Date: Sun Nov 2 10:09:38 2014 -0800 mfd: twl4030-power: Fix regression with missing compatible flag Commit e7cd1d1eb16f ("mfd: twl4030-power: Add generic reset configuration") accidentally removed the compatible flag for "ti,twl4030-power" that should be there as documented in the binding. If "ti,twl4030-power" only the poweroff configuration is done by the driver. Fixes: e7cd1d1eb16f ("mfd: twl4030-power: Add generic reset configuration") Cc: [email protected] # v3.16+ Reported-by: "Dr. H. Nikolaus Schaller" <[email protected]> Signed-off-by: Tony Lindgren <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 5cb5d9616a47d5383a85379afa4429382ef46b38 Author: Micky Ching <[email protected]> Date: Fri Oct 10 13:58:44 2014 +0800 mfd: rtsx: Fix PM suspend for 5227 & 5249 Fix rts5227&5249 failed send buffer cmd after suspend, PM_CTRL3 should reset before send any buffer cmd after suspend. Otherwise, buffer cmd will failed, this will lead resume fail. Signed-off-by: Micky Ching <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 130dd5b039dcbab7bcb2fdce0bb3cc7347b08b29 Author: Krzysztof Kozlowski <[email protected]> Date: Tue Oct 21 13:23:16 2014 +0200 mfd/regulator: dt-bindings: max77686: Document regulators off in suspend Add information which regulators can be disabled during system suspend. Suggested-by: Javier Martinez Canillas <[email protected]> Signed-off-by: Krzysztof Kozlowski <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 6ce286f182e22837a02a368eeb49a0057b2cd5f9 Author: Javier Martinez Canillas <[email protected]> Date: Mon Oct 20 23:05:50 2014 +0200 Revert "mfd: sec-core: Prepare regulators for suspend state to reduce power-consumption" This reverts commit b7cde7078d2344073c310aa65fc2b0a845d2cb5b ("mfd: sec-core: Prepare regulators for suspend state to reduce power-consumption") Commit b7cde7078d23 called regulator_suspend_prepare() to prepare the regulators for a suspend state. But it did from the device pm suspend handler while the regulator suspend prepare function iterates over all regulators and not only the one managed by this device so it doesn't seems to be correct to call it from within a device driver. It is better to call the regulator suspend prepare/finish functions from platform code instead so this patch reverts the mentioned commit. Suggested-by: Doug Anderson <[email protected]> Signed-off-by: Javier Martinez Canillas <[email protected]> Reviewed-by: Chanwoo Choi <[email protected]> Reviewed-by: Doug Anderson <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit efa3ca414be9b930774b5c1a3190f735596f5115 Author: Krzysztof Kozlowski <[email protected]> Date: Mon Oct 20 14:34:46 2014 +0200 mfd: max77693: Map charger device to its own of_node Add a "maxim,max77693-charger" of_compatible to the mfd_cell so the MFD child device (the charger) will have its own of_node set. This will be used by the max77693 charger driver in next patches to obtain battery configuration from DTS. Signed-off-by: Krzysztof Kozlowski <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 6f467e5f0cdc3c0304bfcabcbaf56970ddea3d52 Author: Will Sheppard <[email protected]> Date: Wed Oct 15 09:38:47 2014 +0100 mfd: arizona-spi: Add lines after declarations - checkpatch catch This was found whilst running checkpatch.pl on arizona-spi. WARNING: Missing a blank line after declarations + struct arizona *arizona = spi_get_drvdata(spi); + arizona_dev_exit(arizona); Signed-off-by: Will Sheppard <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 6cbac55368324ec2a0e59e192c5b596d0f4569f7 Author: Krzysztof Kozlowski <[email protected]> Date: Fri Oct 10 10:23:53 2014 +0200 mfd: max77693: Remove unused define Remove old MAX77693_NUM_IRQ_MUIC_REGS define. Not used anywhere. Signed-off-by: Krzysztof Kozlowski <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 590b7795b3dc293a36136a4321ba59da60e5853c Author: Boris Brezillon <[email protected]> Date: Mon Oct 6 15:48:44 2014 +0200 mfd: Add documentation for atmel-hlcdc DT bindings The HLCDC IP available on some Atmel SoCs (i.e. at91sam9n12, at91sam9x5 family or sama5d3 family) exposes 2 subdevices: - a display controller (controlled by a DRM driver) - a PWM chip This patch adds documentation for atmel-hlcdc DT bindings. Signed-off-by: Boris Brezillon <[email protected]> Tested-by: Anthony Harivel <[email protected]> Tested-by: Ludovic Desroches <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 2c86e9fb7263dbca2c21a086090d32ba90129f7b Author: Boris Brezillon <[email protected]> Date: Mon Oct 6 15:48:43 2014 +0200 mfd: Add atmel-hlcdc driver The HLCDC IP available on some Atmel SoCs (i.e. at91sam9n12, at91sam9x5 family or sama5d3 family) exposes 2 subdevices: - a display controller (controlled by a DRM driver) - a PWM chip The MFD device provides a regmap and several clocks (those connected to this hardware block) to its subdevices. This way concurrent accesses to the iomem range are handled by the regmap framework, and each subdevice can safely access HLCDC registers. Signed-off-by: Boris Brezillon <[email protected]> Tested-by: Anthony Harivel <[email protected]> Tested-by: Ludovic Desroches <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 6e3f62f0793ebff3f91076490ff0fbb107939701 Author: Johan Hovold <[email protected]> Date: Fri Sep 26 12:55:33 2014 +0200 mfd: core: Fix platform-device id generation Make sure to always honour multi-function devices registered with PLATFORM_DEVID_NONE (-1) or PLATFORM_DEVID_AUTO (-2) as id base. In this case it does not make sense to append the cell id to the mfd-id base and potentially change the requested behaviour. Specifically this will allow multi-function devices to be registered with PLATFORM_DEVID_AUTO while still having non-zero cell ids. Signed-off-by: Johan Hovold <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 16b5fe2966b8dc4a474d6618d382d26933d90b24 Author: Johan Hovold <[email protected]> Date: Fri Sep 26 12:55:32 2014 +0200 HID: hid-sensor-hub: Use mfd_add_hotplug_devices() helper Use mfd_add_hotplug_devices() helper to register the subdevices. Compile-only tested. Signed-off-by: Johan Hovold <[email protected]> Acked-by: Jiri Kosina <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 1ab589c72ef66f5f281d658ab606e02d661031d8 Author: Johan Hovold <[email protected]> Date: Fri Sep 26 12:55:31 2014 +0200 mfd: Use mfd_add_hotplug_devices() helper Use mfd_add_hotplug_devices helper to register the subdevices. Signed-off-by: Johan Hovold <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit bdb0066df96e74a4002125467ebe459feff1ebef Author: Pankaj Dubey <[email protected]> Date: Tue Sep 30 14:05:27 2014 +0530 mfd: syscon: Decouple syscon interface from platform devices Currently a syscon entity can be only registered directly through a platform device that binds to a dedicated syscon driver. However in certain use cases it is desirable to make a device used with another driver a syscon interface provider. For example, certain SoCs (e.g. Exynos) contain system controller blocks which perform various functions such as power domain control, CPU power management, low power mode control, but in addition contain certain IP integration glue, such as various signal masks, coprocessor power control, etc. In such case, there is a need to have a dedicated driver for such system controller but also share registers with other drivers. The latter is where the syscon interface is helpful. In case of DT based platforms, this patch decouples syscon object from syscon platform driver, and allows to create syscon objects first time when it is required by calling of syscon_regmap_lookup_by APIs and keep a list of such syscon objects along with syscon provider device_nodes and regmap handles. For non-DT based platforms, this patch keeps syscon platform driver structure so that syscon can be probed and such non-DT based drivers can use syscon_regmap_lookup_by_pdev API and access regmap handles. Once all users of "syscon_regmap_lookup_by_pdev" migrated to DT based, we can completely remove platform driver of syscon, and keep only helper functions to get regmap handles. Suggested-by: Arnd Bergmann <[email protected]> Suggested-by: Tomasz Figa <[email protected]> Tested-by: Vivek Gautam <[email protected]> Tested-by: Javier Martinez Canillas <[email protected]> Signed-off-by: Pankaj Dubey <[email protected]> Reviewed-by: Arnd Bergmann <[email protected]> Tested-by: Heiko Stuebner <[email protected]> Reviewed-by: Heiko Stuebner <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit ee828d02611f325a70ef6a3c1fd2dd1eb3bc9704 Author: Jaewon Kim <[email protected]> Date: Thu Sep 18 01:40:26 2014 +0900 mfd: max77693: Update DT binding to support haptic This patch add haptic DT binding documentation and example to support haptic driver in max77693 Multifunction device. Signed-off-by: Jaewon Kim <[email protected]> Acked-by: Chanwoo Choi <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit d1bafd78fce5f07bfc9c2c8a77146f74528a469e Author: Jaewon Kim <[email protected]> Date: Thu Sep 18 01:40:25 2014 +0900 mfd: max77693: Add haptic of_compatible in mfd_cell This patch add haptic of_compatible in order to use the haptic device driver using Devicetree. Signed-off-by: Jaewon Kim <[email protected]> Acked-by: Chanwoo Choi <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit efbf49224acc8ba5ac4d7ac93b5035836aebf400 Author: Jaewon Kim <[email protected]> Date: Thu Sep 18 01:40:24 2014 +0900 mfd: max77693: Initialize haptic register map This patch add regmap_haptic initialization to use haptic register map in haptic device driver. Signed-off-by: Jaewon Kim <[email protected]> Acked-by: Chanwoo Choi <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 11d0d30093301169833aedfc130d9e4abe621be1 Author: Johannes Pointner <[email protected]> Date: Thu Sep 25 08:31:42 2014 +0200 mfd: tps65217: Add compatible string for subdevices Adds of_compatible strings to mfd_cells for sub devices of the tps65217. Signed-off-by: Johannes Pointner <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 65fa5f773196ccc88c4aae43ece9119f092c20a6 Author: Damien Lespiau <[email protected]> Date: Tue Nov 25 13:45:41 2014 +0000 drm/i915: Fix short description of intel_display_power_is_enabled() That's the version actually taking the dev_priv->power_domains lock. Signed-off-by: Damien Lespiau <[email protected]> Signed-off-by: Daniel Vetter <[email protected]> commit 07c802bd7c3951410b105356787d655e273ab537 Author: Will Deacon <[email protected]> Date: Tue Nov 25 15:26:13 2014 +0000 arm64: vmlinux.lds.S: don't discard .exit.* sections at link-time .exit.* sections may be subject to patching by the new alternatives framework and so shouldn't be discarded at link-time. Without this patch, such a section will result in the following linker error: `.exit.text' referenced in section `.altinstructions' of drivers/built-in.o: defined in discarded section `.exit.text' of drivers/built-in.o Signed-off-by: Will Deacon <[email protected]> commit af86e5974d3069bd26ebcf7c046c6e59726acaaa Author: Laura Abbott <[email protected]> Date: Fri Nov 21 21:50:42 2014 +0000 arm64: Factor out fixmap initialization from ioremap The fixmap API was originally added for arm64 for early_ioremap purposes. It can be used for other purposes too so move the initialization from ioremap to somewhere more generic. This makes it obvious where the fixmap is being set up and allows for a cleaner implementation of __set_fixmap. Reviewed-by: Kees Cook <[email protected]> Acked-by: Mark Rutland <[email protected]> Tested-by: Mark Rutland <[email protected]> Tested-by: Kees Cook <[email protected]> Signed-off-by: Laura Abbott <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit c3684fbb446501b48dec6677a6a9f61c215053de Author: Laura Abbott <[email protected]> Date: Fri Nov 21 21:50:40 2014 +0000 arm64: Move cpu_resume into the text section The function cpu_resume currently lives in the .data section. There's no reason for it to be there since we can use relative instructions without a problem. Move a few cpu_resume data structures out of the assembly file so the .data annotation can be dropped completely and cpu_resume ends up in the read only text section. Reviewed-by: Kees Cook <[email protected]> Reviewed-by: Mark Rutland <[email protected]> Reviewed-by: Lorenzo Pieralisi <[email protected]> Tested-by: Mark Rutland <[email protected]> Tested-by: Lorenzo Pieralisi <[email protected]> Tested-by: Kees Cook <[email protected]> Acked-by: Ard Biesheuvel <[email protected]> Signed-off-by: Laura Abbott <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit ac2dec5f6c27a581f8571da605d9ba04df18330d Author: Laura Abbott <[email protected]> Date: Fri Nov 21 21:50:39 2014 +0000 arm64: Switch to adrp for loading the stub vectors The hyp stub vectors are currently loaded using adr. This instruction has a +/- 1MB range for the loading address. If the alignment for sections is changed the address may be more than 1MB away, resulting in reclocation errors. Switch to using adrp for getting the address to ensure we aren't affected by the location of the __hyp_stub_vectors. Acked-by: Ard Biesheuvel <[email protected]> Acked-by: Marc Zyngier <[email protected]> Tested-by: Mark Rutland <[email protected]> Tested-by: Kees Cook <[email protected]> Signed-off-by: Laura Abbott <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit fcff588633e848aa728a4437ef96d437299ba03d Author: Laura Abbott <[email protected]> Date: Fri Nov 21 21:50:38 2014 +0000 arm64: Treat handle_arch_irq as a function pointer handle_arch_irq isn't actually text, it's just a function pointer. It doesn't need to be stored in the text section and doing so causes problesm if we ever want to make the kernel text read only. Declare handle_arch_irq as a proper function pointer stored in the data section. Reviewed-by: Kees Cook <[email protected]> Reviewed-by: Mark Rutland <[email protected]> Acked-by: Ard Biesheuvel <[email protected]> Tested-by: Mark Rutland <[email protected]> Tested-by: Kees Cook <[email protected]> Signed-off-by: Laura Abbott <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit 3eebdbe5fc7d64c7a6ef14cc5b8be518ffd563fa Author: Mark Rutland <[email protected]> Date: Tue Nov 25 13:27:43 2014 +0000 arm64: sanity checks: add ID_AA64DFR{0,1}_EL1 While we currently expect self-hosted debug support to be identical across CPUs, we don't currently sanity check this. This patch adds logging of the ID_AA64DFR{0,1}_EL1 values and associated sanity checking code. It's not clear to me whether we need to check PMUVer, TraceVer, and DebugVer, as we don't currently rely on these fields at all. Signed-off-by: Mark Rutland <[email protected]> Cc: Catalin Marinas <[email protected]> Acked-by: Will Deacon <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit efdf4211d5b103535ae22972acadf57c9fc38b30 Author: Mark Rutland <[email protected]> Date: Tue Nov 25 13:27:42 2014 +0000 arm64: sanity checks: add missing newline to print A missing newline in the WARN_TAINT_ONCE string results in ugly and somewhat difficult to read output in the case of a sanity check failure, as the next print does not appear on a new line: Unsupported CPU feature variation.Modules linked in: This patch adds the missing newline, fixing the output formatting. Signed-off-by: Mark Rutland <[email protected]> Cc: Catalin Marinas <[email protected]> Acked-by: Will Deacon <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit 9760270c36a4d2ac640ea6294f4f8634a8b27121 Author: Mark Rutland <[email protected]> Date: Tue Nov 25 13:27:41 2014 +0000 arm64: sanity checks: ignore ID_MMFR0.AuxReg It seems that Cortex-A53 r0p4 added support for AIFSR and ADFSR, and ID_MMFR0.AuxReg has been updated accordingly to report this fact. As Cortex-A53 could be paired with CPUs which do not implement these registers (e.g. all current revisions of Cortex-A57), this may trigger a sanity check failure at boot. The AuxReg value describes the availability of the ACTLR, AIFSR, and ADFSR registers, which are only of use to 32-bit guest OSs, and have IMPLEMENTATION DEFINED contents. Given the nature of these registers it is likely that KVM will need to trap accesses regardless of whether the CPUs are heterogeneous. This patch masks out the ID_MMFR0.AuxReg value from the sanity checks, preventing spurious warnings at boot time. Signed-off-by: Mark Rutland <[email protected]> Reported-by: Andre Przywara <[email protected]> Cc: Catalin Marinas <[email protected]> Acked-by: Will Deacon <[email protected]> Cc: Marc Zyngier <[email protected]> Cc: Peter Maydell <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit 1cefdaea613bcd247b2235079fcbb0ca4687542d Author: Mark Brown <[email protected]> Date: Fri Nov 21 00:36:49 2014 +0000 arm64: topology: Fix handling of multi-level cluster MPIDR-based detection The only requirement the scheduler has on cluster IDs is that they must be unique. When enumerating the topology based on MPIDR information the kernel currently generates cluster IDs by using the first level of affinity above the core ID (either level one or two depending on if the core has multiple threads) however the ARMv8 architecture allows for up to three levels of affinity. This means that an ARMv8 system may contain cores which have MPIDRs identical other than affinity level three which with current code will cause us to report multiple cores with the same identification to the scheduler in violation of its uniqueness requirement. Ensure that we do not violate the scheduler requirements on systems that uses all the affinity levels by incorporating both affinity levels two and three into the cluser ID when the cores are not threaded. While no currently known hardware uses multi-level clusters it is better to program defensively, this will help ease bringup of systems that have them and will ensure that things like distribution install media do not need to be respun to replace kernels in order to deploy such systems. In the worst case the system will work but perform suboptimally until a kernel modified to handle the new topology better is installed, in the best case this will be an adequate description of such topologies for the scheduler to perform well. Signed-off-by: Mark Brown <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit c0a01b84b1fdbd98bff5bca5b201fe73fda7e9d9 Author: Andre Przywara <[email protected]> Date: Fri Nov 14 15:54:12 2014 +0000 arm64: protect alternatives workarounds with Kconfig options Not all of the errata we have workarounds for apply necessarily to all SoCs, so people compiling a kernel for one very specific SoC may not need to patch the kernel. Introduce a new submenu in the "Platform selection" menu to allow people to turn off certain bugs if they are not affected. By default all of them are enabled. Normal users or distribution kernels shouldn't bother to deselect any bugs here, since the alternatives framework will take care of patching them in only if needed. Signed-off-by: Andre Przywara <[email protected]> [will: moved kconfig menu under `Kernel Features'] Signed-off-by: Will Deacon <[email protected]> commit 5afaa1fc1b320cec48affa7e6949f2493f875c12 Author: Andre Przywara <[email protected]> Date: Fri Nov 14 15:54:11 2014 +0000 arm64: add Cortex-A57 erratum 832075 workaround The ARM erratum 832075 applies to certain revisions of Cortex-A57, one of the workarounds is to change device loads into using load-aquire semantics. This is achieved using the alternatives framework. Signed-off-by: Andre Przywara <[email protected]> Signed-off-by: Will Deacon <[email protected]> commit 301bcfac42897dbd1b0b3c1be49f24654a1bc49e Author: Andre Przywara <[email protected]> Date: Fri Nov 14 15:54:10 2014 +0000 arm64: add Cortex-A53 cache errata workaround The ARM errata 819472, 826319, 827319 and 824069 define the same workaround for these hardware issues in certain Cortex-A53 parts. Use the new alternatives framework and the CPU MIDR detection to patch "cache clean" into "cache clean and invalidate" instructions if an affected CPU is detected at runtime. Signed-off-by: Andre Przywara <[email protected]> [will: add __maybe_unused to squash gcc warning] Signed-off-by: Will Deacon <[email protected]> commit 159a5e920446aed12fe373ecc3c7b3dc667091ae Author: Chanwoo Choi <[email protected]> Date: Tue Nov 18 17:59:43 2014 +0900 mfd: s2mps11: Add binding documentation for Samsung S2MPS13 PMIC This patch adds the binding documentation for Samsung S2MPS13 PMIC which is similiar with existing S2MPS14 PMIC. S2MPS13 has the different number of regulators from S2MPS14 and RTC/Clock is the same with the S2MPS14. Signed-off-by: Chanwoo Choi <[email protected]> Acked-by: Sangbeom Kim <[email protected]> Reviewed-by: Krzysztof Kozlowski <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit f928b53d749bac4514c2ed1ea4d553fa581578b5 Author: Chanwoo Choi <[email protected]> Date: Tue Nov 18 17:59:41 2014 +0900 clk: s2mps11: Add the support for S2MPS13 PMIC clock This patch adds the support for S2MPS13 PMIC clock which is same with existing S2MPS14 RTC IP. But, S2MPS13 uses all of clocks (32khz_{ap|bt|cp}). Signed-off-by: Chanwoo Choi <[email protected]> Reviewed-by: Krzysztof Kozlowski <[email protected]> Acked-by: Michael Turquette <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 76b9840b24ae049b39f1b3cf0e49f21b7c41748f Author: Chanwoo Choi <[email protected]> Date: Tue Nov 18 17:59:40 2014 +0900 regulator: s2mps11: Add support S2MPS13 regulator device This patch adds S2MPS13 regulator device to existing S2MPS11 device driver. The S2MPS13 has just different number of regulators from S2MPS14. The S2MPS13 regulator device includes LDO[1-40] and BUCK[1-10]. Signed-off-by: Chanwoo Choi <[email protected]> Acked-by: Sangbeom Kim <[email protected]> Acked-by: Mark Brown <[email protected]> Reviewed-by: Krzysztof Kozlowski <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit 3bc2ee91a470c52fb3979c23c12d43283455f10d Author: Chanwoo Choi <[email protected]> Date: Tue Nov 18 17:59:39 2014 +0900 mfd: sec-core: Add support for S2MPS13 device This patch adds the support for Samsung S2MPS13 PMIC device to the sec-core MFD driver. The S2MPS13 is very similar with existing S2MPS14 and includes PMIC/ RTC/CLOCK devices. Signed-off-by: Chanwoo Choi <[email protected]> Acked-by: Sangbeom Kim <[email protected]> Signed-off-by: Lee Jones <[email protected]> commit ce79d54ae447d65117303ca9f61ffe9dcbc2465d Author: Pantelis Antoniou <[email protected]> Date: Tue Oct 28 22:36:05 2014 +0200 spi/of: Add OF notifier handler Add OF notifier handler needed for creating/destroying spi devices according to dynamic runtime changes in the DT live tree. This code is enabled when CONFIG_OF_DYNAMIC is selected. Signed-off-by: Pantelis Antoniou <[email protected]> Signed-off-by: Grant Likely <[email protected]> Reviewed-by: Mark Brown <[email protected]> Cc: <[email protected]> commit aff5e3f89a0b07e7edf9243f913378cc27e4110d Author: Pantelis Antoniou <[email protected]> Date: Wed Oct 29 10:40:37 2014 +0200 spi/of: Create new device registration method and accessors Dynamically inserting spi device nodes requires the use of a single device registration method. Refactor the existing of_register_spi_devices() to split out the core functionality for a single device into a separate function; of_register_spi_device(). This function will be used by the OF_DYNAMIC overlay code to make live modifications to the tree. Methods to lookup a device/master using a device node are added as well, of_find_spi_master_by_node() & of_find_spi_device_by_node(). Signed-off-by: Pantelis Antoniou <[email protected]> [grant.likely] Split patch into two pieces for clarity Signed-off-by: Grant Likely <[email protected]> Reviewed-by: Mark Brown <[email protected]> Cc: <[email protected]> commit ea7513bbc04170f1cbf42953187a4d8b731c71c4 Author: Pantelis Antoniou <[email protected]> Date: Tue Oct 28 22:36:03 2014 +0200 i2c/of: Add OF_RECONFIG notifier handler CONFIG_OF_DYNAMIC enables runtime changes to the device tree which in turn may trigger addition or removal of devices from Linux. Add an OF_RECONFIG notifier handler to receive tree change events and to creating or destroy i2c devices as required. Signed-off-by: Pantelis Antoniou <[email protected]> [grant.likely: clean up #ifdefs and drop unneeded error handling] Signed-off-by: Grant Likely <[email protected]> Reviewed-by: Wolfram Sang <[email protected]> Cc: Rob Herring <[email protected]> Cc: [email protected] commit a430a3455f2c48995e06b359a82a1109a419e9ef Author: Pantelis Antoniou <[email protected]> Date: Tue Oct 28 22:36:02 2014 +0200 i2c/of: Factor out Devicetree registration code Dynamically inserting i2c client device nodes requires the use of a single device registration method. Factor out the loop body of of_i2c_register_devices() so that it can be called for individual device_nodes instead of for all the children of a node. Note: The diff of this commit looks far more complicated than it actually is due the indentation being changed for a large block of code. When viewed using the diff -w flag to ignore whitespace changes it can be seen that the change is actually quite simple. Signed-off-by: Pantelis Antoniou <[email protected]> [grant.likely: Made new function static and removed changes to header] Signed-off-by: Grant Likely <[email protected]> Reviewed-by: Wolfram Sang <[email protected]> Cc: Rob Herring <[email protected]> Cc: [email protected] commit ebf3992061db1f7b3aa093f37fb308acc74fbc82 Author: Tony Lindgren <[email protected]> Date: Mon Nov 24 11:05:06 2014 -0800 usb: musb: Use IS_ENABLED for tusb6010 This removes the ifdef clutter a bit and saves few lines. It also makes it easier to detect the remaining places where we have conditional building of code done based on if defined for things like DMA. Signed-off-by: Tony Lindgren <[email protected]> Signed-off-by: Felipe Balbi <[email protected]> commit 82c02f58ba3a1ee0a067c0f90513e826d6152ba6 Author: Tony Lindgren <[email protected]> Date: Mon Nov 24 11:05:05 2014 -0800 usb: musb: Allow multiple glue layers to be built in There's no reason any longer to keep it as a choice now that the IO access has been fixed. Signed-off-by: Tony Lindgren <[email protected]> Signed-off-by: Felipe Balbi <[email protected]> commit 8a77f05aa39be879535f22a9757e703581fa1392 Author: Tony Lindgren <[email protected]> Date: Mon Nov 24 11:05:04 2014 -0800 usb: musb: Pass fifo_mode in platform data This allows setting the correct fifo_mode when multiple MUSB glue layers are built-in. Cc: Fabio Baltieri <[email protected]> Cc: Lee Jones <[email protected]> Cc: Linus Walleij <[email protected]> Cc: Lars-Peter Clausen <[email protected]> Acked-by: Apelete Seketeli <[email protected]> Signed-off-by: Tony Lindgren <[email protected]> Signed-off-by: Felipe Balbi <[email protected]> commit d026e9c76aac3632af174cf02d5c94defa5e6026 Author: Tony Lindgren <[email protected]> Date: Mon Nov 24 11:05:03 2014 -0800 usb: musb: Change end point selection to use new IO access This allows the endpoints to work when multiple MUSB glue layers are built in. Cc: Fabio Baltieri <[email protected]> Cc: Lee Jones <[email protected]> Cc: Lars-Peter Clausen <[email protected]> Acked-by: Linus Walleij <[email protected]> Acked-by: Apelete Seketeli <[email protected]> Signed-off-by: Tony Lindgren <[email protected]> Signed-off-by: Felipe Balbi <[email protected]> commit 1b40fc57a517878cf4c2e16ce29cc9a066dc1064 Author: Tony Lindgren <[email protected]> Date: Mon Nov 24 11:05:02 2014 -0800 usb: musb: Change to use new IO access Change to use new IO access. This allows us to build in multiple …
- Loading branch information
