All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@aj.id.au>
To: joel@jms.id.au
Cc: robh+dt@kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/6] ARM: dts: Enable ramoops for Rainier and Tacoma
Date: Thu, 22 Oct 2020 12:17:25 +1030	[thread overview]
Message-ID: <20201022014731.2035438-1-andrew@aj.id.au> (raw)

Hi,

We're looking to improve our crash data capture for the BMC on some IBM
platforms. This small series enables ramoops for Rainier and Tacoma.

v2 fixes an address overlap bug for Tacoma in v1, which was caused by a node vs
reg mismatch of one of the other reserved memory regions. v2 contains a several
cosmetic cleanups for both the Tacoma and Rainier reserved memory regions
before enabling ramoops in the final two patches. The geometry of the rings has
changed from v1; the slot sizes have been doubled, reducing the captured crash
count from 32 to 16 (32 seemed like overkill and we could trade that for more
space in each slot).

v1 can be found here:

https://lore.kernel.org/linux-arm-kernel/20201016043513.119841-1-andrew@aj.id.au/

Please review.

Andrew

Andrew Jeffery (6):
  ARM: dts: tacoma: Fix node vs reg mismatch for flash memory
  ARM: dts: tacoma: Zero-pad flash memory region length
  ARM: dts: rainier,tacoma: Fix size comment whitespace
  ARM: dts: rainier,tacoma: Comment reserved memory regions
  ARM: dts: rainier: Add reserved memory for ramoops
  ARM: dts: tacoma: Add reserved memory for ramoops

 arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts | 15 ++++++++++++++-
 arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts  | 19 ++++++++++++++++---
 2 files changed, 30 insertions(+), 4 deletions(-)

-- 
2.25.1


WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jeffery <andrew@aj.id.au>
To: joel@jms.id.au
Cc: devicetree@vger.kernel.org, robh+dt@kernel.org,
	linux-aspeed@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/6] ARM: dts: Enable ramoops for Rainier and Tacoma
Date: Thu, 22 Oct 2020 12:17:25 +1030	[thread overview]
Message-ID: <20201022014731.2035438-1-andrew@aj.id.au> (raw)

Hi,

We're looking to improve our crash data capture for the BMC on some IBM
platforms. This small series enables ramoops for Rainier and Tacoma.

v2 fixes an address overlap bug for Tacoma in v1, which was caused by a node vs
reg mismatch of one of the other reserved memory regions. v2 contains a several
cosmetic cleanups for both the Tacoma and Rainier reserved memory regions
before enabling ramoops in the final two patches. The geometry of the rings has
changed from v1; the slot sizes have been doubled, reducing the captured crash
count from 32 to 16 (32 seemed like overkill and we could trade that for more
space in each slot).

v1 can be found here:

https://lore.kernel.org/linux-arm-kernel/20201016043513.119841-1-andrew@aj.id.au/

Please review.

Andrew

Andrew Jeffery (6):
  ARM: dts: tacoma: Fix node vs reg mismatch for flash memory
  ARM: dts: tacoma: Zero-pad flash memory region length
  ARM: dts: rainier,tacoma: Fix size comment whitespace
  ARM: dts: rainier,tacoma: Comment reserved memory regions
  ARM: dts: rainier: Add reserved memory for ramoops
  ARM: dts: tacoma: Add reserved memory for ramoops

 arch/arm/boot/dts/aspeed-bmc-ibm-rainier.dts | 15 ++++++++++++++-
 arch/arm/boot/dts/aspeed-bmc-opp-tacoma.dts  | 19 ++++++++++++++++---
 2 files changed, 30 insertions(+), 4 deletions(-)

-- 
2.25.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-10-22  1:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22  1:47 Andrew Jeffery [this message]
2020-10-22  1:47 ` [PATCH v2 0/6] ARM: dts: Enable ramoops for Rainier and Tacoma Andrew Jeffery
2020-10-22  1:47 ` [PATCH v2 1/6] ARM: dts: tacoma: Fix node vs reg mismatch for flash memory Andrew Jeffery
2020-10-22  1:47   ` Andrew Jeffery
2020-11-19  5:16   ` Joel Stanley
2020-11-19  5:16     ` Joel Stanley
2020-10-22  1:47 ` [PATCH v2 2/6] ARM: dts: tacoma: Zero-pad flash memory region length Andrew Jeffery
2020-10-22  1:47   ` Andrew Jeffery
2020-10-22  1:47 ` [PATCH v2 3/6] ARM: dts: rainier,tacoma: Fix size comment whitespace Andrew Jeffery
2020-10-22  1:47   ` Andrew Jeffery
2020-10-22  1:47 ` [PATCH v2 4/6] ARM: dts: rainier,tacoma: Comment reserved memory regions Andrew Jeffery
2020-10-22  1:47   ` [PATCH v2 4/6] ARM: dts: rainier, tacoma: " Andrew Jeffery
2020-10-22  1:47 ` [PATCH v2 5/6] ARM: dts: rainier: Add reserved memory for ramoops Andrew Jeffery
2020-10-22  1:47   ` Andrew Jeffery
2020-11-19  5:17   ` Joel Stanley
2020-11-19  5:17     ` Joel Stanley
2020-10-22  1:47 ` [PATCH v2 6/6] ARM: dts: tacoma: " Andrew Jeffery
2020-10-22  1:47   ` Andrew Jeffery
2020-11-19  5:18   ` Joel Stanley
2020-11-19  5:18     ` Joel Stanley

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=20201022014731.2035438-1-andrew@aj.id.au \
    --to=andrew@aj.id.au \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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.