From: Tinghan Shen <tinghan.shen@mediatek.com>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tinghan Shen <tinghan.shen@mediatek.com>,
Mark Brown <broonie@kernel.org>, YC Hung <yc.hung@mediatek.com>,
Curtis Malainey <cujomalainey@chromium.org>,
Allen-KH Cheng <allen-kh.cheng@mediatek.com>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: [PATCH v2 0/3] Add MT8186 ADSP dt-binding
Date: Thu, 9 Jun 2022 16:30:58 +0800 [thread overview]
Message-ID: <20220609083101.24195-1-tinghan.shen@mediatek.com> (raw)
v1 -> v2:
1. Change mbox-names from mbox0/mbox1 to rep/req for both mt8186 and mt8195.
2. rename clock-names and remove unused headers
Tinghan Shen (3):
dt-bindings: dsp: mediatek: Use meaningful names for mbox
firmware: mediatek: Use meaningful names for mbox
dt-bindings: dsp: mediatek: add mt8186 dsp document
.../bindings/dsp/mediatek,mt8186-dsp.yaml | 91 +++++++++++++++++++
.../bindings/dsp/mediatek,mt8195-dsp.yaml | 6 +-
drivers/firmware/mtk-adsp-ipc.c | 6 +-
3 files changed, 99 insertions(+), 4 deletions(-)
create mode 100644 Documentation/devicetree/bindings/dsp/mediatek,mt8186-dsp.yaml
--
2.18.0
next reply other threads:[~2022-06-09 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 8:30 Tinghan Shen [this message]
2022-06-09 8:30 ` [PATCH v2 1/3] dt-bindings: dsp: mediatek: Use meaningful names for mbox Tinghan Shen
2022-06-13 12:41 ` AngeloGioacchino Del Regno
2022-06-15 17:30 ` Krzysztof Kozlowski
2022-06-09 8:31 ` [PATCH v2 2/3] firmware: " Tinghan Shen
2022-06-13 12:37 ` AngeloGioacchino Del Regno
2022-06-15 3:22 ` Tinghan Shen
2022-06-09 8:31 ` [PATCH v2 3/3] dt-bindings: dsp: mediatek: add mt8186 dsp document Tinghan Shen
2022-06-15 17:32 ` Krzysztof Kozlowski
2022-06-16 7:34 ` Tinghan Shen
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=20220609083101.24195-1-tinghan.shen@mediatek.com \
--to=tinghan.shen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=broonie@kernel.org \
--cc=cujomalainey@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=yc.hung@mediatek.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
all inboxes | Powered by JetHome®