From: Benoit Parrot <bparrot@ti.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Tony Lindgren <tony@atomide.com>, Tero Kristo <t-kristo@ti.com>
Cc: <linux-omap@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-media@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Benoit Parrot <bparrot@ti.com>
Subject: [Patch v2 5/5] media: ti-vpe: vpe: fix compatible to match bindings
Date: Mon, 4 Nov 2019 14:38:41 -0600 [thread overview]
Message-ID: <20191104203841.3628-6-bparrot@ti.com> (raw)
In-Reply-To: <20191104203841.3628-1-bparrot@ti.com>
Update the compatible string to match the updated bindings.
Signed-off-by: Benoit Parrot <bparrot@ti.com>
---
drivers/media/platform/ti-vpe/vpe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/ti-vpe/vpe.c b/drivers/media/platform/ti-vpe/vpe.c
index b54f637633a7..65c2c048b018 100644
--- a/drivers/media/platform/ti-vpe/vpe.c
+++ b/drivers/media/platform/ti-vpe/vpe.c
@@ -2644,7 +2644,7 @@ static int vpe_remove(struct platform_device *pdev)
#if defined(CONFIG_OF)
static const struct of_device_id vpe_of_match[] = {
{
- .compatible = "ti,vpe",
+ .compatible = "ti,dra7-vpe",
},
{},
};
--
2.17.1
prev parent reply other threads:[~2019-11-04 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 20:38 [Patch v2 0/5] ARM: dts: dra7: add vpe nodes Benoit Parrot
2019-11-04 20:38 ` [Patch v2 1/5] dt-bindings: media: ti-vpe: Document VPE driver Benoit Parrot
2019-11-05 23:05 ` Rob Herring
2019-11-04 20:38 ` [Patch v2 2/5] clk: ti: dra7: add vpe clkctrl data Benoit Parrot
2019-11-04 20:38 ` [Patch v2 3/5] ARM: dts: dra7: add vpe clkctrl node Benoit Parrot
2019-11-08 16:55 ` Tony Lindgren
2019-11-08 17:02 ` Benoit Parrot
2019-11-08 17:06 ` Tony Lindgren
2019-11-04 20:38 ` [Patch v2 4/5] ARM: dts: dra7: Add ti-sysc node for VPE Benoit Parrot
2019-11-04 20:38 ` Benoit Parrot [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=20191104203841.3628-6-bparrot@ti.com \
--to=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).