From: Devarsh Thakkar <devarsht@ti.com>
To: Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: <mchehab@kernel.org>, <robh@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<hverkuil-cisco@xs4all.nl>, <linux-media@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<benjamin.gaignard@collabora.com>,
<laurent.pinchart@ideasonboard.com>, <praneeth@ti.com>,
<nm@ti.com>, <vigneshr@ti.com>, <a-bhatia1@ti.com>,
<j-luthra@ti.com>, <b-brnich@ti.com>, <detheridge@ti.com>,
<p-mantena@ti.com>, <vijayp@ti.com>, <andrzej.p@collabora.com>,
<nicolas@ndufresne.ca>, <afd@ti.com>, <milkfafa@gmail.com>
Subject: Re: [PATCH v6 1/3] media: dt-bindings: Add Imagination E5010 JPEG Encoder
Date: Thu, 29 Feb 2024 16:50:38 +0530 [thread overview]
Message-ID: <7a83fe91-5afa-6aee-a8a4-44f6e3d713c2@ti.com> (raw)
In-Reply-To: <20240229102623.ihwhbba4qwzvxzzq@basti-XPS-13-9310>
Hi Sebastian,
Thanks for the review.
On 29/02/24 15:56, Sebastian Fricke wrote:
> Hey Devarsh,
>
> On 28.02.2024 19:41, Devarsh Thakkar wrote:
>> Add dt-bindings for Imagination E5010 JPEG Encoder [1] which is implemented
>> as stateful V4L2 M2M driver.
>>
>> The device supports baseline encoding with two different quantization
>> tables and compression ratio as demanded.
>>
>> Minimum resolution supported is 64x64 and Maximum resolution supported is
>> 8192x8192.
>>
>> [1]: AM62A TRM (Section 7.6 is for JPEG Encoder)
>> Link: https://www.ti.com/lit/pdf/spruj16
>>
>> Co-developed-by: David Huang <d-huang@ti.com>
>> Signed-off-by: David Huang <d-huang@ti.com>
>> Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>
> hmmm when did Rob give his reviewed by on this patch? (As this is not a
> DT binding I find that odd)
[PATCH v6 1/3] media: dt-bindings: Add Imagination E5010 JPEG Encoder : This
is indeed the dt-binding patch. Also As shared in version history it is at V4
where Rob Herring added a Reviewed-By as seen here [0]
> And where is the Reviewed by tag from Benjamin that he provided on V5?
>
As captured in patch version history here [1] I thought to remove the
Reviewed-By since the Reviewed-By tag was on V5 and with V6 the driver got
updated with some changes to handle reported sparse warnings and so I have
asked Benjamin to check the range-diff and help with a quick review again if
possible.
Kindly let me know if I missed something or anything needs to be done from my end.
[0] :
https://lore.kernel.org/all/170716378412.295212.11603162949482063011.robh@kernel.org/
[1] : https://lore.kernel.org/all/20240228141140.3530612-4-devarsht@ti.com/
Regards
Devarsh
> Greetings,
> Sebastian
>
>> ---
>> V2: No change
>> V3:
>> - Add vendor specific compatible
>> - Update reg names
>> - Update clocks to 1
>> - Fix dts example with proper naming
>> V4:
>> - Use ti-specific compatible ti,am62a-jpeg-enc as secondary one
>> - Update commit message and title
>> - Remove clock-names as only single clock
>> V5:
>> - Add Reviewed-By tag
>> V6:
>> - No change
>>
>> .../bindings/media/img,e5010-jpeg-enc.yaml | 75 +++++++++++++++++++
>> MAINTAINERS | 5 ++
>> 2 files changed, 80 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/media/img,e5010-jpeg-enc.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/media/img,e5010-jpeg-enc.yaml
>> b/Documentation/devicetree/bindings/media/img,e5010-jpeg-enc.yaml
>> new file mode 100644
>> index 000000000000..085020cb9e61
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/img,e5010-jpeg-enc.yaml
>> @@ -0,0 +1,75 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/media/img,e5010-jpeg-enc.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Imagination E5010 JPEG Encoder
>> +
>> +maintainers:
>> + - Devarsh Thakkar <devarsht@ti.com>
>> +
>> +description: |
>> + The E5010 is a JPEG encoder from Imagination Technologies implemented on
>> + TI's AM62A SoC. It is capable of real time encoding of YUV420 and YUV422
>> + inputs to JPEG and M-JPEG. It supports baseline JPEG Encoding up to
>> + 8Kx8K resolution.
>> +
>> +properties:
>> + compatible:
>> + oneOf:
>> + - items:
>> + - const: ti,am62a-jpeg-enc
>> + - const: img,e5010-jpeg-enc
>> + - const: img,e5010-jpeg-enc
>> +
>> + reg:
>> + items:
>> + - description: The E5010 core register region
>> + - description: The E5010 mmu register region
>> +
>> + reg-names:
>> + items:
>> + - const: core
>> + - const: mmu
>> +
>> + power-domains:
>> + maxItems: 1
>> +
>> + resets:
>> + maxItems: 1
>> +
>> + clocks:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - reg-names
>> + - interrupts
>> + - clocks
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/soc/ti,sci_pm_domain.h>
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> +
>> + soc {
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> + jpeg-encoder@fd20000 {
>> + compatible = "img,e5010-jpeg-enc";
>> + reg = <0x00 0xfd20000 0x00 0x100>,
>> + <0x00 0xfd20200 0x00 0x200>;
>> + reg-names = "core", "mmu";
>> + clocks = <&k3_clks 201 0>;
>> + power-domains = <&k3_pds 201 TI_SCI_PD_EXCLUSIVE>;
>> + interrupts = <GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>;
>> + };
>> + };
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index e1475ca38ff2..6b34ee8d92b5 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -10572,6 +10572,11 @@ S: Maintained
>> F: Documentation/devicetree/bindings/auxdisplay/img,ascii-lcd.yaml
>> F: drivers/auxdisplay/img-ascii-lcd.c
>>
>> +IMGTEC JPEG ENCODER DRIVER
>> +M: Devarsh Thakkar <devarsht@ti.com>
>> +S: Supported
>> +F: Documentation/devicetree/bindings/media/img,e5010-jpeg-enc.yaml
>> +
>> IMGTEC IR DECODER DRIVER
>> S: Orphan
>> F: drivers/media/rc/img-ir/
>> --
>> 2.39.1
>>
next prev parent reply other threads:[~2024-02-29 11:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 14:11 [PATCH v6 0/3] Add V4L2 M2M Driver for " Devarsh Thakkar
2024-02-28 14:11 ` [PATCH v6 1/3] media: dt-bindings: Add Imagination " Devarsh Thakkar
2024-02-29 10:26 ` Sebastian Fricke
2024-02-29 11:20 ` Devarsh Thakkar [this message]
2024-02-29 13:30 ` Sebastian Fricke
2024-03-01 16:32 ` Devarsh Thakkar
2024-03-01 17:06 ` Sebastian Fricke
2024-03-06 15:57 ` Devarsh Thakkar
2024-03-07 12:05 ` Sebastian Fricke
2024-02-29 12:16 ` Krzysztof Kozlowski
2024-02-29 13:31 ` Sebastian Fricke
2024-02-28 14:11 ` [PATCH v6 2/3] media: jpeg: Add reference quantization and huffman tables Devarsh Thakkar
2024-03-18 13:39 ` Hans Verkuil
2024-02-28 14:11 ` [PATCH v6 3/3] media: imagination: Add E5010 JPEG Encoder driver Devarsh Thakkar
2024-03-18 14:15 ` Hans Verkuil
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=7a83fe91-5afa-6aee-a8a4-44f6e3d713c2@ti.com \
--to=devarsht@ti.com \
--cc=a-bhatia1@ti.com \
--cc=afd@ti.com \
--cc=andrzej.p@collabora.com \
--cc=b-brnich@ti.com \
--cc=benjamin.gaignard@collabora.com \
--cc=conor+dt@kernel.org \
--cc=detheridge@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=j-luthra@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=milkfafa@gmail.com \
--cc=nicolas@ndufresne.ca \
--cc=nm@ti.com \
--cc=p-mantena@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=sebastian.fricke@collabora.com \
--cc=vigneshr@ti.com \
--cc=vijayp@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
all inboxes | Powered by JetHome®