{"push_id":2212287363,"size":35,"distinct_size":0,"ref":"refs/heads/caf/3.10/caf/torvalds/master","head":"d1ce8ceb8ba87034bb3c3a9c9324e77546ba8608","before":"10a7e9d849150a2879efc0b04d8a51068c9dd0c5","commits":[{"sha":"8c059a4676038967dd6efe614538c329b61e68a1","author":{"name":"Trent Piepho","email":"2714bdff3d9ab6510e80d91d1ed530895d8cf151@impinj.com"},"message":"spi: imx: Update device tree binding documentation\n\nUpdate documentation for gpio-cs and num-cs to reflect the standard SPI\nbindings.\n\nThe dma properties are optional.\n\nInclude a warning that native CS do not work in a commonly useful manner\nwith this hardware/driver, and therefor most users probably should use GPIO\nbased CS lines rather than native.\n\nCC: Mark Brown <broonie@kernel.org>\nCC: Shawn Guo <shawnguo@kernel.org>\nCC: Sascha Hauer <kernel@pengutronix.de>\nCC: Fabio Estevam <fabio.estevam@nxp.com>\nCC: Oleksij Rempel <o.rempel@pengutronix.de>\nSigned-off-by: Trent Piepho <tpiepho@impinj.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/8c059a4676038967dd6efe614538c329b61e68a1"},{"sha":"5a1314fa697fc65cefaba64cd4699bfc3e6882a6","author":{"name":"Ricardo Ribalda","email":"1d916c4e2e300e3102d4ef191eab8464e77b0533@gmail.com"},"message":"spi: xilinx: Detect stall with Unknown commands\n\nWhen the core is configured in C_SPI_MODE > 0, it integrates a\nlookup table that automatically configures the core in dual or quad mode\nbased on the command (first byte on the tx fifo).\n\nUnfortunately, that list mode_?_memoy_*.mif does not contain all the\nsupported commands by the flash.\n\nSince 4.14 spi-nor automatically tries to probe the flash using SFDP\n(command 0x5a), and that command is not part of the list_mode table.\n\nWhit the right combination of C_SPI_MODE and C_SPI_MEMORY this leads\ninto a stall that can only be recovered with a soft rest.\n\nThis patch detects this kind of stall and returns -EIO to the caller on\nthose commands. spi-nor can handle this error properly:\n\nm25p80 spi0.0: Detected stall. Check C_SPI_MODE and C_SPI_MEMORY. 0x21 0x2404\nm25p80 spi0.0: SPI transfer failed: -5\nspi_master spi0: failed to transfer one message from queue\nm25p80 spi0.0: s25sl064p (8192 Kbytes)\n\nSigned-off-by: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/5a1314fa697fc65cefaba64cd4699bfc3e6882a6"},{"sha":"251c201bf4f8b5bf4f1ccb4f8920eed2e1f57580","author":{"name":"Maxime Chevallier","email":"366b7ba31324f21eb0a1756e51570597569e6539@smile.fr"},"message":"spi: a3700: Fix clk prescaling for coefficient over 15\n\nThe Armada 3700 SPI controller has 2 ranges of prescaler coefficients.\nOne ranging from 0 to 15 by steps of 1, and one ranging from 0 to 30 by\nsteps of 2.\n\nThis commit fixes the prescaler coefficients that are over 15 so that it\nuses the correct range of values. The prescaling coefficient is rounded\nto the upper value if it is odd.\n\nThis was tested on Espressobin with spidev and a locigal analyser.\n\nSigned-off-by: Maxime Chevallier <maxime.chevallier@smile.fr>\nSigned-off-by: Mark Brown <broonie@kernel.org>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/251c201bf4f8b5bf4f1ccb4f8920eed2e1f57580"},{"sha":"15d8374874ded0bec37ef27f8301a6d54032c0e5","author":{"name":"Jon Hunter","email":"925569c19579fc17f544da241082fdab4c0bda17@nvidia.com"},"message":"mfd: cros ec: spi: Don't send first message too soon\n\nOn the Tegra124 Nyan-Big chromebook the very first SPI message sent to\nthe EC is failing.\n\nThe Tegra SPI driver configures the SPI chip-selects to be active-high\nby default (and always has for many years). The EC SPI requires an\nactive-low chip-select and so the Tegra chip-select is reconfigured to\nbe active-low when the EC SPI driver calls spi_setup(). The problem is\nthat if the first SPI message to the EC is sent too soon after\nreconfiguring the SPI chip-select, it fails.\n\nThe EC SPI driver prevents back-to-back SPI messages being sent too\nsoon by keeping track of the time the last transfer was sent via the\nvariable 'last_transfer_ns'. To prevent the very first transfer being\nsent too soon, initialise the 'last_transfer_ns' variable after calling\nspi_setup() and before sending the first SPI message.\n\nCc: <stable@vger.kernel.org>\nSigned-off-by: Jon Hunter <jonathanh@nvidia.com>\nReviewed-by: Brian Norris <briannorris@chromium.org>\nReviewed-by: Douglas Anderson <dianders@chromium.org>\nAcked-by: Benson Leung <bleung@chromium.org>\nSigned-off-by: Lee Jones <lee.jones@linaro.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/15d8374874ded0bec37ef27f8301a6d54032c0e5"},{"sha":"0a423772de2f3d7b00899987884f62f63ae00dcb","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"mfd: twl4030-audio: Fix sibling-node lookup\n\nA helper purported to look up a child node based on its name was using\nthe wrong of-helper and ended up prematurely freeing the parent of-node\nwhile leaking any matching node.\n\nTo make things worse, any matching node would not even necessarily be a\nchild node as the whole device tree was searched depth-first starting at\nthe parent.\n\nFixes: 019a7e6b7b31 (\"mfd: twl4030-audio: Add DT support\")\nCc: stable <stable@vger.kernel.org>     # 3.7\nSigned-off-by: Johan Hovold <johan@kernel.org>\nAcked-by: Peter Ujfalusi <peter.ujfalusi@ti.com>\nSigned-off-by: Lee Jones <lee.jones@linaro.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/0a423772de2f3d7b00899987884f62f63ae00dcb"},{"sha":"85e9b13cbb130a3209f21bd7933933399c389ffe","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"mfd: twl6040: Fix child-node lookup\n\nFix child-node lookup during probe, which ended up searching the whole\ndevice tree depth-first starting at the parent rather than just matching\non its children.\n\nTo make things worse, the parent node was prematurely freed, while the\nchild node was leaked.\n\nNote that the CONFIG_OF compile guard can be removed as\nof_get_child_by_name() provides a !CONFIG_OF implementation which always\nfails.\n\nCc: stable <stable@vger.kernel.org>     # 3.5\nFixes: 37e13cecaa14 (\"mfd: Add support for Device Tree to twl6040\")\nFixes: ca2cad6ae38e (\"mfd: Fix twl6040 build failure\")\nSigned-off-by: Johan Hovold <johan@kernel.org>\nAcked-by: Peter Ujfalusi <peter.ujfalusi@ti.com>\nSigned-off-by: Lee Jones <lee.jones@linaro.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/85e9b13cbb130a3209f21bd7933933399c389ffe"},{"sha":"001dde9400d5c3e9e2ce2abe06c1efa70a25dfde","author":{"name":"Shawn Nematbakhsh","email":"19340c910956229ab0dfee3d8dd4a42a182b5b32@chromium.org"},"message":"mfd: cros ec: spi: Fix \"in progress\" error signaling\n\nFor host commands that take a long time to process, cros ec can return\nearly by signaling a EC_RES_IN_PROGRESS result. The host must then poll\nstatus with EC_CMD_GET_COMMS_STATUS until completion of the command.\n\nNone of the above applies when data link errors are encountered. When\nerrors such as EC_SPI_PAST_END are encountered during command\ntransmission, it usually means the command was not received by the EC.\nTreating such errors as if they were 'EC_RES_IN_PROGRESS' results is\nalmost always the wrong decision, and can result in host commands\nsilently being lost.\n\nReported-by: Jon Hunter <jonathanh@nvidia.com>\nSigned-off-by: Shawn Nematbakhsh <shawnn@chromium.org>\nReviewed-by: Brian Norris <briannorris@chromium.org>\nTested-by: Jon Hunter <jonathanh@nvidia.com>\nSigned-off-by: Lee Jones <lee.jones@linaro.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/001dde9400d5c3e9e2ce2abe06c1efa70a25dfde"},{"sha":"8d26fdfcb45dc420115b267ac9d6b3ac13457f1b","author":{"name":"Geert Uytterhoeven","email":"91a5f0ac06d51a651e45b62a5b36e28880b80bc4@glider.be"},"message":"spi: Fix double \"when\"\n\nSigned-off-by: Geert Uytterhoeven <geert+renesas@glider.be>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/8d26fdfcb45dc420115b267ac9d6b3ac13457f1b"},{"sha":"b860b419d970f286294fbfb2b21a4028fd8ee442","author":{"name":"Hans de Goede","email":"a4b43a7169288183ae7c1f5a0140023a97961f48@redhat.com"},"message":"mfd: Fix RTS5227 (and others) powermanagement\n\nCommit 8275b77a1513 (\"mfd: rts5249: Add support for RTS5250S power\nsaving\") adds powersaving support for device-ids 5249 524a and 525a.\n\nBut as a side effect it breaks ASPM support for all the other device-ids,\ncausing e.g. the Haswell CPU on a Lenovo T440s to not go into a higher\nc-state then PC3, while previously it would go to PC7, causing the\nmachine to idle at 7.4W instead of 6.6W!\n\nThe problem here is the new option.dev_aspm_mode field, which only gets\nexplicitly initialized in the new code for the device-ids 5249 524a and\n525a. Leaving the dev_aspm_mode 0 for the other device-ids.\n\nThe default dev_aspm_mode 0 is mapped to DEV_ASPM_DISABLE, but the\nold behavior of calling rtsx_pci_enable_aspm() when idle and\nrtsx_pci_disable_aspm() when busy happens when dev_aspm_mode ==\nDEV_ASPM_DYNAMIC.\n\nThis commit changes the enum so that 0 = DEV_ASPM_DYNAMIC matching the\nold default behavior, fixing the pm regression with the other device-ids.\n\nFixes: 8275b77a1513 (\"mfd: rts5249: Add support for RTS5250S power saving\")\nSigned-off-by: Hans de Goede <hdegoede@redhat.com>\nAcked-by: Rui Feng <rui_feng@realsil.com.cn>\nSigned-off-by: Lee Jones <lee.jones@linaro.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/b860b419d970f286294fbfb2b21a4028fd8ee442"},{"sha":"b458a3490e46dddd5b63f59b458c9b6d2284a63f","author":{"name":"Geert Uytterhoeven","email":"91a5f0ac06d51a651e45b62a5b36e28880b80bc4@glider.be"},"message":"spi: rspi: Do not set SPCR_SPE in qspi_set_config_register()\n\nThe R-Car Gen2 Hardware User Manual Rev. 2.00 states:\n\n    If the master/slave mode select bit (MSTR) is modified while the SPI\n    function enable bit (SPE) is set to 1 (that is, this module is\n    enabled), the subsequent operation cannot be guaranteed.\n\nHence do not set SPCR_SPE when setting SPCR_MSTR, just like the\n.set_config_register() implementations for other RSPI variants do.\n\nNote that when booted from QSPI, the boot loader will have set SPCR_MSTR\nalready, hence usually the bit is never modified by the Linux driver.\n\nReported-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>\nSigned-off-by: Geert Uytterhoeven <geert+renesas@glider.be>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/b458a3490e46dddd5b63f59b458c9b6d2284a63f"},{"sha":"c810daba0ab5226084a56893a789af427a801146","author":{"name":"Takuo Koguchi","email":"53f7ec81030dc6f9a4cd73488ae05921f5af8ac5@gmail.com"},"message":"spi: sun4i: disable clocks in the remove function\n\nmclk and hclk need to be disabled. Since pm_runtime_disable does\nnot disable the clocks, use pm_runtime_force_suspend instead.\n\nFound by Linux Driver Verification project (linuxtesting.org).\n\nSigned-off-by: Takuo Koguchi <takuo.koguchi.sw@hitachi.com>\nAcked-by: Maxime Ripard <maxime.ripard@free-electrons.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/c810daba0ab5226084a56893a789af427a801146"},{"sha":"866f7ed7d67936dcdbcddc111c8af878c918fe7c","author":{"name":"Jussi Laako","email":"0e2b5885971056d0c29c9883351a05bbc3a15e6e@sonarnerd.net"},"message":"ALSA: usb-audio: Add native DSD support for Esoteric D-05X\n\nAdds VID:PID of Esoteric D-05X to the TEAC device id's.\nRenames the is_teac_50X_dac() function to is_teac_dsd_dac() to cover\nbroader device family from the same corporation sharing the same USB\naudio implementation.\n\nSigned-off-by: Jussi Laako <jussi@sonarnerd.net>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/866f7ed7d67936dcdbcddc111c8af878c918fe7c"},{"sha":"2b4584d00a6bc02b63ab3c7213060d41a74bdff1","author":{"name":"Guneshwor Singh","email":"e4b1839f6d31cda06b1f47ee40ee4a42c1d59b29@intel.com"},"message":"ALSA: hda - Add vendor id for Cannonlake HDMI codec\n\nCannonlake HDMI codec has the same nid as Geminilake. This adds the\ncodec entry for it.\n\nSigned-off-by: Guneshwor Singh <guneshwor.o.singh@intel.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/2b4584d00a6bc02b63ab3c7213060d41a74bdff1"},{"sha":"c1cfd9025cc394fd137a01159d74335c5ac978ce","author":{"name":"Takashi Iwai","email":"dd0a9a4ae370c51e6d7099900a4bf6656524e055@suse.de"},"message":"ALSA: rawmidi: Avoid racy info ioctl via ctl device\n\nThe rawmidi also allows to obtaining the information via ioctl of ctl\nAPI.  It means that user can issue an ioctl to the rawmidi device even\nwhen it's being removed as long as the control device is present.\nAlthough the code has some protection via the global register_mutex,\nits range is limited to the search of the corresponding rawmidi\nobject, and the mutex is already unlocked at accessing the rawmidi\nobject.  This may lead to a use-after-free.\n\nFor avoiding it, this patch widens the application of register_mutex\nto the whole snd_rawmidi_info_select() function.  We have another\nmutex per rawmidi object, but this operation isn't very hot path, so\nit shouldn't matter from the performance POV.\n\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/c1cfd9025cc394fd137a01159d74335c5ac978ce"},{"sha":"093b8886f446c9351c4de512cb1d4afe30e37f6f","author":{"name":"Bart Van Assche","email":"b8a13ad2fc8473e67a34a68acf4216fb1fa3477b@wdc.com"},"message":"scsi: core: Use blist_flags_t consistently\n\nUse the type blist_flags_t for all variables that represent blacklist\nflags. Additionally, suppress recently introduced sparse warnings\nrelated to blacklist flags.\n\n[mkp: fixed commit id]\n\nFixes: 5ebde4694e3b (\"scsi: Use 'blist_flags_t' for scsi_devinfo flags\")\nSigned-off-by: Bart Van Assche <bart.vanassche@wdc.com>\nReviewed-by: Christoph Hellwig <hch@lst.de>\nCc: Hannes Reinecke <hare@suse.com>\nCc: Johannes Thumshirn <jthumshirn@suse.de>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/093b8886f446c9351c4de512cb1d4afe30e37f6f"},{"sha":"5771cfffdffe709ae9b403b6f80438ca40bf850e","author":{"name":"Prasad B Munirathnam","email":"3b05666d72533b4eb15b4a9daf12414ef5dbecd6@microsemi.com"},"message":"scsi: aacraid: Fix I/O drop during reset\n\n\"FIB_CONTEXT_FLAG_TIMEDOUT\" flag is set in aac_eh_abort to indicate\ncommand timeout. Using the same flag in reset handler causes the command\nto time out and the I/Os were dropped.\n\nDefine a new flag \"FIB_CONTEXT_FLAG_EH_RESET\" to make sure I/O is\nproperly handled in eh_reset handler.\n\n[mkp: tweaked commit message]\n\nSigned-off-by: Prasad B Munirathnam <prasad.munirathnam@microsemi.com>\nReviewed-by: Raghava Aditya Renukunta <RaghavaAditya.Renukunta@microsemi.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/5771cfffdffe709ae9b403b6f80438ca40bf850e"},{"sha":"36b0cb84ee858f02c256d26f0cb4229c78e3399e","author":{"name":"Chunyan Zhang","email":"9ae80f0b28c1c31e527cbca71874baf57882c864@gmail.com"},"message":"ARM: 8731/1: Fix csum_partial_copy_from_user() stack mismatch\n\nAn additional 'ip' will be pushed to the stack, for restoring the\nDACR later, if CONFIG_CPU_SW_DOMAIN_PAN defined.\n\nHowever, the fixup still get the err_ptr by add #8*4 to sp, which\nresults in the fact that the code area pointed by the LR will be\noverwritten, or the kernel will crash if CONFIG_DEBUG_RODATA is enabled.\n\nThis patch fixes the stack mismatch.\n\nFixes: a5e090acbf54 (\"ARM: software-based priviledged-no-access support\")\nSigned-off-by: Lvqiang Huang <Lvqiang.Huang@spreadtrum.com>\nSigned-off-by: Chunyan Zhang <zhang.lyra@gmail.com>\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/36b0cb84ee858f02c256d26f0cb4229c78e3399e"},{"sha":"9226665159f0367ad08bc7d5dd194aeadb90316f","author":{"name":"Kailang Yang","email":"08a5e1a5190dd16d580b4a90f5cf0a516ee59156@realtek.com"},"message":"ALSA: hda/realtek - Fix Dell AIO LineOut issue\n\nDell AIO had LineOut jack.\nAdd LineOut verb into this patch.\n\n[ Additional notes:\n  the ALC274 codec seems requiring the fixed pin / DAC connections for\n  HP / line-out pins for enabling EQ for speakers; i.e. the HP / LO\n  pins expect to be connected with NID 0x03 while keeping the speaker\n  with NID 0x02.  However, by adding a new line-out pin, the\n  auto-parser assigns the NID 0x02 for HP/LO pins as primary outputs.\n  As an easy workaround, we provide the preferred_pairs[] to map\n  forcibly for these pins. -- tiwai ]\n\nFixes: 75ee94b20b46 (\"ALSA: hda - fix headset mic problem for Dell machines with alc274\")\nSigned-off-by: Kailang Yang <kailang@realtek.com>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/9226665159f0367ad08bc7d5dd194aeadb90316f"},{"sha":"5839ee7389e893a31e4e3c9cf17b50d14103c902","author":{"name":"Rafael J. Wysocki","email":"eb3c82195bc87396d74859a40992e20b7267b462@intel.com"},"message":"PCI / PM: Force devices to D0 in pci_pm_thaw_noirq()\n\nIt is incorrect to call pci_restore_state() for devices in low-power\nstates (D1-D3), as that involves the restoration of MSI setup which\nrequires MMIO to be operational and that is only the case in D0.\n\nHowever, pci_pm_thaw_noirq() may do that if the driver's \"freeze\"\ncallbacks put the device into a low-power state, so fix it by making\nit force devices into D0 via pci_set_power_state() instead of trying\nto \"update\" their power state which is pointless.\n\nFixes: e60514bd4485 (PCI/PM: Restore the status of PCI devices across hibernation)\nCc: 4.13+ <stable@vger.kernel.org> # 4.13+\nReported-by: Thomas Gleixner <tglx@linutronix.de>\nReported-by: Maarten Lankhorst <dev@mblankhorst.nl>\nTested-by: Thomas Gleixner <tglx@linutronix.de>\nTested-by: Maarten Lankhorst <dev@mblankhorst.nl>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nAcked-by: Bjorn Helgaas <bhelgaas@google.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/5839ee7389e893a31e4e3c9cf17b50d14103c902"},{"sha":"ccc153a6de1f7741b5ef7c996f9be133772b2092","author":{"name":"Lucas Stach","email":"18740b0c8812902fa5e7e7dee32da7993c16a6aa@pengutronix.de"},"message":"cpufreq: imx6q: fix speed grading regression on i.MX6 QuadPlus\n\nThe commit moving the speed grading check to the cpufreq driver introduced\nsome additional checks, so the OPP disable is only attempted on SoCs where\nthose OPPs are present. The compatible checks are missing the QuadPlus\ncompatible, so invalid OPPs are not correctly disabled there.\n\nMove both checks to a single condition, so we don't need to sprinkle even\nmore calls to of_machine_is_compatible().\n\nFixes: 2b3d58a3adca (cpufreq: imx6q: Move speed grading check to cpufreq driver)\nSigned-off-by: Lucas Stach <l.stach@pengutronix.de>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel_msm-3.18/commits/ccc153a6de1f7741b5ef7c996f9be133772b2092"}]}
{"actor":{"display_login":"Jackeagle"}}