From: Bryan Brattlof <bb@ti.com>
To: Tom Rini <trini@konsulko.com>,
Vignesh Raghavendra <vigneshr@ti.com>, Andrew Davis <afd@ti.com>,
Nishanth Menon <nm@ti.com>, Judith Mendez <jm@ti.com>
Cc: UBoot Mailing List <u-boot@lists.denx.de>, Bryan Brattlof <bb@ti.com>
Subject: [PATCH 0/2] TI's K3 documentation updates
Date: Mon, 19 Dec 2022 14:29:48 -0600 [thread overview]
Message-ID: <20221219202950.1581-1-bb@ti.com> (raw)
Hello everyone!
Before the holidays get started, I wanted to improve the documentation
for TI's K3 generation of SoCs. Specifically I wanted to collect all the
similarities into one file called 'K3' in doc/board/ti/ and leave the
details to each SoC specific sub-page.
My goal is to eliminate the boilerplate needed to document each new K3
SoC and instead allow the sub-pages to highlight the differences that
could trip others as they begin to develop on their new K3 device.
Thanks for reviewing!
~Bryan
Bryan Brattlof (2):
doc: ti: reorganize existing ti docs
doc: ti: add the K3 generation page
doc/board/ti/am335x_evm.rst | 5 +-
doc/board/ti/am62x_sk.rst | 4 +-
doc/board/ti/index.rst | 5 +-
doc/board/ti/j721e_evm.rst | 4 +-
doc/board/ti/k3.rst | 276 ++++++++++++++++++++++++++++++++++++
5 files changed, 286 insertions(+), 8 deletions(-)
create mode 100644 doc/board/ti/k3.rst
base-commit: 2243922edca9f56a9d5519b9d6e36f5d7a18434d
--
2.39.0
next reply other threads:[~2022-12-19 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 20:29 Bryan Brattlof [this message]
2022-12-19 20:29 ` [PATCH 1/2] doc: ti: reorganize existing ti docs Bryan Brattlof
2022-12-22 9:56 ` Heinrich Schuchardt
2022-12-22 9:58 ` Heinrich Schuchardt
2022-12-19 20:29 ` [PATCH 2/2] doc: ti: add the K3 generation page Bryan Brattlof
2023-01-03 18:28 ` Andrew Davis
2023-01-05 23:01 ` Bryan Brattlof
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=20221219202950.1581-1-bb@ti.com \
--to=bb@ti.com \
--cc=afd@ti.com \
--cc=jm@ti.com \
--cc=nm@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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