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 v3 5/5] media: ti-vpe: vpe: fix compatible to match bindings
Date: Wed, 6 Nov 2019 14:26:22 -0600 [thread overview]
Message-ID: <20191106202622.2648-6-bparrot@ti.com> (raw)
In-Reply-To: <20191106202622.2648-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
WARNING: multiple messages have this Message-ID (diff)
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 v3 5/5] media: ti-vpe: vpe: fix compatible to match bindings
Date: Wed, 6 Nov 2019 14:26:22 -0600 [thread overview]
Message-ID: <20191106202622.2648-6-bparrot@ti.com> (raw)
In-Reply-To: <20191106202622.2648-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
WARNING: multiple messages have this Message-ID (diff)
From: Benoit Parrot <bparrot@ti.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Tony Lindgren <tony@atomide.com>, Tero Kristo <t-kristo@ti.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Benoit Parrot <bparrot@ti.com>, Rob Herring <robh+dt@kernel.org>,
linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [Patch v3 5/5] media: ti-vpe: vpe: fix compatible to match bindings
Date: Wed, 6 Nov 2019 14:26:22 -0600 [thread overview]
Message-ID: <20191106202622.2648-6-bparrot@ti.com> (raw)
In-Reply-To: <20191106202622.2648-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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-11-06 20:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 20:26 [Patch v3 0/5] ARM: dts: dra7: add vpe nodes Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` [Patch v3 1/5] dt-bindings: media: ti-vpe: Document VPE driver Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` [Patch v3 2/5] clk: ti: dra7: add vpe clkctrl data Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` [Patch v3 3/5] ARM: dts: dra7: add vpe clkctrl node Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` [Patch v3 4/5] ARM: dts: dra7: Add ti-sysc node for VPE Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot [this message]
2019-11-06 20:26 ` [Patch v3 5/5] media: ti-vpe: vpe: fix compatible to match bindings Benoit Parrot
2019-11-06 20:26 ` Benoit Parrot
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=20191106202622.2648-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.