OpenSBI Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: opensbi@lists.infradead.org
Subject: [PATCH 0/5] starfive reboot cleanup & fix
Date: Wed, 31 Jan 2024 14:09:02 +0100	[thread overview]
Message-ID: <cover.1706705649.git.namcao@linutronix.de> (raw)

This series:
  - add gracefully error handling when reboot devices are not present
  - correct a device tree compatibility string
  - some minor cleanup

This series complements my other series:
http://lists.infradead.org/pipermail/opensbi/2024-January/006300.html

Nam Cao (5):
  platform: starfive: remove redundant compatibility check in pmic_ops
  platform: starfive: rename "stf,axp15060-regulator" ->
    "x-powers,axp15060"
  platform: starfive: drop "compatible" from struct pmic
  platform: starfive: return error if needed devices are not present
  platform: starfive: call starfive_jh7110_inst_init() in
    pm_reset_init()

 platform/generic/starfive/jh7110.c | 49 ++++++++++++++++--------------
 1 file changed, 27 insertions(+), 22 deletions(-)

-- 
2.39.2



             reply	other threads:[~2024-01-31 13:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 13:09 Nam Cao [this message]
2024-01-31 13:09 ` [PATCH 1/5] platform: starfive: remove redundant compatibility check in pmic_ops Nam Cao
2024-01-31 13:09 ` [PATCH 2/5] platform: starfive: rename "stf,axp15060-regulator" -> "x-powers,axp15060" Nam Cao
2024-01-31 13:09 ` [PATCH 3/5] platform: starfive: drop "compatible" from struct pmic Nam Cao
2024-01-31 13:09 ` [PATCH 4/5] platform: starfive: return error if needed devices are not present Nam Cao
2024-01-31 13:09 ` [PATCH 5/5] platform: starfive: call starfive_jh7110_inst_init() in pm_reset_init() Nam Cao
2024-02-01  3:52 ` [PATCH 0/5] starfive reboot cleanup & fix Anup Patel
2024-02-01  5:38   ` Minda Chen
2024-02-01  7:01     ` Nam Cao
2024-02-02 10:47       ` Minda Chen

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=cover.1706705649.git.namcao@linutronix.de \
    --to=namcao@linutronix.de \
    --cc=opensbi@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox