From: Hsin-Yi Wang <hsinyi@chromium.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
maoguang.meng@mediatek.com, yong.wu@mediatek.com
Subject: [PATCH v4 2/3] dt-bindings: mediatek: Add mediatek,mt8183-jpgenc compatible
Date: Fri, 11 Jun 2021 19:20:08 +0800 [thread overview]
Message-ID: <20210611112009.2955944-2-hsinyi@chromium.org> (raw)
In-Reply-To: <20210611112009.2955944-1-hsinyi@chromium.org>
Add mediatek,mt8183-jpgenc compatible to binding document.
Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
---
.../devicetree/bindings/media/mediatek-jpeg-encoder.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml
index 28f26e79fcb3a..e4e791d76cdaa 100644
--- a/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml
+++ b/Documentation/devicetree/bindings/media/mediatek-jpeg-encoder.yaml
@@ -17,6 +17,7 @@ properties:
items:
- enum:
- mediatek,mt2701-jpgenc
+ - mediatek,mt8183-jpgenc
- const: mediatek,mtk-jpgenc
reg:
maxItems: 1
--
2.32.0.272.g935e593368-goog
next prev parent reply other threads:[~2021-06-11 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 11:20 [PATCH v4 1/3] dt-bindings: mediatek: convert mtk jpeg decoder/encoder to yaml Hsin-Yi Wang
2021-06-11 11:20 ` Hsin-Yi Wang [this message]
2021-06-11 13:47 ` [PATCH v4 2/3] dt-bindings: mediatek: Add mediatek,mt8183-jpgenc compatible Matthias Brugger
2021-06-11 11:20 ` [PATCH v4 3/3] arm64: dts: mt8183: add jpeg enc node for mt8183 Hsin-Yi Wang
2021-06-11 17:55 ` [PATCH v4 1/3] dt-bindings: mediatek: convert mtk jpeg decoder/encoder to yaml Rob Herring
2021-06-11 17:59 ` 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=20210611112009.2955944-2-hsinyi@chromium.org \
--to=hsinyi@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=yong.wu@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;
as well as URLs for NNTP newsgroup(s).