From: Jonathan Corbet <corbet@lwn.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Linus Walleij <linus.walleij@linaro.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: arm: tcm: Fix a few typos
Date: Wed, 19 Feb 2020 02:42:53 -0700 [thread overview]
Message-ID: <20200219024253.3ce1d2b2@lwn.net> (raw)
In-Reply-To: <20200218163829.13066-1-j.neuschaefer@gmx.net>
On Tue, 18 Feb 2020 17:38:25 +0100
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
> Documentation/arm/tcm.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/arm/tcm.rst b/Documentation/arm/tcm.rst
> index effd9c7bc968..b256f9783883 100644
> --- a/Documentation/arm/tcm.rst
> +++ b/Documentation/arm/tcm.rst
> @@ -4,18 +4,18 @@ ARM TCM (Tightly-Coupled Memory) handling in Linux
>
> Written by Linus Walleij <linus.walleij@stericsson.com>
>
> -Some ARM SoC:s have a so-called TCM (Tightly-Coupled Memory).
> +Some ARM SoCs have a so-called TCM (Tightly-Coupled Memory).
> This is usually just a few (4-64) KiB of RAM inside the ARM
> processor.
>
> -Due to being embedded inside the CPU The TCM has a
> +Due to being embedded inside the CPU, the TCM has a
> Harvard-architecture, so there is an ITCM (instruction TCM)
> and a DTCM (data TCM). The DTCM can not contain any
> instructions, but the ITCM can actually contain data.
> The size of DTCM or ITCM is minimum 4KiB so the typical
> minimum configuration is 4KiB ITCM and 4KiB DTCM.
>
> -ARM CPU:s have special registers to read out status, physical
> +ARM CPUs have special registers to read out status, physical
> location and size of TCM memories. arch/arm/include/asm/cputype.h
> defines a CPUID_TCM register that you can read out from the
> system control coprocessor. Documentation from ARM can be found
Applied, thanks.
jon
prev parent reply other threads:[~2020-02-19 9:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 16:38 Jonathan Neuschäfer
2020-02-19 9:42 ` Jonathan Corbet [this message]
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=20200219024253.3ce1d2b2@lwn.net \
--to=corbet@lwn.net \
--cc=j.neuschaefer@gmx.net \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
/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
Powered by JetHome