GitLab

Signed-off-by: Guido Günther <guido.gunther@puri.sm>

Signed-off-by: Guido Günther <guido.gunther@puri.sm>

Some devices like the Librem 5 have full hardware kill switches that cut
power to the device. Their state is indicated via gpio pin so the
drivers only purpose is to forward the current switch state to the
rfkill core.

This needs more work to go upstream.
Signed-off-by: Guido Günther <agx@sigxcpu.org>

This simplifies things when creating multiple switches.
Signed-off-by: Guido Günther <agx@sigxcpu.org>

This allows us to use them in bindings.

TODO: use types in header
Signed-off-by: Guido Günther <agx@sigxcpu.org>

Signed-off-by: Guido Günther <guido.gunther@puri.sm>

Guido Gunther authored Feb 17, 2021 and Martin Kepplinger committed Feb 18, 2021

The there was an additional alias in the specifier it hogged
line 27 instead of line 1.
Signed-off-by: Guido Günther <agx@sigxcpu.org>

sqash into Angus' ("fs: f2fs: make trace_printk's an optional compile")

This makes sure the handset speaker is on.

The codec is currently named after the chip but it should be named like
the device itself since otherwise it's impossible to distinguish from
other devices using the same codec (e.g. in alsa's UCM).
Signed-off-by: Guido Günther <agx@sigxcpu.org>

Otherwise "v4l2-ctl -d 0 --stream-mmap --stream-to=test.raw --stream-count=1"
would result in s_stream disable called twice, which makes running wrap
around to 255 and confuses the logic.

There are a few problems: vdd is shared between multiple drivers and
suspend() can be called as part of runtime_pm or system suspend.

Check before disabling regulators to avoid kernel warnings and simplify
because there is only one supply.

There are a few problems: vdd is shared between multiple drivers and
suspend() can be called as part of runtime_pm or system suspend.

Check before disabling regulators to avoid kernel warnings.

Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>

Marek Vasut authored Dec 18, 2020 and Martin Kepplinger committed Feb 15, 2021

The interrupt handling of the RS911x is particularly heavy. For each RX
packet, the card does three SDIO transactions, one to read interrupt
status register, one to RX buffer length, one to read the RX packet(s).
This translates to ~330 uS per one cycle of interrupt handler. In case
there is more incoming traffic, this will be more.

The drivers/mmc/core/sdio_irq.c has the following comment, quote "Just
like traditional hard IRQ handlers, we expect SDIO IRQ handlers to be
quick and to the point, so that the holding of the host lock does not
cover too much work that doesn't require that lock to be held."

The RS911x interrupt handler does not fit that. This patch therefore
changes it such that the entire IRQ handler is moved to the RX thread
instead, and the interrupt handler only wakes the RX thread.

This is OK, because the interrupt handler only does things which can
also be done in the RX thread, that is, it checks for firmware loading
error(s), it checks buffer status, it checks whether a packet arrived
and if so, reads out the packet and passes it to network stack.

Moreover, this change permits removal of a code which allocated an
skbuff only to get 4-byte-aligned buffer, read up to 8kiB of data
into the skbuff, queue this skbuff into local private queue, then in
RX thread, this buffer is dequeued, the data in the skbuff as passed
to the RSI driver core, and the skbuff is deallocated. All this is
replaced by directly calling the RSI driver core with local buffer.
Signed-off-by: Marek Vasut <marex@denx.de>

Angus Ainslie (Purism) authored Jul 02, 2020 and Martin Kepplinger committed Feb 15, 2021

This is not an ERR print so move it to the INFO zone
Signed-off-by: Angus Ainslie <angus@akkea.ca>

Sebastian Krzyszkowiak authored Apr 14, 2020 and Martin Kepplinger committed Feb 15, 2021

When power save mode is enabled it generates a lot of noise in dmesg.
Storing all this noise in the system journal is unlikely to be power
efficient.

Sebastian Krzyszkowiak authored Mar 04, 2020 and Martin Kepplinger committed Feb 15, 2021

This seems to fix/workaround issues with WiFi connection being dropped after
enabling power_save mode with some networks.

at least in the mainline rsi driver, this is the implemented logic.

Sebastian Krzyszkowiak authored Dec 23, 2019 and Martin Kepplinger committed Feb 15, 2021

Imported patch from Redpine, see: https://source.puri.sm/Librem5/linux-next/issues/69#note_73932

Angus Ainslie (Purism) authored Sep 25, 2019 and Martin Kepplinger committed Feb 15, 2021

Read the version number from the flash module
Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>

Angus Ainslie (Purism) authored Sep 24, 2019 and Martin Kepplinger committed Feb 15, 2021

Refer to line 2308 in
https://git.kernel.org/pub/scm/linux/kernel/git/jberg/iw.git/tree/scan.c

Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>

Angus Ainslie (Purism) authored Sep 24, 2019 and Martin Kepplinger committed Feb 15, 2021

refer to Librem5/linux-emcraft#3


for discussions of this issue.
Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>

Angus Ainslie (Purism) authored Sep 10, 2019 and Martin Kepplinger committed Feb 15, 2021

We need to rename the exported rsi_ functions so they don't conflict
with the mainline driver.
Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>

Angus Ainslie (Purism) authored Sep 10, 2019 and Martin Kepplinger committed Feb 15, 2021

Spoof low power mode as it interferes with thoughput
Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>

Angus Ainslie (Purism) authored Sep 10, 2019 and Martin Kepplinger committed Feb 15, 2021

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: Angus Ainslie (Purism) <angus@akkea.ca>

Angus Ainslie (Purism) authored Sep 10, 2019 and Martin Kepplinger committed Feb 15, 2021

Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>