Skip to content
  1. Dec 16, 2019
  2. Dec 13, 2019
  3. Dec 12, 2019
  4. Dec 11, 2019
  5. Dec 10, 2019
  6. Dec 09, 2019
  7. Dec 06, 2019
  8. Dec 05, 2019
  9. Nov 27, 2019
  10. Nov 26, 2019
    • Masahiro Yamada's avatar
      libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h · a8de1304
      Masahiro Yamada authored
      
      
      The DTC v1.5.1 added references to (U)INT32_MAX.
      
      This is no problem for user-space programs since <stdint.h> defines
      (U)INT32_MAX along with (u)int32_t.
      
      For the kernel space, libfdt_env.h needs to be adjusted before we
      pull in the changes.
      
      In the kernel, we usually use s/u32 instead of (u)int32_t for the
      fixed-width types.
      
      Accordingly, we already have S/U32_MAX for their max values.
      So, we should not add (U)INT32_MAX to <linux/limits.h> any more.
      
      Instead, add them to the in-kernel libfdt_env.h to compile the
      latest libfdt.
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
      a8de1304
    • Michal Simek's avatar
      asm-generic: Make msi.h a mandatory include/asm header · a1b39bae
      Michal Simek authored
      
      
      msi.h is generic for all architectures except x86, which has its own
      version.  Enabling MSI by adding msi.h to every architecture's Kbuild is
      just an additional step which doesn't need to be done.
      
      Make msi.h mandatory in the asm-generic/Kbuild so we don't have to do it
      for each architecture.
      
      Suggested-by: default avatarChristoph Hellwig <hch@infradead.org>
      Link: https://lore.kernel.org/r/c991669e29a79b1a8e28c3b4b3a125801a693de8.1571983829.git.michal.simek@xilinx.com
      
      
      Tested-by: Paul Walmsley <paul.walmsley@sifive.com> # build only, rv32/rv64
      Signed-off-by: default avatarMichal Simek <michal.simek@xilinx.com>
      Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
      Reviewed-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Acked-by: default avatarWaiman Long <longman@redhat.com>
      Acked-by: Paul Walmsley <paul.walmsley@sifive.com> # arch/riscv
      a1b39bae
    • Eric W. Biederman's avatar
      sysctl: Remove the sysctl system call · 61a47c1a
      Eric W. Biederman authored
      
      
      This system call has been deprecated almost since it was introduced, and
      in a survey of the linux distributions I can no longer find any of them
      that enable CONFIG_SYSCTL_SYSCALL.  The only indication that I can find
      that anyone might care is that a few of the defconfigs in the kernel
      enable CONFIG_SYSCTL_SYSCALL.  However this appears in only 31 of 414
      defconfigs in the kernel, so I suspect this symbols presence is simply
      because it is harmless to include rather than because it is necessary.
      
      As there appear to be no users of the sysctl system call, remove the
      code.  As this removes one of the few uses of the internal kernel mount
      of proc I hope this allows for even more simplifications of the proc
      filesystem.
      
      Cc: Alex Smith <alex.smith@imgtec.com>
      Cc: Anders Berg <anders.berg@lsi.com>
      Cc: Apelete Seketeli <apelete@seketeli.net>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Chee Nouk Phoon <cnphoon@altera.com>
      Cc: Chris Zankel <chris@zankel.net>
      Cc: Christian Ruppert <christian.ruppert@abilis.com>
      Cc: Greg Ungerer <gerg@uclinux.org>
      Cc: Harvey Hunt <harvey.hunt@imgtec.com>
      Cc: Helge Deller <deller@gmx.de>
      Cc: Hongliang Tao <taohl@lemote.com>
      Cc: Hua Yan <yanh@lemote.com>
      Cc: Huacai Chen <chenhc@lemote.com>
      Cc: John Crispin <blogic@openwrt.org>
      Cc: Jonas Jensen <jonas.jensen@gmail.com>
      Cc: Josh Boyer <jwboyer@gmail.com>
      Cc: Jun Nie <jun.nie@linaro.org>
      Cc: Kevin Hilman <khilman@linaro.org>
      Cc: Kevin Wells <kevin.wells@nxp.com>
      Cc: Kumar Gala <galak@codeaurora.org>
      Cc: Lars-Peter Clausen <lars@metafoo.de>
      Cc: Ley Foon Tan <lftan@altera.com>
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Markos Chandras <markos.chandras@imgtec.com>
      Cc: Max Filippov <jcmvbkbc@gmail.com>
      Cc: Noam Camus <noamc@ezchip.com>
      Cc: Olof Johansson <olof@lixom.net>
      Cc: Paul Burton <paul.burton@mips.com>
      Cc: Paul Mundt <lethal@linux-sh.org>
      Cc: Phil Edworthy <phil.edworthy@renesas.com>
      Cc: Pierrick Hascoet <pierrick.hascoet@abilis.com>
      Cc: Ralf Baechle <ralf@linux-mips.org>
      Cc: Roland Stigge <stigge@antcom.de>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Scott Telford <stelford@cadence.com>
      Cc: Stephen Boyd <sboyd@codeaurora.org>
      Cc: Steven J. Hill <Steven.Hill@imgtec.com>
      Cc: Tanmay Inamdar <tinamdar@apm.com>
      Cc: Vineet Gupta <vgupta@synopsys.com>
      Cc: Wolfram Sang <w.sang@pengutronix.de>
      Acked-by: default avatarAndi Kleen <ak@linux.intel.com>
      Reviewed-by: default avatarKees Cook <keescook@chromium.org>
      Signed-off-by: default avatar"Eric W. Biederman" <ebiederm@xmission.com>
      61a47c1a
  11. Nov 25, 2019
  12. Nov 22, 2019
  13. Nov 21, 2019
    • Tony Lindgren's avatar
      ARM: dts: Fix vcsi regulator to be always-on for droid4 to prevent hangs · ddb52945
      Tony Lindgren authored
      
      
      In addition to using vcsi regulator for the display, looks like droid4 is
      using vcsi regulator to trigger off mode internally with the PMIC firmware
      when the SoC enters deeper idle states. This is configured in the Motorola
      Mapphone Linux kernel sources as "zerov_regulator".
      
      As we currently don't support off mode during idle for omap4, we must
      prevent vcsi from being disabled when the display is blanked to prevent
      the PMIC change to off mode. Otherwise the device will hang on entering
      idle when the display is blanked.
      
      Before commit 089b3f61 ("regulator: core: Let boot-on regulators be
      powered off"), the boot-on regulators never got disabled like they should
      and vcsi did not get turned off on idle.
      
      Let's fix the issue by setting vcsi to always-on for now. Later on we may
      want to claim the vcsi regulator also in the PM code if needed.
      
      Fixes: 089b3f61 ("regulator: core: Let boot-on regulators be powered off")
      Cc: Merlijn Wajer <merlijn@wizzup.org>
      Cc: Pavel Machek <pavel@ucw.cz>
      Cc: Sebastian Reichel <sre@kernel.org>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      ddb52945
  14. Nov 20, 2019
Loading