linux-firmware.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Pearson <markpearson@lenovo.com>
To: Josh Boyer <jwboyer@kernel.org>
Cc: <linux-firmware@kernel.org>, <bjorn.andersson@linaro.org>
Subject: Re: [External] Re: qcom: Add firmware for Lenovo ThinkPad X13s
Date: Thu, 4 Aug 2022 07:53:37 -0400	[thread overview]
Message-ID: <c0fcdd91-ad52-0c69-4f6b-343cc8c8da56@lenovo.com> (raw)
In-Reply-To: <CA+5PVA6NCSn6ZsVELY0-mW9v82n6Xro2eVkMAcx=LppgMMC2UQ@mail.gmail.com>

Hi Josh,

On 8/4/22 07:50, Josh Boyer wrote:
> On Wed, Aug 3, 2022 at 4:37 PM Mark Pearson <markpearson@lenovo.com> wrote:
>>
>> The following changes since commit 150864a4d73e8c448eb1e2c68e65f07635fe1a66:
>>
>>   amdgpu partially revert "amdgpu: update beige goby to release 22.20"
>> (2022-07-25 14:16:04 -0400)
>>
>> are available in the Git repository at:
>>
>>   https://github.com/mrhpearson/linux-firmware lenovo-thinkpad-x13s
>>
>> for you to fetch changes up to 4ae4ae88918928e15006eb129ad981aa58216b59:
>>
>>   qcom: Add firmware for Lenovo ThinkPad X13s (2022-08-03 16:29:07 -0400)
>>
>> ----------------------------------------------------------------
>> Mark Pearson (1):
>>       qcom: Add firmware for Lenovo ThinkPad X13s
>>
>>  WHENCE                             |   8 ++++++++
>>  qcom/LENOVO/21BX/adspr.jsn         |  28 ++++++++++++++++++++++++++++
>>  qcom/LENOVO/21BX/adspua.jsn        |  29 +++++++++++++++++++++++++++++
>>  qcom/LENOVO/21BX/battmgr.jsn       |  22 ++++++++++++++++++++++
>>  qcom/LENOVO/21BX/cdspr.jsn         |  22 ++++++++++++++++++++++
>>  qcom/LENOVO/21BX/qcadsp8280.mbn    | Bin 0 -> 14367860 bytes
>>  qcom/LENOVO/21BX/qccdsp8280.mbn    | Bin 0 -> 3575808 bytes
>>  qcom/LENOVO/21BX/qcdxkmsuc8280.mbn | Bin 0 -> 14392 bytes
>>  qcom/LENOVO/21BX/qcslpi8280.mbn    | Bin 0 -> 6213632 bytes
>>  9 files changed, 109 insertions(+)
>>  create mode 100644 qcom/LENOVO/21BX/adspr.jsn
>>  create mode 100644 qcom/LENOVO/21BX/adspua.jsn
>>  create mode 100644 qcom/LENOVO/21BX/battmgr.jsn
>>  create mode 100644 qcom/LENOVO/21BX/cdspr.jsn
>>  create mode 100755 qcom/LENOVO/21BX/qcadsp8280.mbn
>>  create mode 100755 qcom/LENOVO/21BX/qccdsp8280.mbn
>>  create mode 100755 qcom/LENOVO/21BX/qcdxkmsuc8280.mbn
>>  create mode 100755 qcom/LENOVO/21BX/qcslpi8280.mbn
>> [banther@p1g4 linux-firmware]$ git log -1
>> commit 4ae4ae88918928e15006eb129ad981aa58216b59 (HEAD ->
>> lenovo-thinkpad-x13s)
>> Author: Mark Pearson <markpearson@lenovo.com>
>> Date:   Wed Aug 3 13:49:42 2022 -0400
>>
>>     qcom: Add firmware for Lenovo ThinkPad X13s
>>
>>     Add runtime loaded firmware for the audio, compute and sensor DSPs, as
>>     well as the zap shader for the GPU on the Lenovo ThinkPad X13s.
>>
>>     The files are placed under qcom/ as some distributions distribute
>>     linux-firmware as multiple packages and the qcom-specific package will
>>     be needed to provide some of the shared GPU files.
>>
>>     Signed-off-by: Mark Pearson <markpearson@lenovo.com>
> 
> Just so I make sure I understand, is the firmware provided by Qualcomm
> itself, or did Lenovo author it?  As of right now, it looks like
> Lenovo releasing Qualcomm firmware under the existing LICENSE.qcom,
> which is slightly odd.  Normally we'd like to see a Signed-off-by or
> Reviewed-by statement from the owner of the firmware if a partner
> company is releasing it to ensure it was intended to be released.
> 
> josh
The firmware is from Qualcomm but is done for Lenovo for the X13s.

My understanding is we (Lenovo) are the 'owner'. I have discussed
releasing this with Qualcomm and they are supporting us with this and
have approved me doing this release.

Does that help?
Thanks
Mark


  reply	other threads:[~2022-08-04 11:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 20:37 qcom: Add firmware for Lenovo ThinkPad X13s Mark Pearson
2022-08-04 11:50 ` Josh Boyer
2022-08-04 11:53   ` Mark Pearson [this message]
2022-08-15 13:02     ` [External] " Josh Boyer
2022-08-05  9:36 ` Dmitry Baryshkov
2022-08-05 12:43   ` [External] " Mark Pearson
2022-08-05 20:45     ` Dmitry Baryshkov
2022-08-05 20:09   ` Rob Clark
2022-08-05 20:35     ` Dmitry Baryshkov

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=c0fcdd91-ad52-0c69-4f6b-343cc8c8da56@lenovo.com \
    --to=markpearson@lenovo.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=jwboyer@kernel.org \
    --cc=linux-firmware@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;
as well as URLs for NNTP newsgroup(s).