From: Krzysztof Kozlowski <krzk@kernel.org>
To: yuji2.ishikawa@toshiba.co.jp, laurent.pinchart@ideasonboard.com,
mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, sakari.ailus@linux.intel.com,
hverkuil-cisco@xs4all.nl, nobuhiro1.iwamatsu@toshiba.co.jp
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v12 1/8] dt-bindings: media: platform: visconti: Add Toshiba Visconti MIPI CSI-2 Receiver
Date: Tue, 17 Dec 2024 06:44:58 +0100 [thread overview]
Message-ID: <cb6be804-1649-4d17-839c-fe58a39baa1d@kernel.org> (raw)
In-Reply-To: <TY3PR01MB9982FE7739FABB2275C79C0B923B2@TY3PR01MB9982.jpnprd01.prod.outlook.com>
On 17/12/2024 00:57, yuji2.ishikawa@toshiba.co.jp wrote:
>> On 25/11/2024 10:21, Yuji Ishikawa wrote:
>>> Adds the Device Tree binding documentation that allows to describe the
>>> MIPI CSI-2 Receiver found in Toshiba Visconti SoCs.
>>>
>>> Signed-off-by: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
>>> Reviewed-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
>>
>>
>> How newly added patch can have already Rb tag? Was this review really, really
>> performed internally or you just satisfy some internal managers requirements
>> and fake the stats?
>>
>
> I added this Reviewed-by tag because the patch was reviewed internally.
What issues were identified by internal review, especially in the
context of bindings?
>
>>> ---
>>>
>>> Changelog v12:
>>> - Newly add bindings for CSI2RX driver
>>>
>>> .../media/toshiba,visconti5-csi2rx.yaml | 104
>> ++++++++++++++++++
>>> 1 file changed, 104 insertions(+)
>>> create mode 100644
>>> Documentation/devicetree/bindings/media/toshiba,visconti5-csi2rx.yaml
>>>
>>> diff --git
>>> a/Documentation/devicetree/bindings/media/toshiba,visconti5-csi2rx.yam
>>> l
>>> b/Documentation/devicetree/bindings/media/toshiba,visconti5-csi2rx.yam
>>> l
>>> new file mode 100644
>>> index 000000000000..5488072bc82a
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/media/toshiba,visconti5-csi2rx
>>> +++ .yaml
>>> @@ -0,0 +1,104 @@
>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2
>>> +---
>>> +$id:
>>> +http://devicetree.org/schemas/media/toshiba,visconti5-csi2rx.yaml#
>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>> +
>>> +title: Toshiba Visconti5 SoC MIPI CSI-2 receiver
>>> +
>>> +maintainers:
>>> + - Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
>>> +
>>> +description: |-
>>
>> Drop |-
>>
>
> I'll drop "|-"
>
>>> + Toshiba Visconti5 SoC MIPI CSI-2 receiver device receives MIPI
>>> + CSI-2 video stream. Use with VIIF device. T.B.D
>>> +
>>> +properties:
>>> + compatible:
>>> + const: toshiba,visconti5-csi2rx
>>
>> Why this is called "RX"? Can you have a TX? I had impression that one cannot.
>>
>
> VIIF has only MIPI CSI2 receiver (CSI2RX). There's no TX for it.
So this device cannot be anything else? Then drop rx.
> Visconti also has VOIF (Video Output Interface) hardware which has MIPI CSI2 (not DSI) transmitter (CSI2TX).
Or this can be something else? Confusing.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-17 5:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 9:21 [PATCH v12 0/8] Add Toshiba Visconti Video Input Interface driver Yuji Ishikawa
2024-11-25 9:21 ` [PATCH v12 1/8] dt-bindings: media: platform: visconti: Add Toshiba Visconti MIPI CSI-2 Receiver Yuji Ishikawa
2024-11-25 10:11 ` Krzysztof Kozlowski
2024-12-16 23:57 ` yuji2.ishikawa
2024-12-17 5:44 ` Krzysztof Kozlowski [this message]
2024-12-24 0:17 ` yuji2.ishikawa
2024-12-26 16:15 ` Laurent Pinchart
2025-01-02 9:29 ` Laurent Pinchart
2025-01-20 0:10 ` yuji2.ishikawa
2024-11-25 9:21 ` [PATCH v12 2/8] dt-bindings: media: platform: visconti: Add Toshiba Visconti Video Input Interface Yuji Ishikawa
2024-11-25 10:07 ` Krzysztof Kozlowski
2024-12-17 0:00 ` yuji2.ishikawa
2024-12-17 5:43 ` Krzysztof Kozlowski
2024-12-17 9:45 ` Laurent Pinchart
2024-12-17 12:51 ` Krzysztof Kozlowski
2025-01-02 9:41 ` Laurent Pinchart
2024-12-24 0:17 ` yuji2.ishikawa
2025-01-02 9:56 ` Laurent Pinchart
2025-01-20 0:13 ` yuji2.ishikawa
2024-11-25 9:21 ` [PATCH v12 3/8] media: uapi: add visconti viif meta buffer format Yuji Ishikawa
2025-01-02 13:10 ` Laurent Pinchart
2025-01-20 0:15 ` yuji2.ishikawa
2025-01-20 1:49 ` Laurent Pinchart
2024-11-25 9:21 ` [PATCH v12 4/8] media: platform: visconti: Add Toshiba Visconti CSI-2 Receiver driver Yuji Ishikawa
2025-01-02 13:08 ` Laurent Pinchart
2025-01-20 0:21 ` yuji2.ishikawa
2024-11-25 9:21 ` [PATCH v12 7/8] documentation: media: add documentation for Toshiba Visconti Video Input Interface driver Yuji Ishikawa
2025-01-02 21:26 ` Laurent Pinchart
2025-02-05 12:29 ` yuji2.ishikawa
2025-04-15 9:01 ` yuji2.ishikawa
2025-06-18 1:30 ` yuji2.ishikawa
2024-11-25 9:21 ` [PATCH v12 8/8] MAINTAINERS: Add entries for Toshiba Visconti Video Input Interface Yuji Ishikawa
2025-01-02 13:16 ` Laurent Pinchart
2025-02-05 12:31 ` yuji2.ishikawa
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=cb6be804-1649-4d17-839c-fe58a39baa1d@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=yuji2.ishikawa@toshiba.co.jp \
/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).