devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Drew Fustini <dfustini@baylibre.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Nishanth Menon <nm@ti.com>, Dave Gerlach <d-gerlach@ti.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] ARM: dts: enable am33xx and am43xx wkup_m3_ipc features
Date: Tue, 3 May 2022 09:15:15 +0300	[thread overview]
Message-ID: <YnDIc6avf+8PwAXK@atomide.com> (raw)
In-Reply-To: <20220502021508.1342869-1-dfustini@baylibre.com>

* Drew Fustini <dfustini@baylibre.com> [220502 02:11]:
> Enable new wkup_m3_ipc features which includes IO isolation on the
> am437x-gp-evm and i2c voltage scaling firmware for both am33xx and
> am43xx based boards.
> 
> This dts series depends on the bindings and driver changes in:
> - [PATCH v3 0/2] soc: ti: wkup_m3_ipc: support i2c voltage scaling [1]
> - [PATCH v3 0/2] soc: ti: wkup_m3_ipc: Add support for IO Isolation [2]
> 
> Dave Gerlach (3):
>   ARM: dts: am437x-gp-evm: Enable wkup_m3 control of IO isolation
>   ARM: dts: am33xx: Add i2c voltage scaling firmware to wkup_m3_ipc
>   ARM: dts: am43xx: Add i2c voltage scaling firmware to wkup_m3_ipc

Applying these all into omap-for-v5.19/dt thanks.

Tony

      parent reply	other threads:[~2022-05-03  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  2:15 [PATCH 0/3] ARM: dts: enable am33xx and am43xx wkup_m3_ipc features Drew Fustini
2022-05-02  2:15 ` [PATCH 1/3] ARM: dts: am437x-gp-evm: Enable wkup_m3 control of IO isolation Drew Fustini
2022-05-02  2:15 ` [PATCH 2/3] ARM: dts: am33xx: Add i2c voltage scaling firmware to wkup_m3_ipc Drew Fustini
2022-05-02  2:15 ` [PATCH 3/3] ARM: dts: am43xx: " Drew Fustini
2022-05-03  6:15 ` Tony Lindgren [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=YnDIc6avf+8PwAXK@atomide.com \
    --to=tony@atomide.com \
    --cc=d-gerlach@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dfustini@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.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).