Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1231073 > unrolled thread
| Started by | Lee Jones <lee.jones@linaro.org> |
|---|---|
| First post | 2015-09-23 02:40 +0200 |
| Last post | 2015-09-23 16:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v3 2/4] Documentation: bindings: mfd: cros ec: document vbc EC property Lee Jones <lee.jones@linaro.org> - 2015-09-23 02:40 +0200
Re: [PATCH v3 2/4] Documentation: bindings: mfd: cros ec: document vbc EC property Emilio López <emilio.lopez@collabora.co.uk> - 2015-09-23 16:40 +0200
| From | Lee Jones <lee.jones@linaro.org> |
|---|---|
| Date | 2015-09-23 02:40 +0200 |
| Subject | Re: [PATCH v3 2/4] Documentation: bindings: mfd: cros ec: document vbc EC property |
| Message-ID | <qbGgi-4Nq-17@gated-at.bofh.it> |
On Mon, 21 Sep 2015, Emilio López wrote: > Some EC implementations include a small nvram space used to store > verified boot context data. This boolean property lets us indicate > whether this space is available or not on a specific EC implementation. > > Signed-off-by: Emilio López <emilio.lopez@collabora.co.uk> > --- > > Patch is new in v3, split from 3/4 > > Documentation/devicetree/bindings/mfd/cros-ec.txt | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mfd/cros-ec.txt b/Documentation/devicetree/bindings/mfd/cros-ec.txt > index 1777916..136e0c2 100644 > --- a/Documentation/devicetree/bindings/mfd/cros-ec.txt > +++ b/Documentation/devicetree/bindings/mfd/cros-ec.txt > @@ -34,6 +34,10 @@ Required properties (LPC): > - compatible: "google,cros-ec-lpc" > - reg: List of (IO address, size) pairs defining the interface uses > > +Optional properties (all): > +- google,has-vbc-nvram: Some implementations of the EC include a small > + nvram space used to store verified boot context data. This boolean flag > + is used to specify whether this nvram is present or not. Is there no way to check for this at runtime? > Example for I2C: > -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [next] | [standalone]
| From | Emilio López <emilio.lopez@collabora.co.uk> |
|---|---|
| Date | 2015-09-23 16:40 +0200 |
| Message-ID | <qbTnc-6Xk-27@gated-at.bofh.it> |
| In reply to | #1231073 |
Hi Lee, On 22/09/15 21:34, Lee Jones wrote: > On Mon, 21 Sep 2015, Emilio López wrote: > >> Some EC implementations include a small nvram space used to store >> verified boot context data. This boolean property lets us indicate >> whether this space is available or not on a specific EC implementation. >> >> Signed-off-by: Emilio López <emilio.lopez@collabora.co.uk> >> --- >> >> Patch is new in v3, split from 3/4 >> >> Documentation/devicetree/bindings/mfd/cros-ec.txt | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/mfd/cros-ec.txt b/Documentation/devicetree/bindings/mfd/cros-ec.txt >> index 1777916..136e0c2 100644 >> --- a/Documentation/devicetree/bindings/mfd/cros-ec.txt >> +++ b/Documentation/devicetree/bindings/mfd/cros-ec.txt >> @@ -34,6 +34,10 @@ Required properties (LPC): >> - compatible: "google,cros-ec-lpc" >> - reg: List of (IO address, size) pairs defining the interface uses >> >> +Optional properties (all): >> +- google,has-vbc-nvram: Some implementations of the EC include a small >> + nvram space used to store verified boot context data. This boolean flag >> + is used to specify whether this nvram is present or not. > > Is there no way to check for this at runtime? You can issue a read and see if it succeeds, but the problem is that some EC implementations return success even when they don't implement the functionality. Cheers, Emilio -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web