The vfat fs is required for mounting u-boot env partition which is
actually used by reMarkable post install script.
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
5b29f6e removed disabling of the mu node. Although the imx-mailbox
driver is not enabled in the zero-sugar_defconfig we want to keep
the mu node disabled for correctness.
Signed-off-by: Morten Schade Flå <morten.schade.fla@remarkable.no>
Commit 4e028df4e3 enabled rpmsg on imx legacy platform.
In order to disable the Mailbox MU driver we must disable the mu_lp node.
Signed-off-by: Morten Schade Flå <morten.schade.fla@remarkable.no>
i.MX7 has a completely different bit field layout for IOMUXC_SW_PAD_CTL
register comparing to i.MX6. The current setting for GPIO1_IO14 and
GPIO1_IO13 look like the values for i.MX6, while i.MX7 has only the
following bit fields.
[6:5] PS (Pull Select)
[4] PE (Pull Enable)
[3] HYS (Hyst. Enable)
[2] SRE (Slew Rate Enable)
[1:0] DSE (Drive Strength Enable)
Use 47k pull-up for TOUCH_INT input, disable pull for TOUCH_RESET
output, and keep other bits as the default.
While at it, update the comment for these two pins to use the name from
board schematics.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
This commit disables:
- Initial RAM filesystem and RAM disk (initramfs/initrd) support
- RAM block device support
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
This commit disables some not used by rM1 features and drivers:
- Memory Technology Device (MTD) support
- SPI support
- EEPROM support
- MOUSE support
- LED support
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
This commit disables:
- SLUB debugging support
- Miscellaneous debug code
- MMC host test driver (used during developing or testing host driver).
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Quoting CONFIG_TRIM_UNUSED_KSYMS Kconfig description:
"This option allows for unused exported symbols to be dropped from the
build. In turn, this provides the compiler more opportunities
(especially when using LTO) for optimizing the code and reducing binary
size. This might have some security advantages as well."
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Since the available RAM for rM1 is only 512M the HIGHMEM can be disabled
which should result in a slightly faster kernel.
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Converting CYTTSP5 to loadable kernel module will allow to take
advantage of potential rootfs fw (/lib/firmware/cyttsp5_fw_pid00.bin).
Nevertheless it is worth noting that the cyttsp5_loader.ko is not
automatically probed but firmware upgrade was only used during
production stage once and is not performed at daily basis.
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Currently imx6sl uses IMX SDMA together with: UART, SPI, SSI and SPDIF
peripherals which are not used in rM1.
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
The zero-gravitas-dev.config converts CFG80211 and MAC80211 to builtin while
disabling loadable module support. Additionally MEMTEST is enabled and
access to .config through /proc/config.gz is provided.
This Kconfig fragment was built by selecting differences between
zero-gravitas_defconfig and zero-gravitas-dev_defconfig found in
https://github.com/reMarkable/linux/commits/lars/zero-gravitas_4.9
cid: 1774e2a6a0
To take advantage of additional zero-gravitas-dev.config and generate
desirable development .config use following command:
$ make zero-gravitas_defconfig zero-gravitas-dev.config
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Disabling busfreq through busfreq phandle is a leftover from a v4.9
custom approach of disabling busfreq for zero-gravitas-factory.dts. This
was done by exposing busfreq through phandle from
arch/arm/boot/dts/imx6sl.dtsi. This is not needed since the busfreq is
already disabled through kernel config.
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
The CMA description was present in Linux v4.9 but seems to get somehow
lost. Restore it since the cma area is needed e.g. by E-Ink Panel
Framebuffer used in reMarkable1.
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
This patch fixes below warnings:
arch/arm/boot/dts/zero-gravitas-factory.dts:164.20-262.4: Warning (i2c_bus_reg):
/soc/aips-bus@2100000/i2c@21a0000/pfuze100@08: I2C bus unit address
format error, expected "8"
arch/arm/boot/dts/zero-gravitas-factory.dts:345.26-351.4: Warning (i2c_bus_reg):
/soc/aips-bus@2100000/i2c@21a4000/wacom-i2c@09: I2C bus unit address
format error, expected "9"
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
This patch adds DT description for reMarkable 1.0 device.
DT taken as is from reMarkable v4.9 kernel [1]
[1] 1774e2a6a0
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
This commit fixes multiple redefinitions which prevents kernel from
compiling when CONFIG_HAVE_IMX_BUSFREQ is not enabled. This is observed
since include/linux/busfreq-imx.h provides empty stubs when
CONFIG_HAVE_IMX_BUSFREQ is not enabled, which redefined ones defined in
busfreq-imx.c.
Before this patch built failed with below:
arch/arm/mach-imx/busfreq-imx.c:183:5: error: redefinition of ‘register_busfreq_notifier’
183 | int register_busfreq_notifier(struct notifier_block *nb)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from arch/arm/mach-imx/busfreq-imx.c:23:
./include/linux/busfreq-imx.h:64:19: note: previous definition of ‘register_busfreq_notifier’ was here
64 | static inline int register_busfreq_notifier(struct notifier_block *nb)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
arch/arm/mach-imx/busfreq-imx.c:189:5: error: redefinition of ‘unregister_busfreq_notifier’
189 | int unregister_busfreq_notifier(struct notifier_block *nb)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from arch/arm/mach-imx/busfreq-imx.c:23:
./include/linux/busfreq-imx.h:68:19: note: previous definition of ‘unregister_busfreq_notifier’ was here
68 | static inline int unregister_busfreq_notifier(struct notifier_block *nb)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/arm/mach-imx/busfreq-imx.c:821:6: error: redefinition of ‘request_bus_freq’
821 | void request_bus_freq(enum bus_freq_mode mode)
| ^~~~~~~~~~~~~~~~
In file included from arch/arm/mach-imx/busfreq-imx.c:23:
./include/linux/busfreq-imx.h:58:20: note: previous definition of ‘request_bus_freq’ was here
58 | static inline void request_bus_freq(enum bus_freq_mode mode)
| ^~~~~~~~~~~~~~~~
arch/arm/mach-imx/busfreq-imx.c:870:6: error: redefinition of ‘release_bus_freq’
870 | void release_bus_freq(enum bus_freq_mode mode)
| ^~~~~~~~~~~~~~~~
In file included from arch/arm/mach-imx/busfreq-imx.c:23:
./include/linux/busfreq-imx.h:61:20: note: previous definition of ‘release_bus_freq’ was here
61 | static inline void release_bus_freq(enum bus_freq_mode mode)
| ^~~~~~~~~~~~~~~~
arch/arm/mach-imx/busfreq-imx.c:946:5: error: redefinition of ‘get_bus_freq_mode’
946 | int get_bus_freq_mode(void)
| ^~~~~~~~~~~~~~~~~
In file included from arch/arm/mach-imx/busfreq-imx.c:23:
./include/linux/busfreq-imx.h:72:19: note: previous definition of ‘get_bus_freq_mode’ was here
72 | static inline int get_bus_freq_mode(void)
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
This change was generated with 'make zero-gravitas_defconfig',
'savedefconfig' and finally arch/arm/configs/zero-gravitas_defconfig was
overwritten by just generated defconfig.
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
This patch adds default defconfig for reMarkable 1.0 device. Defconfig
taken as is from reMarkable v4.9 kernel [1].
[1] 1774e2a6a0
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
On 5.4 kernel, regulatory database is loaded from firmware file
regulatory.db. Right now, the database loading fails like below.
That's because rootfs accommodating the firmware is not ready yet when
cfg80211 starts running.
[ 7.218726] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 7.229948] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 7.236647] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 7.245333] cfg80211: failed to load regulatory.db
[ 7.262905] EXT4-fs (mmcblk2p2): mounted filesystem with ordered data mode. Opts: (null)
[ 7.271183] ext4 filesystem being mounted at /root supports timestamps until 2038 (0x7fffffff)
[ 7.279881] VFS: Mounted root (ext4 filesystem) on device 179:2.
Build cfg80211 (and mac80211) as module, so that when it gets loaded
from rootfs, regulatory.db is ready to be requested as a firmware.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
We do not have bcmdhd driver available currently, so it's not possible
to run WiFi calibration. Drop the defconfig file.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
We do not have bcmdhd driver available currently, so it's not possible
to run WiFi calibration. Drop the DTS file.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
To take advantage of IMX cpufreq support the IMX On-Chip OTP
(CONFIG_NVMEM_IMX_OCOTP) has to be enabled as well. Otherwise the IMX
cpufreq driver will not probe successfully.
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
The system currently warns if the config conditions for
building return_address in arch/arm/kernel/return_address.c
are not met, leaving just an EXPORT_SYMBOL_GPL(return_address)
of a function defined to be 'static linline'.
This is a result of aeea3592a1 ("ARM: 8158/1: LLVMLinux: use static inline in ARM ftrace.h").
Since we're not going to build anything other than an exported
symbol for something that is already being defined to be an
inline-able return of NULL, just avoid building the code to
remove the following warning:
MODPOST vmlinux.o
WARNING: "return_address" [vmlinux] is a static EXPORT_SYMBOL_GPL
Fixes: aeea3592a1 ("ARM: 8158/1: LLVMLinux: use static inline in ARM ftrace.h")
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
(cherry picked from commit fb033c95c94ca1ee3d16e04ebdb85d65fb55fff8 upstream)
[shawn.guo: Add missing warning message in commit log]
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
Probably because of some issue we see on early version hardware, 200mhz
pinctrl state for SDIO was disabled. Although the following access
failure is seen with DDR50 mode, both SDR50 and SDR104 mode works pretty
good on recent rM2 device.
[ 122.957669] brcmfmac: brcmf_sdiod_regrw_helper: failed to read data F1@0x08000, err: -84
[ 122.965816] brcmfmac: brcmf_chip_recognition: chip backplane type 15 is not supported
[ 122.973674] brcmfmac: brcmf_sdio_probe_attach: brcmf_chip_attach failed!
[ 122.980381] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed
[ 122.987089] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...
Add back 200mhz pinctrl state, so that AP5256 can work at SDR104 mode
and provide a much better WIFI throughput.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
The tweak configuration is done through SNVS register-set which requires
SNVC clock running.
This commit fixes "pm-imx7: LPSR: Button ON_TIME & GPIO wakeup tweaks".
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Add a dts for wifi calibration. It adds a separate dts/dtb for wifi
calibration, which works with BCMDHD wifi driver instead of BRCMFMAC.
Comparing to mainstream zero-sugar.dts, it adds 'wifi-host' property for
SDIO slot and deletes bcrmf child node from there, as the node is only
required by BRCMFMAC driver.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
[Lars: add licensing info]
Signed-off-by: Lars Ivar Miljeteig <lars.ivar.miljeteig@remarkable.no>
[Grzegorz: DT taken as is from reMarkable v4.14 kernel:
ad90c03aa7]
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
This commit fixes below warning:
arch/arm/boot/dts/zero-sugar.dts:205.26-219.4: Warning (i2c_bus_reg):
/soc/aips-bus@30800000/i2c@30a20000/wacom-i2c@09: I2C bus unit address
format error, expected "9"
Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Grzegorz Jaszczyk