public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>,
	mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, hverkuil+cisco@kernel.org
Cc: sakari.ailus@linux.intel.com, bparrot@ti.com,
	jai.luthra@ideasonboard.com, dale@farnsworth.org,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, u-kumar1@ti.com,
	Sukrut Bellary <sbellary@baylibre.com>
Subject: Re: [PATCH V3 4/5] dt-bindings: media: ti: vpe: Add support for Video Input Port
Date: Mon, 13 Oct 2025 08:26:50 +0200	[thread overview]
Message-ID: <3038fee4-f2a2-4fba-a1a1-d7ec00128d8c@kernel.org> (raw)
In-Reply-To: <7d183747-af9e-4607-8219-e89ddcb79654@ti.com>

On 13/10/2025 08:21, Yemike Abhilash Chandra wrote:
>>> +examples:
>>> +  - |
>>> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
>>> +    #include <dt-bindings/interrupt-controller/irq.h>
>>> +
>>> +    vip1: video@48970000 {
>>> +        compatible = "ti,dra7-vip";
>>> +        reg = <0x48970000 0x114>,
>>> +              <0x48975500 0xD8>,
>>> +              <0x48975700 0x18>,
>>> +              <0x48975800 0x80>,
>>> +              <0x48975a00 0xD8>,
>>> +              <0x48975c00 0x18>,
>>> +              <0x48975d00 0x80>,
>>
>> Are you really, REALLY sure these are separate address spaces? Some
>> people thing that gaps means address space finishes...
>>
>>
>> How does your datasheet define these?
>>
> 
> These are not separate address spaces. The datasheet defines them as a
> single address region: VIP1 (0x4897_0000 –> 0x4897_FFFF, 64 KiB).
> 
> We created three common libraries sc.c (scalar), csc.c (color space 
> converter),
> and vpdma.c, which are used by both VPE and VIP drivers. The helper 
> functions
> in these libraries were originally written in a way that assumes sc0, csc0,
> sc1, and csc1 are separate address spaces. Since VPE has already been
> upstreamed using this approach. I have tried to use the same kind of 
> approach.
> But I now understand that, this might not be correct to define these as 
> separate
> address spaces.


Your previous driver choices should not matter. You are describing here
hardware, not drivers. Especially not previous drivers.

> 
> One solution would be to rewrite these helpers and update both VPE and
> VIP accordingly, but changing these helpers now may risk breaking backward
> compatibility for VPE.

Don't care. Describe properly hardware.

> 
> Alternatively, we could make the VIP driver standalone by avoiding the 
> use of these
> helpers. I was able to achieve this for csc.c and sc.c, but for vpdma.c, 
> I had to
> export a specific function from vpdma.c, since the VIP driver no longer 
> relies on the
> helpers provided by vpdma.c (In the previous approach the helper would 
> call this function)

Again, describe hardware, not drivers.


Best regards,
Krzysztof

  reply	other threads:[~2025-10-13  6:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  8:07 [PATCH V3 0/5] Add support for TI VIP Yemike Abhilash Chandra
2025-09-09  8:07 ` [PATCH V3 1/5] Revert "media: platform: ti: Remove unused vpdma_update_dma_addr" Yemike Abhilash Chandra
2025-09-09  8:21   ` Krzysztof Kozlowski
2025-09-09  8:07 ` [PATCH V3 2/5] media: platform: ti: Add kerneldoc for vpdma_update_dma_addr() Yemike Abhilash Chandra
2025-09-09  8:22   ` Krzysztof Kozlowski
2025-09-09  8:07 ` [PATCH V3 3/5] media: platform: ti: Switch to EXPORT_SYMBOL_GPL() Yemike Abhilash Chandra
2025-09-09  8:24   ` Krzysztof Kozlowski
2025-09-09  8:07 ` [PATCH V3 4/5] dt-bindings: media: ti: vpe: Add support for Video Input Port Yemike Abhilash Chandra
2025-09-09  8:36   ` Krzysztof Kozlowski
2025-10-13  6:21     ` Yemike Abhilash Chandra
2025-10-13  6:26       ` Krzysztof Kozlowski [this message]
2025-09-09  8:07 ` [PATCH V3 5/5] media: ti-vpe: Add the VIP driver Yemike Abhilash Chandra

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=3038fee4-f2a2-4fba-a1a1-d7ec00128d8c@kernel.org \
    --to=krzk@kernel.org \
    --cc=bparrot@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=dale@farnsworth.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil+cisco@kernel.org \
    --cc=jai.luthra@ideasonboard.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sbellary@baylibre.com \
    --cc=u-kumar1@ti.com \
    --cc=y-abhilashchandra@ti.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