mirror of
https://github.com/Fishwaldo/build.git
synced 2025-03-23 15:21:39 +00:00
e261c6f828
* Initial Mvebu RFC https://github.com/armbian/build/issues/1426
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* mvebu: add missing patches
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* mvebu: change making u-boot targets to standard way, adjust patches and config
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* helios4: set default branch to use U-Boot 2018.11
Switch over to U-Boot 2018.11 that has been used for some time in next
branch.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: Enable DEV branch
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: Add RTC support on Clearfog and Helios4
Added DM driver for mvebu RTC and enable it on Clearfog and Helios4
configuration.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* add boot-marvell.cmd backward compatibility
The patches added missing variable that used on boot-marvell.cmd and
also adjust the some memory addresses to prevent crash due to usage of
fdt_high and initrd_high.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* helios4: Added SPI NOR flash target
Build bootable SPI NOR flash image.
Change the boot order to USB -> SATA -> MMC
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Restore SPI support on U-Boot 2019.04
* mvebu: kernel: Added Wake-On-GPIO and WoL support
The patch set was missing during transition.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update
Old versions of U-Boot did not configure correctly the ODT on data
signals of DDR RAM on SolidRun's ARMADA A388 SOMs.
According to SolidRun Knowledge Base, the changes already pushed to
mainline U-Boot. But then it was overwritten when Marvell DDR Training
Tool updated
[URL]
https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* [#1429] mvebu: u-boot: Add revision id for Armada 38x B0
Added patch for SolidRun U-Boot v2018.01 and
for Helios4 U-Boot v2018.11
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* clearfog: Added SPI NOR flash target
Build bootable SPI NOR flash image.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: clearfog: DEV branch use mainline U-Boot
Also move clearfog base patch into its own board folder.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: enable U-Boot uart target
Normal MMC image can be used for uart boot using following command:
./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX
But on Helios4, the SPL failed to continue the booting process if ECC is
enabled, so disable it.
Since the usage of uart boot is more for rescue/debug, disable autoboot.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: NEXT branch use mainline U-Boot
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: fix fancontrol related bug during buster testing
- On kernel 4.19, cpu thermal sensor changed the name from
armada_thermal into f10e4078.thermal. Added this new name to udev rules
- Since DEFAULT branch now use kernel 4.14, update fancontrol
configuration
- Load lm75 kernel module
- On kernel 4.19, cpu temp reading about 20 degree C lower, update
fancontrol configuration.
[URL]
https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: Override vendor provided fancontrol unit
systemd emit following message on dmesg
systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile=
references path below legacy directory /var/run/, updating
/var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update
the unit file accordingly.
Override and change the value in the unit file to remove the message.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: DEV branch use its own u-boot patch folder
The patches are copied over from u-boot-mvebu-next
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: u-boot: Make clearfog model distinction more obvious
While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* lib: Use apt-get install instead of dpkg on install_deb_chroot()
dpkg -i does not install dependencies required by the package.
This is needed if the BSP package requires other package that is not
installed during debootstrap.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* config: mvebu: helios4: Move various tweak to family_tweak_bsp()
Various tweak in family_tweaks_s() only applied to SD card image.
Move it to family_tweaks_bsp() so it will also included on the BSP
package and applied to existing user.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* config: mvebu: helios4: Add /etc/modules to BSP
On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel
module. Pack the file into BSP so user no longer needed to modify it.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: kernel: Make zbud as built-in module
To remove the following error:
[ 1.705485] zswap: default zpool zbud not available
[ 1.705488] zswap: pool creation failed
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* bootscripts: mvebu: Add default value for spi_workaround
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452)
On kernel 4.19, armada_thermal driver has been fixed to address
Marvell's Errata #132698 (The changes first appear on LK 4.16). The
result is temperature reading is around 20 degree Celsius lower.
Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19
which is incorrect. Instead of adding some logic on what condition to
apply the tweak, it is better to remove the tweak and patch the kernel
instead.
Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in
motd")
which is part of #1421 solution.
[URL]
https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: unified fancontrol config
Since LK 4.14 on DEFAULT branch already patched and the temp reading is
same as LK 4.19 on NEXT branch, it is no longer needed to separate
fancontrol configuration file.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: helios4: Remove rev id patch
The patch is already applied in helios4 repo, no need to have it in
armbian.
This revert helios4 part of commit 7411c55
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: clearfog: enable PCIe support and PCIe reset
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: clearfog: add boot-marvell.cmd backward compatibility
The patches added missing variable that used on boot-marvell.cmd and
also adjust the some memory addresses to prevent crash due to usage of
fdt_high and initrd_high.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: tweak regarding temperature setting
Make fan speed similar compared to pre-patched armada-thermal. Target
PWM value around 70 during idle.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* config: sources: clearfog to use u-boot 2018.01 for NEXT branch
This changes also affect Helios4. Moved the shared U-Boot source setting
back to Helios4 for NEXT branch.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* config: boards: build Stretch image for Clearfog and Helios4
Also remove DEV from Helios4 CLI_TARGET
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* kernel: mvebu-next: Disable access to SPI Flash
User need to set spi_workaround=yes to enable SPI Flash access and lost
access to internal SATA.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu-next: adjust kernel config
* mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building.
* Adjust kernel config, add AUFS
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* mvebu-next: Adjust kernel config, add debug GPIO
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu-dev: separate Clearfog Base U-boot configuration file and patch
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
75 lines
2.3 KiB
Diff
75 lines
2.3 KiB
Diff
Some boards like the Turris Omnia have an RTC chip that does not get
|
|
initialized. Initializing the RTC at the driver level helps get rid of
|
|
bootloader hacks that write special register values.
|
|
|
|
--- a/drivers/rtc/rtc-armada38x.c
|
|
+++ b/drivers/rtc/rtc-armada38x.c
|
|
@@ -30,7 +30,10 @@
|
|
#define RTC_IRQ_FREQ_1HZ BIT(2)
|
|
#define RTC_CCR 0x18
|
|
#define RTC_CCR_MODE BIT(15)
|
|
+#define RTC_CCR_NORMAL_PPB 0x2000
|
|
#define RTC_CONF_TEST 0x1C
|
|
+#define RTC_TEST_CONF 0x1c
|
|
+#define RTC_TEST_CONF_MASK 0xff
|
|
#define RTC_NOMINAL_TIMING BIT(13)
|
|
|
|
#define RTC_TIME 0xC
|
|
@@ -91,6 +94,7 @@ struct armada38x_rtc_data {
|
|
void (*clear_isr)(struct armada38x_rtc *rtc);
|
|
void (*unmask_interrupt)(struct armada38x_rtc *rtc);
|
|
u32 alarm;
|
|
+ void (*init_rtc)(struct armada38x_rtc *rtc);
|
|
};
|
|
|
|
/*
|
|
@@ -202,6 +206,23 @@ static void armada38x_unmask_interrupt(s
|
|
writel(val | SOC_RTC_ALARM1_MASK, rtc->regs_soc + SOC_RTC_INTERRUPT);
|
|
}
|
|
|
|
+static void armada38x_rtc_init(struct armada38x_rtc *rtc)
|
|
+{
|
|
+ u32 reg;
|
|
+
|
|
+ /* Test RTC test configuration register bits [7:0] */
|
|
+ reg = readl(rtc->regs + RTC_TEST_CONF);
|
|
+ /* If bits [7:0] are non-zero, assume RTC was uninitialized */
|
|
+ if (reg & RTC_TEST_CONF_MASK) {
|
|
+ rtc_delayed_write(0, rtc, RTC_TEST_CONF);
|
|
+ rtc_delayed_write(0, rtc, RTC_TIME);
|
|
+ rtc_delayed_write((RTC_STATUS_ALARM1 | RTC_STATUS_ALARM2),
|
|
+ rtc, RTC_STATUS);
|
|
+ rtc_delayed_write(RTC_CCR_NORMAL_PPB, rtc, RTC_CCR);
|
|
+ }
|
|
+ return;
|
|
+}
|
|
+
|
|
static void armada8k_clear_isr(struct armada38x_rtc *rtc)
|
|
{
|
|
writel(RTC_8K_ALARM2, rtc->regs_soc + RTC_8K_ISR);
|
|
@@ -464,6 +485,7 @@ static const struct armada38x_rtc_data a
|
|
.clear_isr = armada38x_clear_isr,
|
|
.unmask_interrupt = armada38x_unmask_interrupt,
|
|
.alarm = ALARM1,
|
|
+ .init_rtc = armada38x_rtc_init,
|
|
};
|
|
|
|
static const struct armada38x_rtc_data armada8k_data = {
|
|
@@ -558,6 +580,17 @@ static __init int armada38x_rtc_probe(st
|
|
dev_err(&pdev->dev, "Failed to register RTC device: %d\n", ret);
|
|
return ret;
|
|
}
|
|
+
|
|
+ /*
|
|
+ * Try to detect if RTC is in uninitialized state.
|
|
+ * It is not definitive to know if the RTC is in an uninialized state or not,
|
|
+ * but the following call will read some bits in the RTC unit and guess if
|
|
+ * if it's in that state, and accordingly set it to sane default values.
|
|
+ */
|
|
+ if (rtc->data->init_rtc) {
|
|
+ rtc->data->init_rtc(rtc);
|
|
+ }
|
|
+
|
|
return 0;
|
|
}
|
|
|