From: Rob Herring <robh@kernel.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
kernel@pengutronix.de, Alexandre Torgue <alexandre.torgue@st.com>
Subject: Re: [PATCH v2 2/3] dt-bindings: arm: stm32: add extra SiP compatible for lxa, stm32mp157c-mc1
Date: Mon, 16 Nov 2020 11:01:54 -0600 [thread overview]
Message-ID: <20201116170154.GA1808177@bogus> (raw)
In-Reply-To: <20201110102552.7270-2-a.fatoum@pengutronix.de>
On Tue, 10 Nov 2020 11:25:50 +0100, Ahmad Fatoum wrote:
> The Linux Automation MC-1 is built around an OSD32MP15x SiP with CPU,
> RAM, PMIC, Oscillator and EEPROM. Adjust the binding, so the SiP
> compatible is contained as well. This allows boot firmware to match
> against it to apply fixups if necessary.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> v1 -> v2:
> - split up binding and device tree change
> ---
> Documentation/devicetree/bindings/arm/stm32/stm32.yaml | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-11-16 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 10:25 [PATCH v2 1/3] dt-bindings: vendor-prefixes: document Octavo Systems oct prefix Ahmad Fatoum
2020-11-10 10:25 ` [PATCH v2 2/3] dt-bindings: arm: stm32: add extra SiP compatible for lxa,stm32mp157c-mc1 Ahmad Fatoum
2020-11-16 17:01 ` Rob Herring [this message]
2020-11-10 10:25 ` [PATCH v2 3/3] ARM: dts: stm32: lxa-mc1: add OSD32MP15x to list of compatibles Ahmad Fatoum
2020-11-17 14:26 ` Alexandre Torgue
2020-11-16 17:00 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: document Octavo Systems oct prefix 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=20201116170154.GA1808177@bogus \
--to=robh@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).