From: "David E. Garcia Porras" <david.garcia@aheadcomputing.com>
To: opensbi@lists.infradead.org
Cc: Anup Patel <anup@brainfault.org>,
Nicholas Piggin <npiggin@gmail.com>,
Himanshu Chauhan <hchauhan@ventanamicro.com>,
"David E. Garcia Porras" <david.garcia@aheadcomputing.com>
Subject: [PATCH 0/3] lib: sbi: dbtr: per-slot trigger capability detection
Date: Mon, 27 Jul 2026 12:30:38 -0600 [thread overview]
Message-ID: <20260727183041.258377-1-david.garcia@aheadcomputing.com> (raw)
Patch 1 adds an optional platform device (struct sbi_dbtr_device)
reporting whether a trigger slot supports a given configuration --
WARL fields tied off inside an implemented trigger CSR are not
discoverable via tinfo -- and makes trigger allocation
configuration-aware instead of picking the first free slot.
Patches 2 and 3 fix error return codes: sbi_dbtr_read_trig() returns
SBI_ERR_BAD_RANGE per SBI v3.0 section 19.3, and
sbi_dbtr_install_trig() returns SBI_ERR_INVALID_PARAM for an invalid
trigger configuration per section 19.4.
David E. Garcia Porras (3):
lib: sbi: dbtr: add platform device for per-slot trigger capabilities
lib: sbi: dbtr: return SBI_ERR_BAD_RANGE for invalid trigger index
range
lib: sbi: dbtr: return SBI_ERR_INVALID_PARAM for invalid trigger
configuration
include/sbi/sbi_dbtr.h | 10 ++++
lib/sbi/sbi_dbtr.c | 166 ++++++++++++++++++++++++++++++++++++++++++-------
2 files changed, 154 insertions(+), 22 deletions(-)
--
2.43.0
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
next reply other threads:[~2026-07-27 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 18:30 David E. Garcia Porras [this message]
2026-07-27 18:30 ` [PATCH 1/3] lib: sbi: dbtr: add platform device for per-slot trigger capabilities David E. Garcia Porras
2026-07-27 18:30 ` [PATCH 2/3] lib: sbi: dbtr: return SBI_ERR_BAD_RANGE for invalid trigger index range David E. Garcia Porras
2026-07-27 18:30 ` [PATCH 3/3] lib: sbi: dbtr: return SBI_ERR_INVALID_PARAM for invalid trigger configuration David E. Garcia Porras
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=20260727183041.258377-1-david.garcia@aheadcomputing.com \
--to=david.garcia@aheadcomputing.com \
--cc=anup@brainfault.org \
--cc=hchauhan@ventanamicro.com \
--cc=npiggin@gmail.com \
--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 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.