From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jacopo Mondi <jacopo+renesas@jmondi.org>
Cc: koji.matsuoka.xm@renesas.com,
niklas.soderlund+renesas@ragnatech.se,
laurent.pinchart@ideasonboard.com, linux-media@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 0/2] media: rcar-vin: Mask access to VNCSI_IFMD register
Date: Thu, 3 Dec 2020 07:58:30 +0100 [thread overview]
Message-ID: <20201203075830.2701c8b5@coco.lan> (raw)
In-Reply-To: <20201126074757.2768-1-jacopo+renesas@jmondi.org>
Em Thu, 26 Nov 2020 08:47:55 +0100
Jacopo Mondi <jacopo+renesas@jmondi.org> escreveu:
> As reported in patch 2/2 commit message the the VNCSI_IFMD register
> has the following limitations according to chip manual revision 2.20
>
> - V3M, V3H and E3 do not support the DES1 field has they do not feature
> a CSI20 receiver.
> - D3 only supports parallel input, and the whole register shall always
> be written as 0.
>
> This patch upports the BSP change commit f54697394457
> ("media: rcar-vin: Fix VnCSI_IFMD register access for r8a77990") from
> Koji Matsuoka
As checkpatch warned:
-:22: WARNING: Unknown commit id 'f54697394457', maybe rebased or not pulled?
There's no such commit upstream. Are you referring to an OOT patch?
If so, you should provide an URL from where the patch is stored,
as otherwise this comment won't make any sense upstream.
If you can't provide such URL, please adjust the comment to provide
a description that won't be dependent of such OOT commit.
>
> Tested on r-car E3 Ebisu.
>
> v2 -> v3:
> - Remove a few comments and add Niklas' tag to [2/2]
>
> v1 -> v2:
> - Inspect the channel routing table to deduce the availability of DES1/DES0
> bits as suggested by Niklas.
>
> Jacopo Mondi (2):
> media: rcar-vin: Remove unused macro
> media: rcar-vin: Mask VNCSI_IFMD register
>
> drivers/media/platform/rcar-vin/rcar-dma.c | 26 ++++++++++++++++++----
> 1 file changed, 22 insertions(+), 4 deletions(-)
>
> --
> 2.29.1
>
Thanks,
Mauro
next prev parent reply other threads:[~2020-12-03 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 7:47 [PATCH v3 0/2] media: rcar-vin: Mask access to VNCSI_IFMD register Jacopo Mondi
2020-11-26 7:47 ` [PATCH v3 1/2] media: rcar-vin: Remove unused macro Jacopo Mondi
2020-11-26 7:47 ` [PATCH v3 2/2] media: rcar-vin: Mask VNCSI_IFMD register Jacopo Mondi
2020-12-03 6:58 ` Mauro Carvalho Chehab [this message]
2020-12-03 7:06 ` [PATCH v3 0/2] media: rcar-vin: Mask access to " Hans Verkuil
2020-12-03 7:08 ` Hans Verkuil
2020-12-03 7:52 ` Mauro Carvalho Chehab
2020-12-03 8:33 ` Geert Uytterhoeven
2020-12-03 9:20 ` Jacopo Mondi
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=20201203075830.2701c8b5@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=jacopo+renesas@jmondi.org \
--cc=koji.matsuoka.xm@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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