All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: richard.gong@linux.intel.com
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org, richard.gong@intel.com
Subject: Re: [PATCHv1] Add Intel Stratix10 service layer driver
Date: Thu, 25 Jan 2018 17:53:52 +0100	[thread overview]
Message-ID: <20180125165352.GA21640@kroah.com> (raw)
In-Reply-To: <1516898344-20020-1-git-send-email-richard.gong@linux.intel.com>

On Thu, Jan 25, 2018 at 10:39:03AM -0600, richard.gong@linux.intel.com wrote:
> From: Richard Gong <richard.gong@intel.com>
> 
> Intel Stratix10 SoC is composed of a 64 bit quad-core ARM Cortex A53 hard
> processor system (HPS) and Secure Device Manager (SDM). SDM is the hardware
> which does the FPGA configuration, QSPI, Crypto and warm reset.
> 
> When the FPGA is configured from HPS, there needs to be a way for HPS to
> notify SDM the location and size of the configuration data. Then SDM will
> get the configuration data from that location and perform the FPGA configuration.
> 
> To meet the whole system security needs and support virtual machine
> requesting communication with SDM, only the secure world of software (EL3,
> Exception Level 3) can interface with SDM. All software entities running
> on other exception levels must channel through the EL3 software whenever it
> needs service from SDM.
> 
> Intel Stratix10 service layer driver is added to provide the service for
> FPGA configuration. Running at privileged exception level (EL1, Exception
> Level 1), Intel Stratix10 service layer driver interfaces with the service
> provider at EL1 (Intel Stratix10 FPGA Manager) and manages secure monitor
> call (SMC) to communicate with secure monitor software at secure monitor
> exception level (EL3).
> 
> Later the Intel Stratix10 service layer driver will be extended to provide
> services for QSPI, Crypto and warm reset.
> 
> Richard Gong (1):
>   driver: misc: add Intel Stratix10 service layer driver
> 
>  drivers/misc/Kconfig                       |   3 +-
>  drivers/misc/Makefile                      |   3 +-
>  drivers/misc/intel-service/Kconfig         |   9 +
>  drivers/misc/intel-service/Makefile        |   2 +
>  drivers/misc/intel-service/intel_service.c | 703 +++++++++++++++++++++++++++++
>  include/linux/intel-service-client.h       | 227 ++++++++++
>  include/linux/intel-service.h              | 122 +++++
>  include/linux/intel-smc.h                  | 246 ++++++++++

Simple questions first:
 - why do you have 3 different .h files for a single .c file?
 - why do you have any public .h files for a single .c file?
 - use the correct SPDX markers for your file licenses, Intel legal
   knows all about this, please follow their rules.
 - why is this in a subdirectory for a single .c file?

thanks,

greg k-h

  parent reply	other threads:[~2018-01-25 16:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 16:39 [PATCHv1] Add Intel Stratix10 service layer driver richard.gong
2018-01-25 16:39 ` [PATCHv1] driver: misc: add " richard.gong
2018-01-25 16:54   ` Greg KH
2018-01-25 16:55   ` Greg KH
2018-01-25 16:58   ` Greg KH
2018-01-25 23:27   ` Randy Dunlap
2018-01-25 16:53 ` Greg KH [this message]
2018-01-30  2:08   ` [PATCHv1] Add " Richard Gong
2018-01-30  7:41     ` Greg KH
2018-02-22 21:43       ` Alan Tull

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=20180125165352.GA21640@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.gong@intel.com \
    --cc=richard.gong@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.