- 02 Jun, 2020 36 commits
-
-
Imported patch from Redpine, see: https://source.puri.sm/Librem5/linux-next/issues/69#note_73932
-
Read the version number from the flash module Signed-off-by:Angus Ainslie (Purism) <angus@akkea.ca>
-
Refer to line 2308 in https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/tree/scan.c Signed-off-by:
-
refer to Librem5/linux-emcraft#3 for discussions of this issue. Signed-off-by:
-
We need to rename the exported rsi_ functions so they don't conflict with the mainline driver. Signed-off-by: -
Spoof low power mode as it interferes with thoughput Signed-off-by: -
To enable the diversity set the module parameter antenna_diversity=1 insmod rsi_91x.ko rsi_zone_enabled=1 dev_oper_mode=13 antenna_diversity=1 Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Signed-off-by: -
Add the Redpine driver for RS9116 module Signed-off-by: -
Allow network tools to specify MAC addresses other than the HW address for scanning. Fixes https://source.puri.sm/Librem5/linux-next/issues/157 Signed-off-by:
-
Add a module parameter to set the redpine logging level, Signed-off-by: -
The purism redpine module loads the firmware from the onboard flash Signed-off-by: -
Otherwise it breaks mipi Signed-off-by:
Guido Günther <guido.gunther@puri.sm> -
Martin Kepplinger authoredSigned-off-by:
Martin Kepplinger <martin.kepplinger@puri.sm> -
Martin Kepplinger authored
Signed-off-by:Martin Kepplinger <martin.kepplinger@puri.sm> -
This makes sure the system uses the right one.
-
Martin Kepplinger authored
Signed-off-by:Martin Kepplinger <martin.kepplinger@puri.sm> -
According to the imx8mq data sheet running VDD_GPU at 0.9V is enough when not overclocking to 1GHz (which we currently don't do). Signed-off-by:Guido Günther <agx@sigxcpu.org> -
Martin Kepplinger authored
without this, we see "failed to enable ep0out" during boot and no gadget would work. This fixes g_multi gadget functionality like the ACM serial console. Signed-off-by:Martin Kepplinger <martin.kepplinger@puri.sm> -
-
Martin Kepplinger authored
my devkit would stop with the following, exactly at the same time: [ 35.104345] PM: Adding info for No Bus:lo [ 35.327694] PM: Removing info for No Bus:lo [ 40.025566] 1v8_p: disabling [ 40.028468] 2v8_p: disabling [ 40.031406] buck1: disabling I'm not sure why. Others don't see this happening. if only buck1 is set to always-on, I get: [ 42.071568] buck2: disabling [ 42.075038] buck3: disabling and with buck1, buck2 and buck3 always-on I still get stopped at [ 42.071604] buck5: disabling and so on with buck6 ldo5 ldo6 ldo7 always on: usb xhci dies otherwise
-
Martin Kepplinger authored
cherry-picked from 47f91181
-
Need to be able to enable the camera so use a named gpio-led instead of an unnamed gpio. Signed-off-by: -
Due to current spikes during boot the USB-C VBUS can get drawn down too low causing the bq25890 to reset the board. Allow VBUS to drop a bit further to make allowance for thses spikes. see https://lore.kernel.org/linux-devicetree/20190520180712.32405-1-angus@akkea.ca/ Signed-off-by:
Eric Kuzmenko <eric.kuzmenko@puri.sm>
Signed-off-by: -
use vselect to set the io voltage to 1.8V Signed-off-by: -
Add a simple-battery with default power capacity Discharge curve comes from the panasonic NCR18650B datasheet https://www.batteryspace.com/prod-specs/NCR18650B.pdf Signed-off-by:
-
-
This otherwise confuses mesa/drm which picks the wrong output.
-
-
Somewhat based on the defconfig from Boundary Devices BSP.
-
This is a work around to ensure smooth kernel upgrades with older flash-kernel. Helps https://source.puri.sm/Librem5/linux-next/issues/25 Signed-off-by:
Guido Günther <guido.gunther@puri.sm> -
This message prints out on every dvfs transtion and fills the kernel log. Remove it. Signed-off-by: -
This supports the Librem 5 and it's devkit Signed-off-by:
Guido Günther <guido.gunther@puri.sm>
Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm> -
-
- 31 May, 2020 4 commits
-
-
Linus Torvalds authored
-
Joe Perches authored
Yes, staying withing 80 columns is certainly still _preferred_. But it's not the hard limit that the checkpatch warnings imply, and other concerns can most certainly dominate. Increase the default limit to 100 characters. Not because 100 characters is some hard limit either, but that's certainly a "what are you doing" kind of value and less likely to be about the occasional slightly longer lines. Miscellanea: - to avoid unnecessary whitespace changes in files, checkpatch will no longer emit a warning about line length when scanning files unless --strict is also used - Add a bit to coding-style about alignment to open parenthesis Signed-off-by:
-
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipLinus Torvalds authored
Pull x86 fixes from Thomas Gleixner: "A pile of x86 fixes: - Prevent a memory leak in ioperm which was caused by the stupid assumption that the exit cleanup is always called for current, which is not the case when fork fails after taking a reference on the ioperm bitmap. - Fix an arithmething overflow in the DMA code on 32bit systems - Fill gaps in the xstate copy with defaults instead of leaving them uninitialized - Revert: "Make __X32_SYSCALL_BIT be unsigned long" as it turned out that existing user space fails to build" * tag 'x86-urgent-2020-05-31' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/ioperm: Prevent a memory leak when fork fails x86/dma: Fix max PFN arithmetic overflow on 32 bit systems copy_xstate_to_kernel(): don't leave parts of destination uninitialized x86/syscalls: Revert "x86/syscalls: Make __X32_SYSCALL_BIT be unsigned long" -
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipLinus Torvalds authored
Pull scheduler fix from Thomas Gleixner: "A single scheduler fix preventing a crash in NUMA balancing. The current->mm check is not reliable as the mm might be temporary due to use_mm() in a kthread. Check for PF_KTHREAD explictly" * tag 'sched-urgent-2020-05-31' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: sched/fair: Don't NUMA balance for kthreads
-
