From: Tom Rini <trini@konsulko.com>
To: Aswath Govindraju <a-govindraju@ti.com>
Cc: u-boot@lists.denx.de, Suman Anna <s-anna@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: [PATCH v2 1/3] include: configs: j721e_evm.h: Fix the env variable corresponding to QSGMII PHY init
Date: Mon, 14 Mar 2022 09:07:09 -0400 [thread overview]
Message-ID: <20220314130709.GJ9986@bill-the-cat> (raw)
In-Reply-To: <20220222051905.24917-2-a-govindraju@ti.com>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
On Tue, Feb 22, 2022 at 10:49:03AM +0530, Aswath Govindraju wrote:
> QSGMII PHY initialization should only be done for J721E EVMs and not for
> J721E-SK boards. Therefore, fix the environment variables accordingly.
>
> Also, by default remote processors should not be booted in U-Boot but
> rather be left to the users to enable this by setting dorprocboot.
> Therefore, remove dorprocboot that is being set by default.
>
> Fixes: 5980925e2a5a ("include: configs: j721e_evm: Add support to boot ethfw core in j721e")
> Reported-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Aswath Govindraju <a-govindraju@ti.com>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-03-14 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 5:19 [PATCH v2 0/3] J721E: Fix initialization of QSGMII PHY Aswath Govindraju
2022-02-22 5:19 ` [PATCH v2 1/3] include: configs: j721e_evm.h: Fix the env variable corresponding to QSGMII PHY init Aswath Govindraju
2022-03-14 13:07 ` Tom Rini [this message]
2022-02-22 5:19 ` [PATCH v2 2/3] configs: j721e_evm_a72_defconfig: Fix the bootcmd Aswath Govindraju
2022-03-14 13:07 ` Tom Rini
2022-02-22 5:19 ` [PATCH v2 3/3] configs: j721e_hs_evm_a72_defconfig: Add command for initializing QSGMII PHY Aswath Govindraju
2022-03-14 13:07 ` Tom Rini
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=20220314130709.GJ9986@bill-the-cat \
--to=trini@konsulko.com \
--cc=a-govindraju@ti.com \
--cc=kishon@ti.com \
--cc=s-anna@ti.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.