From: Richard Gong <richard.gong@linux.intel.com>
To: David Laight <David.Laight@ACULAB.COM>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "mdf@kernel.org" <mdf@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Richard Gong <richard.gong@intel.com>
Subject: Re: [PATCH] firmware: stratix10-svc: extend SVC driver to get the firmware version
Date: Tue, 30 Mar 2021 11:02:46 -0500 [thread overview]
Message-ID: <16c40de5-b405-92b6-d08f-e395b9774e7e@linux.intel.com> (raw)
In-Reply-To: <26176a0062114b9faa7c2c64c8ea3e64@AcuMS.aculab.com>
Hi David,
On 3/30/21 9:19 AM, David Laight wrote:
> From: richard.gong@linux.intel.com
>> Sent: 30 March 2021 15:33
>>
>> Extend Intel service layer driver to get the firmware version running at
>> FPGA device. Therefore FPGA manager driver, one of Intel service layer
>> driver's client, can decide whether to handle the newly added bitstream
>> authentication function based on the retrieved firmware version.
>
> Using the version number to detect features is just plain wrong.
>
> You should use something like a bitmap of supported features.
Firmware, which runs at EL3, returns the version to Intel service layer
driver in a 64-bit value at the register. Intel service layer driver
runs at EL1.
Regards,
Richard
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
next prev parent reply other threads:[~2021-03-30 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 14:33 [PATCH] A patch for Intel service layer driver richard.gong
2021-03-30 14:33 ` [PATCH] firmware: stratix10-svc: extend SVC driver to get the firmware version richard.gong
2021-03-30 14:19 ` David Laight
2021-03-30 16:02 ` Richard Gong [this message]
2021-03-30 16:15 ` Moritz Fischer
2021-03-30 17:36 ` Richard Gong
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=16c40de5-b405-92b6-d08f-e395b9774e7e@linux.intel.com \
--to=richard.gong@linux.intel.com \
--cc=David.Laight@ACULAB.COM \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=richard.gong@intel.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
all inboxes | Powered by JetHome®