From: Baruch Siach <baruch@tkos.co.il>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] docs: dt: fix documented Primecell compatible string
Date: Tue, 25 Apr 2023 11:31:15 +0300 [thread overview]
Message-ID: <878regbbr7.fsf@tarshish> (raw)
In-Reply-To: <9e137548c4e76e0d8deef6d49460cb37897934ca.1682333574.git.baruch@tkos.co.il>
Hi Rob, Krzysztof,
On Mon, Apr 24 2023, Baruch Siach wrote:
> Only arm,primecell is documented as compatible string for Primecell
> peripherals. Current code agrees with that.
Once again my patches do not show up in patchwork. But they do show in
lore:
https://lore.kernel.org/linux-devicetree/9e137548c4e76e0d8deef6d49460cb37897934ca.1682333574.git.baruch@tkos.co.il/
FYI,
baruch
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> v2:
>
> Split the translation update to a separate patch
> ---
> Documentation/devicetree/usage-model.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/usage-model.rst b/Documentation/devicetree/usage-model.rst
> index b6a287955ee5..0717426856b2 100644
> --- a/Documentation/devicetree/usage-model.rst
> +++ b/Documentation/devicetree/usage-model.rst
> @@ -415,6 +415,6 @@ When using the DT, this creates problems for of_platform_populate()
> because it must decide whether to register each node as either a
> platform_device or an amba_device. This unfortunately complicates the
> device creation model a little bit, but the solution turns out not to
> -be too invasive. If a node is compatible with "arm,amba-primecell", then
> +be too invasive. If a node is compatible with "arm,primecell", then
> of_platform_populate() will register it as an amba_device instead of a
> platform_device.
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2023-04-25 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 10:52 [PATCH v2 1/2] docs: dt: fix documented Primecell compatible string Baruch Siach
2023-04-24 10:52 ` [PATCH v2 2/2] docs: zh_CN/devicetree: sync usage-model fix Baruch Siach
2023-04-27 13:28 ` Yanteng Si
2023-04-25 8:31 ` Baruch Siach [this message]
2023-05-01 9:53 ` [PATCH v2 1/2] docs: dt: fix documented Primecell compatible string Krzysztof Kozlowski
2023-05-01 10:01 ` Baruch Siach
2023-05-01 12:09 ` Krzysztof Kozlowski
2023-05-09 8:36 ` Baruch Siach
2023-06-08 13:31 ` Rob Herring
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=878regbbr7.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=alexs@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=siyanteng@loongson.cn \
/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;
as well as URLs for NNTP newsgroup(s).