{"push_id":1303209411,"size":341,"distinct_size":341,"ref":"refs/heads/djwong-wtf","head":"96b364b3a597bb96debaece9b65c4c9a47226340","before":"339437a36029cd7573358e5d8fbe1499cf6db407","commits":[{"sha":"b46211d6dcfb81a8af66b8684a42d629183670d4","author":{"name":"Sebastian Reichel","email":"5c640c7a90bed91e410c56f3d809209f98dfc235@kernel.org"},"message":"ARM: OMAP3: hwmod data: Add sysc information for DSI\n\nAdd missing sysconfig/sysstatus information\nto OMAP3 hwmod. The information has been\nchecked against OMAP34xx and OMAP36xx TRM.\n\nWithout this change DSI block is not reset\nduring boot, which is required for working\nNokia N950 display.\n\nSigned-off-by: Sebastian Reichel <sre@kernel.org>\nCc: stable@vger.kernel.org\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/b46211d6dcfb81a8af66b8684a42d629183670d4"},{"sha":"60a5b875047e827d0f5a1a3166df714be2ef13df","author":{"name":"Dave Gerlach","email":"3e06ef4d4921cad6e94c6d4858a41ad0a7a20d1e@ti.com"},"message":"ARM: OMAP4+: hwmod: Add hwmod flag for HWMOD_OMAP4_ZERO_CLKCTRL_OFFSET\n\nNearly all modules on OMAP4 and newer platforms have clkctrl offsets\nthat are non-zero except for the RTC on am335x. Because we rely on a\nclkctrl_offset of zero to indicate no clkctrl_offset being present,\nlets add a HWMOD_OMAP4_ZERO_CLKCTRL_OFFSET flag to use to indicate\nhwmods that have a valid clkctrl_offset of 0.\n\nSigned-off-by: Dave Gerlach <d-gerlach@ti.com>\nAcked-by: Tero Kristo <t-kristo@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/60a5b875047e827d0f5a1a3166df714be2ef13df"},{"sha":"ddb0d99d53fea77c568d17265b8bca6e64f2975b","author":{"name":"Dave Gerlach","email":"3e06ef4d4921cad6e94c6d4858a41ad0a7a20d1e@ti.com"},"message":"ARM: OMAP2+: AM33XX: Add HWMOD_OMAP4_ZERO_CLKCTRL_OFFSET flag to rtc hwmod\n\nThe RTC hwmod on AM335x family of SoCs is unique in that the\nclkctrl_offs in the PRCM is 0. We rely on a clkctrl_offs of zero as\nindicating no clkctrl is present so we must flag this hwmod with\nHWMOD_OMAP4_ZERO_CLKCTRL_OFFSET to indicate the 0 clkctrl_offs is in\nfact valid in this case.\n\nSigned-off-by: Dave Gerlach <d-gerlach@ti.com>\nAcked-by: Tero Kristo <t-kristo@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/ddb0d99d53fea77c568d17265b8bca6e64f2975b"},{"sha":"428929c79cc3de7f9fefd2184da6ed625676ad9e","author":{"name":"Dave Gerlach","email":"3e06ef4d4921cad6e94c6d4858a41ad0a7a20d1e@ti.com"},"message":"ARM: OMAP4+: Have _omap4_wait_target_* check for valid clkctrl_offs\n\nPreviously the low-level CM call internal to the\n_omap4_wait_target_ready/disable calls was responsible for checking for\na valid clkctrl_offs. Now we must also consider the value of the\nprcm.omap4.flags because if HWMOD_OMAP4_ZERO_CLKCTRL_OFFSET is set in\nthe flags then clkctrl_offs of 0 is valid.\n\nLet's add this check into the _omap4_wait_target_ready/disable where we\nhave access to both the clkctrl_offs and the flags values and simply\nreturn 0 without calling the low level CM call at all, which would have\nreturned 0 anyway if the clktrl_offs was zero.\n\nSigned-off-by: Dave Gerlach <d-gerlach@ti.com>\nAcked-by: Tero Kristo <t-kristo@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/428929c79cc3de7f9fefd2184da6ed625676ad9e"},{"sha":"e4e53287701b2b8087fa107b4a965fa49505615f","author":{"name":"Dave Gerlach","email":"3e06ef4d4921cad6e94c6d4858a41ad0a7a20d1e@ti.com"},"message":"ARM: OMAP4+: CM: Remove redundant checks for clkctrl_offs of zero\n\nNow that we have moved the check for valid clkctrl_offs to the caller of\nam33xx_cm_wait_module_ready/idle and omap4_cminst_wait_module_ready/idle\nlet's remove the now redundant check for clkctrl_offs from these functions.\n\nSigned-off-by: Dave Gerlach <d-gerlach@ti.com>\nAcked-by: Tero Kristo <t-kristo@ti.com>\nSigned-off-by: Tony Lindgren <tony@atomide.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/e4e53287701b2b8087fa107b4a965fa49505615f"},{"sha":"6678716751af24af09163aef54bbabb60c12e18b","author":{"name":"Wei Yongjun","email":"dca6c8f1a6d37ffc89e9774b7b686d7557106bdd@gmail.com"},"message":"spi: qup: Remove spi_master_put in spi_qup_remove()\n\nThe call to spi_master_put() in spi_qup_remove() is redundant since\nthe master is registered using devm_spi_register_master() and no\nreference hold by using spi_master_get() in spi_qup_remove().\n\nThis is detected by Coccinelle semantic patch.\n\nSigned-off-by: Wei Yongjun <weiyj.lk@gmail.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/6678716751af24af09163aef54bbabb60c12e18b"},{"sha":"c2b08cede727387a5e19b40fa8e1a1e3a53e8527","author":{"name":"Wei Yongjun","email":"dca6c8f1a6d37ffc89e9774b7b686d7557106bdd@gmail.com"},"message":"spi: mediatek: remove spi_master_put in mtk_spi_remove()\n\nThe call to spi_master_put() in mtk_spi_remove() is redundant since\nthe master is registered using devm_spi_register_master() and no\nreference hold by using spi_master_get() in mtk_spi_remove().\n\nThis is detected by Coccinelle semantic patch.\n\nSigned-off-by: Wei Yongjun <weiyj.lk@gmail.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/c2b08cede727387a5e19b40fa8e1a1e3a53e8527"},{"sha":"2932c287108e2987454449b8214eae6db066da85","author":{"name":"Wei Yongjun","email":"dca6c8f1a6d37ffc89e9774b7b686d7557106bdd@gmail.com"},"message":"spi: img-spfi: Remove spi_master_put in img_spfi_remove()\n\nThe call to spi_master_put() in img_spfi_remove() is redundant since\nthe master is registered using devm_spi_register_master() and no\nreference hold by using spi_master_get() in img_spfi_remove().\n\nThis is detected by Coccinelle semantic patch.\n\nSigned-off-by: Wei Yongjun <weiyj.lk@gmail.com>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/2932c287108e2987454449b8214eae6db066da85"},{"sha":"b2c7f5d9c939a37c1ce7f86a642de70e3033ee9e","author":{"name":"Maarten ter Huurne","email":"aefcb2ed777a0a61706cd44aa8812552bfcc84df@treewalker.org"},"message":"regmap: cache: Fix num_reg_defaults computation from reg_defaults_raw\n\nIn 3245d460 (regmap: cache: Fall back to register by register read for\ncache defaults) non-readable registers are skipped when initializing\nreg_defaults, but are still included in num_reg_defaults. So there can\nbe uninitialized entries at the end of reg_defaults, which can cause\nproblems when the register cache initializes from the full array.\n\nFixed it by excluding non-readable registers from the count as well.\n\nSigned-off-by: Maarten ter Huurne <maarten@treewalker.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/b2c7f5d9c939a37c1ce7f86a642de70e3033ee9e"},{"sha":"1bc8da4e143c0fd8807e061a66d91d5972601ab1","author":{"name":"Lars-Peter Clausen","email":"7f698333860e9f21dcc513102ebee3bcaf8d683e@metafoo.de"},"message":"regmap: rbtree: Avoid overlapping nodes\n\nWhen searching for a suitable node that should be used for inserting a new\nregister, which does not fall within the range of any existing node, we not\nonly looks for nodes which are directly adjacent to the new register, but\nfor nodes within a certain proximity. This is done to avoid creating lots\nof small nodes with just a few registers spacing in between, which would\nincrease memory usage as well as tree traversal time.\n\nThis means there might be multiple node candidates which fall within the\nproximity range of the new register. If we choose the first node we\nencounter, under certain register insertion patterns it is possible to end\nup with overlapping ranges. This will break order in the rbtree and can\ncause the cached register value to become corrupted.\n\nE.g. take the simplified example where the proximity range is 2 and the\nregister insertion sequence is 1, 4, 2, 3, 5.\n * Insert of register 1 creates a new node, this is the root of the rbtree\n * Insert of register 4 creates a new node, which is inserted to the right\n   of the root.\n * Insert of register 2 gets inserted to the first node\n * Insert of register 3 gets inserted to the first node\n * Insert of register 5 also gets inserted into the first node since\n   this is the first node encountered and it is within the proximity range.\n   Now there are two overlapping nodes.\n\nTo avoid this always choose the node that is closest to the new register.\nThis will ensure that nodes will not overlap. The tree traversal is still\ndone as a binary search, we just don't stop at the first node found. So the\ncomplexity of the algorithm stays within the same order.\n\nIdeally if a new register is in the range of two adjacent blocks those\nblocks should be merged, but that is a much more invasive change and left\nfor later.\n\nThe issue was initially introduced in commit 472fdec7380c (\"regmap: rbtree:\nReduce number of nodes, take 2\"), but became much more exposed by commit\n6399aea629b0 (\"regmap: rbtree: When adding a reg do a bsearch for target\nnode\") which changed the order in which nodes are looked-up.\n\nFixes: 6399aea629b0 (\"regmap: rbtree: When adding a reg do a bsearch for target node\")\nSigned-off-by: Lars-Peter Clausen <lars@metafoo.de>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/1bc8da4e143c0fd8807e061a66d91d5972601ab1"},{"sha":"c3ccf357c3d75bd2924e049b6a991f7c0c111068","author":{"name":"Geert Uytterhoeven","email":"91a5f0ac06d51a651e45b62a5b36e28880b80bc4@glider.be"},"message":"spi: sh-msiof: Avoid invalid clock generator parameters\n\nThe conversion from a look-up table to a calculation for clock generator\nparameters forgot to take into account that BRDV x 1/1 is valid only if\nBRPS is x 1/1 or x 1/2, leading to undefined behavior (e.g. arbitrary\nclock rates).\n\nThis limitation is documented for the MSIOF module in all supported\nSH/R-Mobile and R-Car Gen2/Gen3 ARM SoCs.\n\nTested on r8a7791/koelsch and r8a7795/salvator-x.\n\nFixes: 65d5665bb260b034 (\"spi: sh-msiof: Update calculation of frequency dividing\")\nSigned-off-by: Geert Uytterhoeven <geert+renesas@glider.be>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/c3ccf357c3d75bd2924e049b6a991f7c0c111068"},{"sha":"290284776bb281759b11faa287b8abccaf74bfcb","author":{"name":"Stephen Boyd","email":"496892c5e989e3d4519358ac44c914f60a4d59d9@codeaurora.org"},"message":"regulator: qcom_smd: Fix voltage ranges for pm8x41\n\nThe voltage ranges listed here are wrong. The correct ranges can\nbe seen in the \"native\" spmi regulator driver\nqcom_spmi-regulator.c at pldo_ranges[], ftsmps_ranges[] and\nboost_ranges[] for the pldo, ftsmps, and boost type regulators.\nPort these ranges over to the RPM SMD regulator driver so that we\nlist the appropriate set of supported voltages on pldos.\n\nDoing this allows us to specify a voltage like 3075000 for l24,\nwhereas before that wasn't a supported voltage.\n\nFixes: da65e367b67e (\"regulator: Regulator driver for the Qualcomm RPM\")\nSigned-off-by: Stephen Boyd <sboyd@codeaurora.org>\nReviewed-by: Andy Gross <andy.gross@linaro.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/290284776bb281759b11faa287b8abccaf74bfcb"},{"sha":"c488f0071eacd10a290df4fb34bbdeb4eb8e7888","author":{"name":"Stephen Boyd","email":"496892c5e989e3d4519358ac44c914f60a4d59d9@codeaurora.org"},"message":"regulator: qcom_smd: Fix voltage ranges for pma8084 ftsmps and pldo\n\nThe voltage ranges listed here are wrong. The pma8084 pldo\nsupports three different overlapping voltage ranges with\ndiffering step sizes and the pma8084 ftsmps supports two. These\nranges can be seen in the \"native\" spmi regulator driver\n(qcom_spmi-regulator.c) at pldo_ranges[] and ftsmps_ranges[]\nrespectively. Port these ranges over to the RPM SMD regulator\ndriver so that we list the appropriate set of supported voltages\non these types of regulators.\n\nFixes: ee01d0c91ef1 (\"regulator: qcom-smd: Add support for PMA8084\")\nSigned-off-by: Stephen Boyd <sboyd@codeaurora.org>\nReviewed-by: Andy Gross <andy.gross@linaro.org>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/c488f0071eacd10a290df4fb34bbdeb4eb8e7888"},{"sha":"23540d6e2f3193b946c4de43e3f9654fa6d23fe7","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"memory: omap-gpmc: allow probe of child nodes to fail\n\nA recent commit (inadvertently?) changed how failed probe of a gpmc\nchild node was handled. Instead of proceeding with setting up any other\nchildren as before, a single error now aborts the whole process.\n\nThis change broke networking on some Overo boards due to probe failing\nfor an unrelated nand node. This second issue should obviously be\nfixed, but let's restore the old behaviour of allowing child-node\nprobe to fail to avoid further similar breakage on other systems.\n\nFixes: d2d00862dfbb (\"memory: omap-gpmc: Support general purpose input\nfor WAITPINs\")\n\nCc: stable@vger.kernel.org  # v4.7+\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Roger Quadros <rogerq@ti.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/23540d6e2f3193b946c4de43e3f9654fa6d23fe7"},{"sha":"d9fd3c918114cfd3995947339549c7341181efb0","author":{"name":"Russell King","email":"8640768d851c67eb4c0e8bfcf2aabcc8010b9372@armlinux.org.uk"},"message":"ARM: dts: armada-388-clearfog: number LAN ports properly\n\nCurrently, the ports as seen from the rear number as:\n\n\teth0 sfp lan5 lan4 lan3 lan2 lan1 lan6\n\nwhich is illogical - this came about because the rev 2.0 boards have the\nLEDs on the front for the DSA switch (lan5-1) reversed.  Rev 2.1 boards\nfixed the LED issue, and the Clearfog case numbers the lan ports\nincreasing from left to right.\n\nMaintaining this illogical numbering causes confusion, with reports that\n\"my link isn't coming up\" and \"my connection negotiates 10base-Half\"\nboth of which are due to people thinking that the port next to the SFP\nis lan1.\n\nFix this by renumbering the ports to match people's expectations.\n\n[gregory.clement@free-electrons.com: added the Fixes and stable tags]\n\nFixes: 4c945e8556ec (\"ARM: dts: Add SolidRun Armada 388 Clearfog A1 DT\nfile\")\nCc: <stable@vger.kernel.org>\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>\nReviewed-by: Andrew Lunn <andrew@lunn.ch>\nSigned-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/d9fd3c918114cfd3995947339549c7341181efb0"},{"sha":"557e37c05f28bad113d65d584699e8d8f29f70a3","author":{"name":"Peter Chen","email":"1bd50f75c460ec6fb073f71822628b73bde58ca9@nxp.com"},"message":"bus: vexpress-config: add missing of_node_put after calling of_parse_phandle\n\nof_node_put needs to be called when the device node which is got\nfrom of_parse_phandle has finished using.\n\nCc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>\nAcked-by: Liviu Dudau <liviu.dudau@arm.com>\nSigned-off-by: Peter Chen <peter.chen@nxp.com>\nSigned-off-by: Sudeep Holla <sudeep.holla@arm.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/557e37c05f28bad113d65d584699e8d8f29f70a3"},{"sha":"b079bd555f6060cd6b435a1eb58ec3b8d255ebd0","author":{"name":"Peter Chen","email":"1bd50f75c460ec6fb073f71822628b73bde58ca9@nxp.com"},"message":"firmware: arm_scpi: add missing of_node_put after calling of_parse_phandle\n\nof_node_put needs to be called when the device node which is got\nfrom of_parse_phandle has finished using it.\n\nBesides, of_address_to_resource always returns -EINVAL for error, delete\nthe assignment for ret.\n\nSigned-off-by: Peter Chen <peter.chen@nxp.com>\nSigned-off-by: Sudeep Holla <sudeep.holla@arm.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/b079bd555f6060cd6b435a1eb58ec3b8d255ebd0"},{"sha":"b9700be51bf00bbe9e1dabcb4838d6aa420192d1","author":{"name":"Andreas Färber","email":"ba9fe284894dd7813268c95c6ecd167a2b670df1@suse.de"},"message":"ARM: dts: imx6sx-sabreauto: Fix misspelled property\n\nIn commit 99fc5ba0bfb6 (\"ARM: dts: imx6sx: add i.mx6sx sabreauto board\nsupport\") it should've been enable-sdio-wakeup (not -wakup). But that is\nnow considered a legacy name for wakeup-source, so directly use the new\nname instead, as done in commit 26cefdd15db1 for the other occurrence.\n\nFixes: 26cefdd15db1 (\"ARM: dts: imx: replace legacy wakeup property with 'wakeup-source'\")\nSigned-off-by: Andreas Färber <afaerber@suse.de>\nAcked-by: Sudeep Holla <sudeep.holla@arm.com>\nSigned-off-by: Shawn Guo <shawnguo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/b9700be51bf00bbe9e1dabcb4838d6aa420192d1"},{"sha":"764f21665a12e99f03124b4c8de722cdbff92213","author":{"name":"Mark Brown","email":"bf2c7ef56f4d087c7cc4d81e9839c8674e3b6b2e@kernel.org"},"message":"spi: Drop io_mutex in error paths\n\nA couple of error paths were missing drops of io_mutex.\n\nReported-by: Julia Lawall <julia.lawall@lip6.fr>\nSigned-off-by: Mark Brown <broonie@kernel.org>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/764f21665a12e99f03124b4c8de722cdbff92213"},{"sha":"162f2db394a0efb270db3d93475ce466794a8eef","author":{"name":"Krzysztof Kozlowski","email":"fa33ff94ee78b0cc87406a1c5d4cb96cbd5b6ef8@samsung.com"},"message":"ARM: dts: exynos: Properly select eMMC HighSpeed mode on Odroid XU\n\nExynos5410 supports eMMC version 4.41 so HS200 is the top mode which\nshould be configured.  This is reflected in usage of\n\"samsung,exynos5250-dw-mshc\" compatible.  However Odroid XU DTS\ncontained also property \"mmc-hs400-1_8v\" which is parsed by MMC core\ntherefore resulting in mixed configuration.  MMC core set HS400 but\ndwmmc_exynos driver did not configure the data strobe for HS400 DDR\nmode.\n\nRemoval of HS400 properties fixes semi-random mmc errors during boot:\n  mmc_host mmc0: Bus speed (slot 0) = 400000000Hz (slot req 200000000Hz, actual 200000000HZ div = 1)\n  mmc0: mmc_select_hs400 failed, error -84\n  mmc0: error -84 whilst initialising MMC card\n\nSigned-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>\nReviewed-by: Alim Akhtar <alim.akhtar@samsung.com>","distinct":true,"url":"https://api.github.com/repos/djwong/linux/commits/162f2db394a0efb270db3d93475ce466794a8eef"}]}
{"actor":{"display_login":"djwong"}}