linux/kernel/git/baikal/linux.git, branch boot/bt1

dt-bindings: sram: Add Baikal-T1 Boot SRAM binding

2026-08-12T22:21:23+00:00

Baikal-T1 is equipped with embedded SRAM of 64KB being accessed over the AXI interconnect. It's normally used at the SoC startup procedure to execute the system bootloader before the normal memory is initialized. Alternatively the internal SRAM can be used to automatically pre-load a bootloader code from external SPI-flash if corresponding Baikal-T1 Boot mode is enabled, But functionally the later feature isn't that useful, since SRAM is too small while the initial software can be XIP-ed right from the SPI-flash and then download the system software from any place it wants. Baikal-T1 SRAM is clocked with a dedicated AXI-clock source and can be reset by toggling the corresponding reset line. Due to the ability to serve as a target of the system startup code pre-loading SRAM is connected to the Baikal-T1 Boot Controller, which needs to be tuned in order to get a direct access to the memory. The later is implemented in the framework of the mux-controller functionality. Signed-off-by: Serge Semin

dt-bindings: mtd-physmap: Add Baikal-T1 internal ROM bindings

2026-08-12T22:21:23+00:00

Rom embedded into the Baikal-T1 SoC has been supported by the MTD Physmap ROM driver since commit b3e79e7682e0 ("mtd: physmap: Add Baikal-T1 physically mapped ROM support"). Let's make sure that the corresponding DT node is evaluated by the 'mtd-rom'-compatible DT schema. Note the subschema is defined as having two compatibles: 'baikal,bt1-int-rom' and 'mtd-rom'. The former string is listed in the enumeration for the sake of maintainability in case if some other vendor-specific MTD Physmap ROM is added. Signed-off-by: Serge Semin

dt-bindings: sram: Add "sram-controller" nodename

2026-08-12T22:21:22+00:00

In accordance with the DT-specification [1] SRAM-related node name is supposed to be "sram-controller". Update the generic SRAM bindings to permitting the nodes with such names thus to be consistent with the specification. [1] Devicetree Specification Release v0.3, 13 February 2020, p.10 Signed-off-by: Serge Semin

dt-bindings: mtd: Add "sram-controller" nodename

2026-08-12T22:21:22+00:00

In accordance with the DT-specification [1] SRAM-related node name is supposed to be "sram-controller". Update the generic MTD bindings to permitting the nodes with such names thus to be consistent with the specification. [1] Devicetree Specification Release v0.3, 13 February 2020, p.10 Signed-off-by: Serge Semin

dt-bindings: mtd: Add "rom" nodename

2026-08-12T22:21:22+00:00

Aside of "flash" and "s?ram" it's possible to have just RO-memory accessed as the Memory Technology Device. In this case the most suitable nodename would be just "rom". Signed-off-by: Serge Semin

Linux 7.0

2026-04-12T20:48:06+00:00

Merge tag 'edac_urgent_for_7.0' of git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras

2026-04-12T18:56:07+00:00

Pull EDAC fix from Borislav Petkov: - Fix the error path ordering when the driver-private descriptor allocation fails * tag 'edac_urgent_for_7.0' of git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras: EDAC/mc: Fix error path ordering in edac_mc_alloc()

Merge tag 'wq-for-7.0-rc7-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq

2026-04-12T17:42:40+00:00

Pull workqueue fix from Tejun Heo: "This is a fix for a stall which triggers on ordered workqueues when there are multiple inactive work items during workqueue property changes through sysfs, which doesn't happen that frequently. While really late, the fix is very low risk as it just repeats an operation which is already being performed: - Fix incomplete activation of multiple inactive works when unplugging a pool_workqueue, where the pending_pwqs list wasn't being updated for subsequent works" * tag 'wq-for-7.0-rc7-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq: workqueue: Add pool_workqueue to pending_pwqs list when unplugging multiple inactive works

Merge tag 'timers-urgent-2026-04-12' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

2026-04-12T17:01:55+00:00

Pull timer fixes from Thomas Gleixner: "Two fixes for the time/timers subsystem: - Invert the inverted fastpath decision in check_tick_dependency(), which prevents NOHZ full to stop the tick. That's a regression introduced in the 7.0 merge window. - Prevent a unpriviledged DoS in the clockevents code, where user space can starve the timer interrupt by arming a timerfd or posix interval timer in a tight loop with an absolute expiry time in the past. The fix turned out to be incomplete and was was amended yesterday to make it work on some 20 years old AMD machines as well. All issues with it have been confirmed to be resolved by various reporters" * tag 'timers-urgent-2026-04-12' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: clockevents: Prevent timer interrupt starvation tick/nohz: Fix inverted return value in check_tick_dependency() fast path

Merge tag 'sched-urgent-2026-04-12' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

2026-04-12T15:30:20+00:00

Pull scheduler fix from Ingo Molnar: "Fix DL server related slowdown to deferred fair tasks" * tag 'sched-urgent-2026-04-12' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: sched/deadline: Use revised wakeup rule for dl_server