public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Devarsh Thakkar <devarsht@ti.com>
To: <andersson@kernel.org>, <devicetree@vger.kernel.org>,
	<mathieu.poirier@linaro.org>, <p.zabel@pengutronix.de>,
	<linux-remoteproc@vger.kernel.org>, <robh+dt@kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <s-anna@ti.com>
Cc: <hnagalla@ti.com>, <praneeth@ti.com>, <nm@ti.com>,
	<vigneshr@ti.com>, <a-bhatia1@ti.com>, <j-luthra@ti.com>,
	<devarsht@ti.com>, <rogerq@kernel.org>
Subject: [PATCH v7 0/3] Add single core R5F IPC for AM62 SoC family
Date: Fri, 10 Mar 2023 21:55:41 +0530	[thread overview]
Message-ID: <20230310162544.3468365-1-devarsht@ti.com> (raw)

Devarsh Thakkar (3):
  remoteproc: k3-r5: Simplify cluster mode setting usage
  dt-bindings: remoteproc: ti: Add new compatible for AM62 SoC family
  remoteproc: k3-r5: Use separate compatible string for TI AM62x SoC
    family

 .../bindings/remoteproc/ti,k3-r5f-rproc.yaml  |  76 ++++++++----
 drivers/remoteproc/ti_k3_r5_remoteproc.c      | 110 ++++++++++++------
 2 files changed, 130 insertions(+), 56 deletions(-)
---
V2: 
  - dt-bindings: Avoid acronyms, use "Device Manager" instead of "DM" 
V3: 
  - dt-bindings: Use separate if block for each compatible for ti,cluster-mode property
  - dt-bindings: Rearrange compatibles as per alphabatical order
V4:
  - dt-bindings: Place each enum in separate line in allOf
V5: 
  - No change (fixing typo in email address) 
V6: 
  - dt-bindings: Remove reviewed-by due to new modifications to use cluster-mode=3
    Introduce Simplify cluster-mode setting preamble patch per review comments
  - Use CLUSTER_MODE_SINGLECORE for AM62x
  - Set PROC_BOOT_CFG_FLAG_R5_SINGLE_CORE for single core.
V7: 
  - Override to appropriate cluster-mode per firmware status flag without checking soc_data
  - Set appropriate mode as default if not provided in DT                         
  - Check mode validity against SoC data during probe
  - Rebase on top of 6.3 linux-next 
-- 
2.34.1


             reply	other threads:[~2023-03-10 16:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10 16:25 Devarsh Thakkar [this message]
2023-03-10 16:25 ` [PATCH v7 1/3] remoteproc: k3-r5: Simplify cluster mode setting usage Devarsh Thakkar
2023-03-10 16:25 ` [PATCH v7 2/3] dt-bindings: remoteproc: ti: Add new compatible for AM62 SoC family Devarsh Thakkar
2023-03-14 20:08   ` Krzysztof Kozlowski
2023-03-10 16:25 ` [PATCH v7 3/3] remoteproc: k3-r5: Use separate compatible string for TI AM62x " Devarsh Thakkar
2023-03-17 16:17   ` Mathieu Poirier
2023-03-27 15:24     ` Devarsh Thakkar
2023-03-28  7:52     ` Roger Quadros
2023-03-28 16:08       ` Devarsh Thakkar
2023-03-29  8:21         ` Roger Quadros
2023-03-29 13:15           ` Devarsh Thakkar

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=20230310162544.3468365-1-devarsht@ti.com \
    --to=devarsht@ti.com \
    --cc=a-bhatia1@ti.com \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=j-luthra@ti.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=nm@ti.com \
    --cc=p.zabel@pengutronix.de \
    --cc=praneeth@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=s-anna@ti.com \
    --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