U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: <u-boot@lists.denx.de>, <git@amd.com>, Simon Glass <sjg@chromium.org>
Cc: Andrew Goodbody <andrew.goodbody@linaro.org>,
	Naman Trivedi <naman.trivedimanojbhai@amd.com>,
	Padmarao Begari <padmarao.begari@amd.com>,
	Senthil Nathan Thangaraj <senthilnathan.thangaraj@amd.com>,
	Tom Rini <trini@konsulko.com>,
	Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
Subject: [PATCH v2 0/4] reset: Introduce reset_reset.*() API
Date: Tue, 5 May 2026 14:30:28 +0200	[thread overview]
Message-ID: <cover.1777984225.git.michal.simek@amd.com> (raw)

Hi,

the patchset is adding reset_reset.*() interface which is common
in Linux. And implement it for ZynqMP.

Thanks,
Michal

Changes in v2:
- Add delay_us parameter to specify delay between assert and deassert
- Pass delay_us to rst_reset op so drivers can use it if needed
- Return -ENOSYS in stubs when !CONFIG_DM_RESET (like clk.h)
- Fix line length to stay within 80 characters
- Add reset_count field to track reset pulse operations
- Implement sandbox_reset_reset() for rst_reset op
- Add sandbox_reset_get_count() to query reset pulse count
- Clear reset_count when reset is requested
- Update tests to verify reset pulse actually happened
- Pass 10us via parameter

Michal Simek (4):
  reset: Add reset_reset() and reset_reset_bulk() API
  reset: Add sandbox tests for reset_reset() and reset_reset_bulk()
  spi: cadence: Use reset_reset_bulk() for proper reset cycling
  reset: zynqmp: Implement rst_reset using PM_RESET_ACTION_PULSE

 arch/sandbox/include/asm/reset.h   |  3 ++
 drivers/reset/reset-uclass.c       | 34 +++++++++++++++
 drivers/reset/reset-zynqmp.c       | 11 +++++
 drivers/reset/sandbox-reset-test.c | 14 +++++++
 drivers/reset/sandbox-reset.c      | 31 ++++++++++++++
 drivers/spi/cadence_qspi.c         | 16 ++-----
 include/reset-uclass.h             | 12 ++++++
 include/reset.h                    | 41 ++++++++++++++++++
 test/dm/reset.c                    | 67 ++++++++++++++++++++++++++++++
 9 files changed, 217 insertions(+), 12 deletions(-)

-- 
2.43.0

base-commit: 57460fde4ba84d67de4066ee1141e89e8139ed23

             reply	other threads:[~2026-05-05 12:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 12:30 Michal Simek [this message]
2026-05-05 12:30 ` [PATCH v2 1/4] reset: Add reset_reset() and reset_reset_bulk() API Michal Simek
2026-05-07 21:11   ` Simon Glass
2026-05-13  8:25     ` Michal Simek
2026-05-15 14:10       ` Simon Glass
2026-05-05 12:30 ` [PATCH v2 2/4] reset: Add sandbox tests for reset_reset() and reset_reset_bulk() Michal Simek
2026-05-07 21:11   ` Simon Glass
2026-05-13  8:52     ` Michal Simek
2026-05-13 14:47       ` Simon Glass
2026-05-13 15:14         ` Michal Simek
2026-05-05 12:30 ` [PATCH v2 3/4] spi: cadence: Use reset_reset_bulk() for proper reset cycling Michal Simek
2026-05-05 12:30 ` [PATCH v2 4/4] reset: zynqmp: Implement rst_reset using PM_RESET_ACTION_PULSE Michal Simek

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.1777984225.git.michal.simek@amd.com \
    --to=michal.simek@amd.com \
    --cc=andrew.goodbody@linaro.org \
    --cc=git@amd.com \
    --cc=naman.trivedimanojbhai@amd.com \
    --cc=padmarao.begari@amd.com \
    --cc=senthilnathan.thangaraj@amd.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=venkatesh.abbarapu@amd.com \
    /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