From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/6] J721e HS device support
Date: Mon, 16 Dec 2019 15:50:56 -0500 [thread overview]
Message-ID: <312875c7-1734-e691-25db-dc551fbc126a@ti.com> (raw)
In-Reply-To: <749b0881-4237-f532-1981-4c454979f424@ti.com>
Hi Tom,
I see you have a -next again, if you don't want to take this for the
v2020.01 perhaps this could be a good candidate for the next?
Andrew
On 11/20/19 10:59 PM, Lokesh Vutla wrote:
>
>
> On 20/11/19 11:10 PM, Andrew F. Davis wrote:
>> Hello all,
>>
>> This series brings up High-Security (HS) device support on the J721e
>> platform. Support for this K3 HS device is much like the existing
>> AM65x HS and this series leverages much of that support.
>>
>> There are also a couple tangentially related fixups that I noticed while
>> adding this support and testing. Although not strictly needed they
>> do allow J721e HS to just work out-of-box by the time the last patch
>> adds the defconfigs.
>
> For the entire series:
>
> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
>
> Thank and regards,
> Lokesh
>
>>
>> Thanks,
>> Andrew
>>
>> Andrew F. Davis (6):
>> configs: j721e_evm.h: Sync J721e environment configuration with AM65x
>> configs: ti: Factor out call to 'args_mmc' into MMC common environment
>> arm: K3: Fix header comment match AM6 specific file function
>> arm: K3: Disable ROM configured firewalls
>> arm: K3: Increase default SYSFW image size allocation
>> configs: Add configs for J721e High Security EVM
>>
>> arch/arm/mach-k3/Kconfig | 2 +-
>> arch/arm/mach-k3/am6_init.c | 28 +++++++-
>> arch/arm/mach-k3/common.c | 30 ++++++++
>> arch/arm/mach-k3/common.h | 7 ++
>> arch/arm/mach-k3/j721e_init.c | 52 ++++++++++++++
>> configs/j721e_hs_evm_a72_defconfig | 106 +++++++++++++++++++++++++++++
>> configs/j721e_hs_evm_r5_defconfig | 102 +++++++++++++++++++++++++++
>> include/configs/j721e_evm.h | 16 ++++-
>> include/configs/ti_armv7_common.h | 1 -
>> include/environment/ti/mmc.h | 5 +-
>> 10 files changed, 341 insertions(+), 8 deletions(-)
>> create mode 100644 configs/j721e_hs_evm_a72_defconfig
>> create mode 100644 configs/j721e_hs_evm_r5_defconfig
>>
next prev parent reply other threads:[~2019-12-16 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 17:40 [U-Boot] [PATCH 0/6] J721e HS device support Andrew F. Davis
2019-11-20 17:40 ` [U-Boot] [PATCH 1/6] configs: j721e_evm.h: Sync J721e environment configuration with AM65x Andrew F. Davis
2019-11-20 17:40 ` [U-Boot] [PATCH 2/6] configs: ti: Factor out call to 'args_mmc' into MMC common environment Andrew F. Davis
2019-11-20 17:40 ` [U-Boot] [PATCH 3/6] arm: K3: Fix header comment match AM6 specific file function Andrew F. Davis
2019-11-20 17:40 ` [U-Boot] [PATCH 4/6] arm: K3: Disable ROM configured firewalls Andrew F. Davis
2019-11-20 17:40 ` [U-Boot] [PATCH 5/6] arm: K3: Increase default SYSFW image size allocation Andrew F. Davis
2019-11-20 17:40 ` [U-Boot] [PATCH 6/6] configs: Add configs for J721e High Security EVM Andrew F. Davis
2019-11-21 3:59 ` [U-Boot] [PATCH 0/6] J721e HS device support Lokesh Vutla
2019-12-16 20:50 ` Andrew F. Davis [this message]
2020-01-10 18:38 ` Andrew F. Davis
2020-01-10 19:28 ` Andrew F. Davis
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=312875c7-1734-e691-25db-dc551fbc126a@ti.com \
--to=afd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox