All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Paul Barker <paul.barker@sancloud.com>
Cc: u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH v3 2/3] arm: dts: am335x-sancloud-bbe-lite: UEFI SPI export
Date: Wed, 21 Sep 2022 12:15:09 -0400	[thread overview]
Message-ID: <20220921161509.GV3044094@bill-the-cat> (raw)
In-Reply-To: <20220921160628.4166966-3-paul.barker@sancloud.com>

[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]

On Wed, Sep 21, 2022 at 05:06:27PM +0100, Paul Barker wrote:
> Add properties to the Authenta SPI flash device node to enable access by
> a UEFI application using a fixed GUID. Also specify that this device is
> JEDEC compatible so that it is correctly initialized when running
> `sf probe`.
> 
> Signed-off-by: Paul Barker <paul.barker@sancloud.com>
> ---
>  arch/arm/dts/am335x-sancloud-bbe-lite.dts | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/dts/am335x-sancloud-bbe-lite.dts b/arch/arm/dts/am335x-sancloud-bbe-lite.dts
> index d6ef19311a91..f1ff9d6024cb 100644
> --- a/arch/arm/dts/am335x-sancloud-bbe-lite.dts
> +++ b/arch/arm/dts/am335x-sancloud-bbe-lite.dts
> @@ -37,14 +37,20 @@
>  	pinctrl-names = "default";
>  	pinctrl-0 = <&bb_spi0_pins>;
>  
> -	channel@0 {
> +	authenta-flash@0 {
>  		#address-cells = <1>;
>  		#size-cells = <0>;
>  
> -		compatible = "micron,spi-authenta";
> +		compatible = "micron,spi-authenta", "jedec,spi-nor";
>  
>  		reg = <0>;
>  		spi-max-frequency = <16000000>;
>  		spi-cpha;
> +
> +		uefi-spi-vendor = "micron";
> +		uefi-spi-part-number = "mt25ql128abb";
> +		/* GUID in UEFI format: 77126730-a4ca-4386-b341-881fe18e7f7d */
> +		uefi-spi-io-guid = [30 67 12 77 ca a4 86 43
> +				    b3 41 88 1f e1 8e 7f 7d];
>  	};
>  };

Are we far enough along with part one of this series to talk about
getting these properties in the upstream binding document now?

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2022-09-21 16:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 16:06 [PATCH v3 0/3] Support UEFI SPI I/O protocol Paul Barker
2022-09-21 16:06 ` [PATCH v3 1/3] efi_loader: Add SPI I/O protocol support Paul Barker
2022-09-26 12:43   ` Ilias Apalodimas
2022-09-26 13:13     ` Heinrich Schuchardt
2022-09-26 13:40       ` Ilias Apalodimas
2022-10-03 12:05       ` Paul Barker
2022-10-03 12:00     ` Paul Barker
2022-09-26 13:52   ` Heinrich Schuchardt
2022-10-03 12:05     ` Paul Barker
2022-10-04 16:31       ` Paul Barker
2022-10-04 17:25         ` Heinrich Schuchardt
2022-09-21 16:06 ` [PATCH v3 2/3] arm: dts: am335x-sancloud-bbe-lite: UEFI SPI export Paul Barker
2022-09-21 16:15   ` Tom Rini [this message]
2022-09-26 11:33     ` Ilias Apalodimas
2022-09-26 13:13       ` Tom Rini
2022-09-26 13:33         ` Heinrich Schuchardt
2022-09-26 19:13           ` Tom Rini
2022-09-21 16:06 ` [PATCH v3 3/3] am335x_evm_defconfig: Enable Micron SPI flash support Paul Barker
2022-09-26 13:21   ` Heinrich Schuchardt
2022-10-03 12:07     ` Paul Barker

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=20220921161509.GV3044094@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=paul.barker@sancloud.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.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.