All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
To: linux-media@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org
Subject: [PATCH/RFC 4/9] v4l: vsp1: VSPD instances have no LUT on Gen3
Date: Fri, 12 Feb 2016 04:00:45 +0200	[thread overview]
Message-ID: <1455242450-24493-5-git-send-email-laurent.pinchart+renesas@ideasonboard.com> (raw)
In-Reply-To: <1455242450-24493-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Remove the HAS_LUT flag in the corresponding device information entry.

Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
---
 drivers/media/platform/vsp1/vsp1_drv.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/media/platform/vsp1/vsp1_drv.c b/drivers/media/platform/vsp1/vsp1_drv.c
index 25750a0e4631..da43e3f35610 100644
--- a/drivers/media/platform/vsp1/vsp1_drv.c
+++ b/drivers/media/platform/vsp1/vsp1_drv.c
@@ -623,7 +623,7 @@ static const struct vsp1_device_info vsp1_device_infos[] = {
 		.uapi = true,
 	}, {
 		.version = VI6_IP_VERSION_MODEL_VSPD_GEN3,
-		.features = VSP1_HAS_BRU | VSP1_HAS_LIF | VSP1_HAS_LUT,
+		.features = VSP1_HAS_BRU | VSP1_HAS_LIF,
 		.rpf_count = 5,
 		.wpf_count = 2,
 		.num_bru_inputs = 5,
-- 
2.4.10


  parent reply	other threads:[~2016-02-12  2:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12  2:00 [PATCH/RFC 0/9] FCP support for Renesas video cores Laurent Pinchart
2016-02-12  2:00 ` [PATCH/RFC 1/9] clk: shmobile: r8a7795: Add FCP clocks Laurent Pinchart
2016-02-15  9:22   ` Geert Uytterhoeven
2016-02-15 12:26     ` Laurent Pinchart
2016-02-26 10:55   ` Laurent Pinchart
2016-03-01  1:03     ` Kuninori Morimoto
2016-03-03  0:17       ` Kuninori Morimoto
2016-03-03  6:52         ` Laurent Pinchart
2016-03-03  7:19           ` Kuninori Morimoto
2016-03-03  7:31             ` Laurent Pinchart
2016-03-03  8:37               ` Kuninori Morimoto
2016-03-03 10:49                 ` Laurent Pinchart
2016-03-03 11:56                   ` Geert Uytterhoeven
2016-03-03 12:04                     ` Laurent Pinchart
2016-04-12  6:27       ` Kuninori Morimoto
2016-02-12  2:00 ` [PATCH/RFC 2/9] clk: shmobile: r8a7795: Add LVDS module clock Laurent Pinchart
2016-02-15  9:24   ` Geert Uytterhoeven
2016-02-15 12:27     ` Laurent Pinchart
2016-02-12  2:00 ` [PATCH/RFC 3/9] v4l: Add Renesas R-Car FCP driver Laurent Pinchart
2016-02-15  9:32   ` Geert Uytterhoeven
2016-02-15 12:35     ` Laurent Pinchart
2016-02-26 13:20       ` Geert Uytterhoeven
2016-02-12  2:00 ` Laurent Pinchart [this message]
2016-02-12  2:00 ` [PATCH/RFC 5/9] v4l: vsp1: Add FCP support Laurent Pinchart
2016-02-12  2:00 ` [PATCH/RFC 6/9] ARM64: renesas: r8a7795: Add FCPV nodes Laurent Pinchart
2016-02-15  9:45   ` Geert Uytterhoeven
2016-02-15 12:50     ` Laurent Pinchart
2016-02-12  2:00 ` [PATCH/RFC 7/9] ARM64: renesas: r8a7795: Add VSP instances Laurent Pinchart
2016-02-15  9:58   ` Geert Uytterhoeven
2016-02-15 12:53     ` Laurent Pinchart
2016-02-12  2:00 ` [PATCH/RFC 8/9] ARM64: renesas: r8a7795: Add DU device to DT Laurent Pinchart
2016-02-12  2:00 ` [PATCH/RFC 9/9] ARM64: renesas: salvator-x: Enable DU Laurent Pinchart

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=1455242450-24493-5-git-send-email-laurent.pinchart+renesas@ideasonboard.com \
    --to=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    /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.