Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kishore Batta <kishore.batta@oss.qualcomm.com>,
	jeff.hugo@oss.qualcomm.com, bjorn.andersson@oss.qualcomm.com,
	konradybcio@kernel.org, konrad.dybcio@oss.qualcomm.com
Cc: andersson@kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v1 06/12] drivers: soc: qcom: Add support for Qualcomm QDU device.
Date: Sat, 7 Mar 2026 14:20:53 +0100	[thread overview]
Message-ID: <c22930d4-38b1-4d34-b624-247a52fc9ae0@kernel.org> (raw)
In-Reply-To: <182f5e1c-3037-4ac7-b2a9-df604e9b2211@oss.qualcomm.com>

On 07/03/2026 12:33, Kishore Batta wrote:
> 
> On 8/28/2025 7:49 PM, Krzysztof Kozlowski wrote:
>> On 25/08/2025 12:19, Kishore Batta wrote:
>>> diff --git a/drivers/soc/qcom/Makefile b/drivers/soc/qcom/Makefile
>>> index 99e490e3174e..8d036edf304a 100644
>>> --- a/drivers/soc/qcom/Makefile
>>> +++ b/drivers/soc/qcom/Makefile
>>> @@ -41,3 +41,4 @@ obj-$(CONFIG_QCOM_INLINE_CRYPTO_ENGINE)	+= qcom_ice.o
>>>   obj-$(CONFIG_QCOM_PBS) +=	qcom-pbs.o
>>>   obj-$(CONFIG_QCOM_UBWC_CONFIG) += ubwc_config.o
>>>   obj-$(CONFIG_QCOM_SAHARA_PROTOCOL) += sahara/
>>> +obj-$(CONFIG_QCOM_QDU) += qdu.o
>>> diff --git a/drivers/soc/qcom/qdu.c b/drivers/soc/qcom/qdu.c
>>> new file mode 100644
>>> index 000000000000..afd8011793fa
>>> --- /dev/null
>>> +++ b/drivers/soc/qcom/qdu.c
>>> @@ -0,0 +1,85 @@
>>> +// SPDX-License-Identifier: GPL-2.0-only
>>> +
>>> +/* Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries. */
>>> +
>>> +#include <linux/init.h>
>>> +#include <linux/kernel.h>
>>> +#include <linux/module.h>
>>> +#include <linux/sahara_image_table_ops.h>
>>> +
>>> +static const char * const qdu100_image_table[] = {
>>> +	[5] = "qcom/qdu100/uefi.elf",
>>> +	[8] = "qcom/qdu100/qdsp6sw.mbn",
>>> +	[16] = "qcom/qdu100/efs1.bin",
>>> +	[17] = "qcom/qdu100/efs2.bin",
>>> +	[20] = "qcom/qdu100/efs3.bin",
>>> +	[23] = "qcom/qdu100/aop.mbn",
>>> +	[25] = "qcom/qdu100/tz.mbn",
>>> +	[29] = "qcom/qdu100/zeros_1sector.bin",
>>> +	[33] = "qcom/qdu100/hypvm.mbn",
>>> +	[34] = "qcom/qdu100/mdmddr.mbn",
>>> +	[36] = "qcom/qdu100/multi_image_qti.mbn",
>>> +	[37] = "qcom/qdu100/multi_image.mbn",
>>> +	[38] = "qcom/qdu100/xbl_config.elf",
>>> +	[39] = "qcom/qdu100/abl_userdebug.elf",
>>> +	[40] = "qcom/qdu100/zeros_1sector.bin",
>>> +	[41] = "qcom/qdu100/devcfg.mbn",
>>> +	[42] = "qcom/qdu100/zeros_1sector.bin",
>>> +	[43] = "qcom/qdu100/kernel_boot.elf",
>> We should not accept this code because corresponding linux-firmware
>> release was not properly authorized in Qualcomm. All of above might change.
>>
>> I can give more details in private.
> Thanks for the comment. The QDu100 image table in v2 reflects the 
> firmware images required by the device for boot. The sahara driver 
> relies on request_firmware_nowarn() and does not make assumptions about 
> firmware distributions or availability.

You did not answer to my comment at all. It does not matter what it
reflects to. You violated GPL license and that's NAK here.

And responding to this after half a year with irrelevant comment of
whatever is clearly:

NAK


Best regards,
Krzysztof

  reply	other threads:[~2026-03-07 13:20 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 10:19 [PATCH v1 00/12] Sahara protocol enhancements Kishore Batta
2025-08-25 10:19 ` [PATCH v1 01/12] Add documentation for Sahara protocol Kishore Batta
2025-08-25 10:19 ` [PATCH v1 02/12] drivers: accel : Move AIC specific image tables to mhi_controller.c file Kishore Batta
2025-08-25 21:08   ` Bjorn Andersson
2026-03-07 11:30     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 03/12] drivers: accel: qaic: Support for registration of image tables in Sahara Kishore Batta
2025-08-25 21:26   ` Bjorn Andersson
2026-03-07 11:31     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 04/12] drivers: accel: Register Qualcomm AIC specific image tables with Sahara Kishore Batta
2025-08-25 21:38   ` Bjorn Andersson
2026-03-07 11:31     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 05/12] drivers: soc: qcom: Move Sahara driver to drivers/soc/qcom directory Kishore Batta
2025-08-25 22:12   ` Bjorn Andersson
2026-03-07 11:57     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 06/12] drivers: soc: qcom: Add support for Qualcomm QDU device Kishore Batta
2025-08-25 23:24   ` Bjorn Andersson
2025-08-28 12:48     ` Kishore Batta
2026-03-07 11:32     ` Kishore Batta
2025-08-28 14:19   ` Krzysztof Kozlowski
2026-03-07 11:33     ` Kishore Batta
2026-03-07 13:20       ` Krzysztof Kozlowski [this message]
2026-03-08  6:12         ` Kishore Batta
2026-03-09 14:25           ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 07/12] drivers: soc: qcom: Add sysfs support for DDR training data in Sahara Kishore Batta
2025-08-25 22:37   ` Bjorn Andersson
2026-03-07 11:31     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 08/12] drivers: soc: qcom: Support Sahara command mode packets(READY and EXECUTE) Kishore Batta
2025-08-25 22:58   ` Bjorn Andersson
2026-03-07 11:32     ` Kishore Batta
2025-08-28 14:20   ` Krzysztof Kozlowski
2026-03-07 11:33     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 09/12] drivers: soc: qcom: Remove is_mem_dump_mode variable Kishore Batta
2025-08-25 22:59   ` Bjorn Andersson
2026-03-07 11:32     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 10/12] drivers: soc: qcom: Support for DDR training in Sahara Kishore Batta
2025-08-25 23:14   ` Bjorn Andersson
2026-03-07 11:32     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 11/12] drivers: soc: qcom: Support to load saved DDR training data " Kishore Batta
2025-08-26  2:16   ` Bjorn Andersson
2026-03-07 11:32     ` Kishore Batta
2025-08-25 10:19 ` [PATCH v1 12/12] Add sysfs ABI documentation for DDR training data node Kishore Batta

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=c22930d4-38b1-4d34-b624-247a52fc9ae0@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=jeff.hugo@oss.qualcomm.com \
    --cc=kishore.batta@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.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