All of lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Kaloz <kaloz@kernel.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] MIPS: SGI fixes
Date: Tue, 13 Oct 2026 11:45:51 +0200	[thread overview]
Message-ID: <20261013094554.16804-1-kaloz@kernel.org> (raw)

Two fixes for the SGI O2 (IP32) and a defconfig fix for the Octane
(IP30).

Patch 1 clears CRIME errors latched before the kernel starts, which
are otherwise reported as new once the error interrupts are enabled.

Patch 2 reserves the firmware memory listed by the ARC descriptors on
IP32, which now ends up in the page allocator and CMA.

Patch 3 enables the 1-wire drivers the Bridge probe needs, and the
DS1685-family RTC driver, in ip30_defconfig, and drops four lines
that savedefconfig removes.

Tested on SGI O2 and Octane machines.

Imre Kaloz (3):
  MIPS: sgi-ip32: Clear latched CRIME errors at boot
  MIPS: sgi-ip32: Reserve the firmware memory
  MIPS: SGI-IP30: fix the defconfig defaults for the Bridge PROM and RTC

 arch/mips/configs/ip30_defconfig |  9 ++++-----
 arch/mips/fw/arc/memory.c        | 11 +++++++++--
 arch/mips/include/asm/sgialib.h  |  3 +++
 arch/mips/sgi-ip32/crime.c       |  4 ++++
 arch/mips/sgi-ip32/ip32-memory.c |  3 +++
 5 files changed, 23 insertions(+), 7 deletions(-)


base-commit: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907
-- 
2.47.3


             reply	other threads:[~2026-10-13  9:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  9:45 Imre Kaloz [this message]
2026-10-13  9:45 ` [PATCH 1/3] MIPS: sgi-ip32: Clear latched CRIME errors at boot Imre Kaloz
2026-11-17 16:55   ` Thomas Bogendoerfer
2026-10-13  9:45 ` [PATCH 2/3] MIPS: sgi-ip32: Reserve the firmware memory Imre Kaloz
2026-11-17 16:56   ` Thomas Bogendoerfer
2026-10-13  9:45 ` [PATCH 3/3] MIPS: SGI-IP30: fix the defconfig defaults for the Bridge PROM and RTC Imre Kaloz
2026-11-05 15:22   ` Thomas Bogendoerfer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261013094554.16804-1-kaloz@kernel.org \
    --to=kaloz@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.