All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] fsl: csu: add an API to set individual device access permission
Date: Thu, 21 Jul 2016 04:38:59 +0000	[thread overview]
Message-ID: <VI1PR0401MB19661BC6D42EE7D33EFF15FF97090@VI1PR0401MB1966.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1467613697-18128-3-git-send-email-Zhiqiang.Hou@nxp.com>


> -----Original Message-----
> From: Zhiqiang Hou [mailto:Zhiqiang.Hou at nxp.com]
> Sent: Monday, July 04, 2016 11:58 AM
> To: u-boot at lists.denx.de; albert.u.boot at aribaud.net; york sun
> <york.sun@nxp.com>; wd at denx.de; Prabhakar Kushwaha
> <prabhakar.kushwaha@nxp.com>; alison.wang at freescale.com;
> Mingkai.Hu at freescale.com
> Cc: yao.yuan at freescale.com; Qianyu.Gong at freescale.com;
> bmeng.cn at gmail.com; Shengzhou Liu <shengzhou.liu@nxp.com>; Zhiqiang Hou
> <zhiqiang.hou@nxp.com>
> Subject: [PATCH 3/5] fsl: csu: add an API to set individual device access
> permission
> 
> From: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
> 
> Add this API to make the individual device is able to be set to
> the specified permission.
> 

I am curious about requirement of devices to configure CSU in their driver. 
Why cannot it be done during early boot sequence as part of normal boot-flow for all devices

--prabhakar 

  reply	other threads:[~2016-07-21  4:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04  6:28 [U-Boot] [PATCH 1/5] fsl: serdes: ensure accessing the initialized maps of serdes protocol Zhiqiang Hou
2016-07-04  6:28 ` [U-Boot] [PATCH 2/5] arm: fsl-layerscape: move forward the non-secure access permission setup Zhiqiang Hou
2016-07-04  6:28 ` [U-Boot] [PATCH 3/5] fsl: csu: add an API to set individual device access permission Zhiqiang Hou
2016-07-21  4:38   ` Prabhakar Kushwaha [this message]
2016-07-21  7:55     ` Zhiqiang Hou
2016-07-04  6:28 ` [U-Boot] [PATCH 4/5] fsl: csu: add an API to disable all R/W permission to PCIe Zhiqiang Hou
2016-07-04  6:28 ` [U-Boot] [PATCH 5/5] fsl-layerscape: Add workaround for PCIe erratum A010315 Zhiqiang Hou
2016-07-19 16:01   ` york sun
2016-07-20 10:04     ` Zhiqiang Hou
2016-07-19  7:04 ` [U-Boot] [PATCH 1/5] fsl: serdes: ensure accessing the initialized maps of serdes protocol Zhiqiang Hou
2016-07-19 15:45 ` york sun
2016-07-20  9:38   ` Zhiqiang Hou
2016-07-20 21:15     ` york sun
2016-07-21  2:42       ` Zhiqiang Hou
2016-07-21  4:28       ` Prabhakar Kushwaha
2016-07-21  7:40         ` Zhiqiang Hou

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=VI1PR0401MB19661BC6D42EE7D33EFF15FF97090@VI1PR0401MB1966.eurprd04.prod.outlook.com \
    --to=prabhakar.kushwaha@nxp.com \
    --cc=u-boot@lists.denx.de \
    /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.