From: "Falkowski, Maciej" <maciej.falkowski@linux.intel.com>
To: Jeff Hugo <jeff.hugo@oss.qualcomm.com>, dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, karol.wachowski@linux.intel.com,
lizhi.hou@amd.com
Subject: Re: [PATCH] accel/ivpu: Implement warm boot flow for NPU6 and unify boot handling
Date: Thu, 8 Jan 2026 12:37:11 +0100 [thread overview]
Message-ID: <deb4834f-3770-483e-9d1e-3c2a885f971f@linux.intel.com> (raw)
In-Reply-To: <ca17e5d1-9de9-44b2-a15a-664d50612ed6@oss.qualcomm.com>
On 1/7/2026 6:11 PM, Jeff Hugo wrote:
> On 12/30/2025 7:21 AM, Maciej Falkowski wrote:
>> From: Karol Wachowski <karol.wachowski@linux.intel.com>
>>
>> Starting from NPU6, the driver can pass boot parameters address through
>> the AON retention register and toggle between cold/warm boot types using
>> the boot_type parameter, while setting the cold boot entry point in both
>> cases.
>>
>> Refactor the existing cold/warm boot handling to be consistent with the
>> new NPU6 boot flow requirements and still maintain compatibility with
>> older boot flows.
>>
>> This will allow firmware to remove support for legacy warm boot starting
>> from NPU6.
>>
>> Fixes: 550f4dd2cedd ("accel/ivpu: Add support for Nova Lake's NPU")
>> Signed-off-by: Karol Wachowski <karol.wachowski@linux.intel.com>
>> Signed-off-by: Maciej Falkowski <maciej.falkowski@linux.intel.com>
>
> Happy new year.
>
> Reviewed-by: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
Happy new year!
Pushed to drm-misc-next.
Best regards,
Maciej
prev parent reply other threads:[~2026-01-08 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 14:21 [PATCH] accel/ivpu: Implement warm boot flow for NPU6 and unify boot handling Maciej Falkowski
2026-01-07 11:46 ` Andrzej Kacprowski
2026-01-07 17:11 ` Jeff Hugo
2026-01-08 11:37 ` Falkowski, Maciej [this message]
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=deb4834f-3770-483e-9d1e-3c2a885f971f@linux.intel.com \
--to=maciej.falkowski@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=karol.wachowski@linux.intel.com \
--cc=lizhi.hou@amd.com \
--cc=oded.gabbay@gmail.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