public inbox for linux-coco@lists.linux.dev
 help / color / mirror / Atom feed
From: Vedashree Vidwans <vvidwans@nvidia.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: salman.nabi@arm.com, andre.przywara@arm.com,
	lpieralisi@kernel.org, mark.rutland@arm.com, ardb@kernel.org,
	chao.gao@intel.com, linux-arm-kernel@lists.infradead.org,
	linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org,
	sdonthineni@nvidia.com, vsethi@nvidia.com, vwadekar@nvidia.com
Subject: Re: [RFC PATCH 0/5] Arm LFA: Improvements and interrupt support
Date: Fri, 19 Dec 2025 00:38:39 -0800	[thread overview]
Message-ID: <8bca8c4b-52b8-4a1d-9f21-176c994a58bb@nvidia.com> (raw)
In-Reply-To: <20251209-miniature-curassow-of-energy-b6a303@sudeepholla>



On 12/9/25 03:39, Sudeep Holla wrote:
> On Mon, Dec 08, 2025 at 10:13:10PM +0000, Vedashree Vidwans wrote:
>> Hello,
>>
>> The patches update the proposed Arm Live Firmware Activation (LFA)
>> kernel driver [1] to incorporate review feedback [2] and refine the
>> activation flow while remaining aligned with the LFA specification
>> DEN0147 [3] and the SMCCC 1.2 calling convention. The series keeps
>> the existing functionality but restructures and extends it to improve
>> robustness, reviewability, and future extensibility.​
>>
>> The SMCCC usage in the driver is updated to consistently use the
>> SMCCC 1.2 register-based calling convention, consolidating arguments
>> and results into a single struct to reduce stack usage and simplify
>> the SMC interface. The patches also split the original changes into
>> focused pieces and document the device node bindings in the commit
>> messages, making it easier to follow and validate the implementation
>> against the specification.​
>>
>> The kernel driver is registered as a platform driver in accordence to
>> the LFA device defined by the specification [3]. The driver now extends
>> interface for interrupt-based enablement of LFA. During LFA, the
>> interrupt
>> thread refreshes firmware component details after each activation step
>> and iterates over all activable components until no further activation
>> is pending, matching the spec’s allowance for component detail changes
>> after activation. This ensures that sysfs exposure of LFA components
>> remains consistent with the authoritative information provided by the
>> secure firmware.​
>>
>> The handling of CPU rendezvous is adjusted so that the kernel now
>> honors the rendezvous policy chosen by the firmware, instead of
>> unconditionally forcing a rendezvous. This reflects experience with
>> existing firmware deployments where mandatory rendezvous is not
>> required, while still allowing the firmware to request it when
>> needed.​
>>
>> Thank you,
>> Veda
>>
>> [1] https://lore.kernel.org/lkml/20250926123145.268728-1-salman.nabi@arm.com/
>> [2] https://lkml.org/lkml/2025/10/8/980
>> [3] https://developer.arm.com/documentation/den0147/latest/
>>
>> Vedashree Vidwans (5):
>>    firmware: smccc: LFA: use smcc 1.2
>>    firmware: smccc: LFA: refactor
>>    firmware: smccc: add timeout, touch wdt
>>    firmware: smccc: register as platform driver
>>    firmware: smccc: lfa: refresh fw details
>>
>>   drivers/firmware/smccc/Kconfig  |   3 +-
>>   drivers/firmware/smccc/lfa_fw.c | 478 +++++++++++++++++++++++++-------
> 
> Same comment as before[1], looks like the feedback got ignored or missed.
> 
> -- 
> Regards,
> Sudeep
> 
> [1]https://lore.kernel.org/all/20251009-calculating-glorious-oriole- 
> ceccf6@sudeepholla

Thank you for your comment.
I did include DT binding in commit message of the patch. Please let me 
know if there's anything else I can elaborate.

Regards,
Veda

  reply	other threads:[~2025-12-19  8:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 22:13 [RFC PATCH 0/5] Arm LFA: Improvements and interrupt support Vedashree Vidwans
2025-12-08 22:13 ` [RFC PATCH 1/5] firmware: smccc: LFA: use smcc 1.2 Vedashree Vidwans
2025-12-09 11:42   ` Sudeep Holla
2025-12-19  8:47     ` Vedashree Vidwans
2025-12-19 10:37       ` Sudeep Holla
2025-12-08 22:13 ` [RFC PATCH 2/5] firmware: smccc: LFA: refactor Vedashree Vidwans
2025-12-08 22:13 ` [RFC PATCH 3/5] firmware: smccc: add timeout, touch wdt Vedashree Vidwans
2025-12-08 22:13 ` [RFC PATCH 4/5] firmware: smccc: register as platform driver Vedashree Vidwans
2025-12-09 11:47   ` Sudeep Holla
2025-12-19  8:26     ` Vedashree Vidwans
2025-12-19 10:40       ` Sudeep Holla
2025-12-12 15:31   ` Matt Ochs
2025-12-18 21:41     ` Vedashree Vidwans
2026-01-20 14:07   ` Salman Nabi
2025-12-08 22:13 ` [RFC PATCH 5/5] firmware: smccc: lfa: refresh fw details Vedashree Vidwans
2025-12-12 15:37   ` Matt Ochs
2025-12-18 21:40     ` Vedashree Vidwans
2026-01-19 19:50   ` Salman Nabi
2025-12-09 11:39 ` [RFC PATCH 0/5] Arm LFA: Improvements and interrupt support Sudeep Holla
2025-12-19  8:38   ` Vedashree Vidwans [this message]
2025-12-19 10:32     ` Sudeep Holla
2026-01-13 17:30 ` Andre Przywara

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=8bca8c4b-52b8-4a1d-9f21-176c994a58bb@nvidia.com \
    --to=vvidwans@nvidia.com \
    --cc=andre.przywara@arm.com \
    --cc=ardb@kernel.org \
    --cc=chao.gao@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=salman.nabi@arm.com \
    --cc=sdonthineni@nvidia.com \
    --cc=sudeep.holla@arm.com \
    --cc=vsethi@nvidia.com \
    --cc=vwadekar@nvidia.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