Select Git revision
Search by author
- Any Author
- authors
-
Alexander Arndt
aarndt
-
Andreas Findeklee afindeklee
-
Annette Kobou akobou
-
Armin Mück amueck
-
**** project_143_bot_c8bbc40375b18788e4765d3c396612d5
-
Daniel Ehrler dehrler
-
Devran Ölcer doelcer
-
Dieter Scheufele dscheufele
-
Dietmar Kolbus dkolbus
-
Dominik Wurster Wurster
-
Eberhard Stoll estoll
-
Florian Mayer fmayer
-
Frieder Schrempf
fschrempf
-
Julian Bauknecht jbauknecht
-
Jó Bitsch jbitsch
-
Jürgen Kling
jgkling
-
Klemenz Christof kchristof
-
Lukas Loosli lloosli
-
Marc Gonser mgonser
-
Markus Abegg mabegg
- Nov 08, 2017
-
-
Martyn Welch authored
VME Subsystem lists driver-core repository as canonical tree. Greg has stated that char-misc should be used for submissions instead[1]. [1] https://lkml.org/lkml/2017/9/1/486 Signed-off-by:
Martyn Welch <martyn.welch@collabora.co.uk> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Icenowy Zheng authored
Allwinner A64/H5 SoCs come with a SID controller like the one in H3, but without the silicon bug that makes the initial value at 0x200 wrong, so the value at 0x200 can be directly read. Add support for this kind of SID controller. Signed-off-by:
Icenowy Zheng <icenowy@aosc.io> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Signed-off-by:
-
Bryan O'Donoghue authored
This imx-ocotp driver encapsulates support for a subset of both i.MX6 and i.MX7 processors. Update the module description to reflect. Fixes: 711d4547 ("nvmem: octop: Add i.MX7D support") Signed-off-by:
Bryan O'Donoghue <pure.logic@nexus-software.ie> Signed-off-by:
-
Bryan O'Donoghue authored
After applying patches for both banked access and write timings we can re-enable the OTP write interface on i.MX7D processors. Fixes: 0642bac7 ("nvmem: imx-ocotp: add write support") Signed-off-by:
-
Bryan O'Donoghue authored
This patch adds logic to correctly setup the write timing parameters when blowing an OTP fuse for the i.MX7S/D. Fixes: 0642bac7 ("nvmem: imx-ocotp: add write support") Signed-off-by:
-
Bryan O'Donoghue authored
The i.MX7S/D has a different set of timing requirements, as a pre-cursor to adding the i.MX7 timing parameters, move the i.MX6 stuff to a dedicated function. Fixes: 0642bac7 ("nvmem: imx-ocotp: add write support") Signed-off-by:
Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by:
-
Bryan O'Donoghue authored
The i.MX7S/D takes the bank address in the CTRLn.ADDR field and the data value in one of the DATAx {0, 1, 2, 3} register fields. The current write routine is based on writing the CTRLn.ADDR field and writing a single DATA register only. Fixes: 0642bac7 ("nvmem: imx-ocotp: add write support") Signed-off-by: -
Bryan O'Donoghue authored
It will be useful in later patches to know the register access mode and bit-shift to apply to a given input offset. Fixes: 0642bac7 ("nvmem: imx-ocotp: add write support") Signed-off-by:
-
Bryan O'Donoghue authored
i.MX7S/D have a different scheme for addressing the OTP registers inside the OCOTP block. Currently it's possible to address the wrong OTP registers given the disparity between IMX6 and IMX7 OTP addressing. Since OTP programming is one-time destructive its important we restrict this interface ASAP. Fixes: 0642bac7 ("nvmem: imx-ocotp: add write support") Signed-off-by:
-
Keiji Hayashibara authored
Add eFuse driver for Socionext UniPhier series SoC. Note that eFuse device is under soc-glue and this register implements as read only. Signed-off-by:
Keiji Hayashibara <hayashibara.keiji@socionext.com> Signed-off-by:
-
Keiji Hayashibara authored
Add uniphier-efuse dt-bindings documentation. Signed-off-by:
-
Masahiro Yamada authored
All nvmem drivers are supposed to set the owner field of struct nvmem_config, but this matches nvmem->dev->driver->owner. As far as I see in drivers/nvmem/ directory, all the drivers are the case. So, make nvmem_register() set the nvmem's owner to the associated driver's owner unless nvmem_config sets otherwise. Remove .owner settings in the drivers that are now redundant. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by:
-
Masahiro Yamada authored
Fix the following sparse warnings: drivers/nvmem/qfprom.c:23:30: warning: incorrect type in initializer (different address spaces) drivers/nvmem/qfprom.c:23:30: expected void [noderef] <asn:2>*base drivers/nvmem/qfprom.c:23:30: got void *context drivers/nvmem/qfprom.c:36:30: warning: incorrect type in initializer (different address spaces) drivers/nvmem/qfprom.c:36:30: expected void [noderef] <asn:2>*base drivers/nvmem/qfprom.c:36:30: got void *context drivers/nvmem/qfprom.c:76:22: warning: incorrect type in assignment (different address spaces) drivers/nvmem/qfprom.c:76:22: expected void *static [toplevel] [assigned] priv drivers/nvmem/qfprom.c:76:22: got void [noderef] <asn:2>*[assigned] base The type of nvmem_config->priv is (void *), so sparse complains about assignment of the base address with (void __iomem *) type. Even if we cast it out, sparse still warns: warning: cast removes address space of expression Of course, we can shut up the sparse by marking __force, but a more correct way is to put the base address into driver private data. Signed-off-by:
-
Masahiro Yamada authored
Fix the following sparse warnings: drivers/nvmem/mtk-efuse.c:24:30: warning: incorrect type in initializer (different address spaces) drivers/nvmem/mtk-efuse.c:24:30: expected void [noderef] <asn:2>*base drivers/nvmem/mtk-efuse.c:24:30: got void *context drivers/nvmem/mtk-efuse.c:37:30: warning: incorrect type in initializer (different address spaces) drivers/nvmem/mtk-efuse.c:37:30: expected void [noderef] <asn:2>*base drivers/nvmem/mtk-efuse.c:37:30: got void *context drivers/nvmem/mtk-efuse.c:69:23: warning: incorrect type in assignment (different address spaces) drivers/nvmem/mtk-efuse.c:69:23: expected void *priv drivers/nvmem/mtk-efuse.c:69:23: got void [noderef] <asn:2>*[assigned] base The type of nvmem_config->priv is (void *), so sparse complains about assignment of the base address with (void __iomem *) type. Even if we cast it out, sparse still warns: warning: cast removes address space of expression Of course, we can shut up the sparse by marking __force, but a more correct way is to put the base address into driver private data. Signed-off-by:
-
Masahiro Yamada authored
nvmem_register() copies all the members of nvmem_config to nvmem_device. So, nvmem_config is one-time use data during probing. There is no point to keep it until the driver detach. Using stack should be no problem because nvmem_config is pretty small. Signed-off-by:
Sean Wang <sean.wang@mediatek.com> Signed-off-by:
-
Masahiro Yamada authored
nvmem_register() copies all the members of nvmem_config to nvmem_device. So, nvmem_config is one-time use data during probing. There is no point to keep it until the driver detach. Using stack should be no problem because nvmem_config is pretty small. Signed-off-by:
-
- Nov 06, 2017
-
-
Gustavo A. R. Silva authored
Add a ̣̣continue statement in order to avoid using a previously free'd pointer tunnel in list_add. Addresses-Coverity-ID: 1415336 Fixes: 9d3cce0b ("thunderbolt: Introduce thunderbolt bus and connection manager") Signed-off-by:
Gustavo A. R. Silva <garsilva@embeddedor.com> Acked-by:
Mika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by:
-
Mika Westerberg authored
I will be gathering Thunderbolt related patches to this git tree with help of other Thunderbolt maintainers. Signed-off-by:
-
- Nov 05, 2017
-
-
Kees Cook authored
One part of automated timer conversion tools did not take into account void * variables when searching out prior direct timer callback usage, which resulted in an attempt to dereference the timer field without a proper type. Reported-by:
kbuild test robot <fengguang.wu@intel.com> Signed-off-by:
Kees Cook <keescook@chromium.org> Signed-off-by:
-
- Nov 04, 2017
-
-
Vitaly Kuznetsov authored
Added an additional set of trace points for when channel gets notified or signals host. Suggested-by:
Stephen Hemminger <sthemmin@microsoft.com> Signed-off-by:
Vitaly Kuznetsov <vkuznets@redhat.com> Signed-off-by:
K. Y. Srinivasan <kys@microsoft.com> Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_TL_CONNECT_REQUEST sender. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_RELID_RELEASED sender. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_INITIATE_CONTACT sender. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_GPADL_TEARDOWN sender. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_GPADL_HEADER/CHANNELMSG_GPADL_BODY sender. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_CLOSECHANNEL sender. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_OPENCHANNEL sender. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_REQUESTOFFERS sender. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_VERSION_RESPONSE handler. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_GPADL_TORNDOWN handler. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_GPADL_CREATED handler. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_OPENCHANNEL_RESULT handler. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_RESCIND_CHANNELOFFER handler. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to CHANNELMSG_OFFERCHANNEL handler. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracepoint to vmbus_on_message() which is called when we start processing a blocking from work context. Signed-off-by:
-
Vitaly Kuznetsov authored
Add tracing subsystem to Hyper-V VMBus module and add tracepoint to vmbus_on_msg_dpc() which is called when we receive a message from host. Signed-off-by:
-
Kees Cook authored
In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Florian Fainelli <f.fainelli@gmail.com> Cc: bcm-kernel-feedback-list@broadcom.com Cc: David Howells <dhowells@redhat.com> Cc: Arnd Bergmann <arnd@arndb.de> Cc: linux-pcmcia@lists.infradead.org Cc: linux-arm-kernel@lists.infradead.org Signed-off-by:
Russell King <rmk+kernel@armlinux.org.uk> Signed-off-by:
-
Kees Cook authored
In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Cliff Whickman <cpw@sgi.com> Signed-off-by:
Robin Holt <robinmholt@gmail.com> Signed-off-by:
-
Kees Cook authored
In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly. Cc: Miguel Ojeda Sandonis <miguel.ojeda.sandonis@gmail.com> Signed-off-by:
Paul Burton <paul.burton@mips.com> Tested-by:
-
- Oct 31, 2017
-
-
K. Y. Srinivasan authored
Hyper-V allows the guest to report panic and the guest can pass additional information. All this is logged on the host. Currently Linux is passing back information that is not particularly useful. Make the following changes: 1. Windows uses crash MSR P0 to report bugcheck code. Follow the same convention for Linux as well. 2. It will be useful to know the gust ID of the Linux guest that has paniced. Pass back this information. These changes will help in better supporting Linux on Hyper-V Signed-off-by:
-
