Re: [PATCH v8 14/18] media: iris: implement support for the Agatti platform
Dmitry Baryshkov <[email protected]> Fri, 31 Jul 2026 02:37:09 +0300
| Newsgroups | dev.linux.lists.sashiko-reviews,org.kernel.vger.linux-devicetree |
|---|---|
| Message-ID | <tokophmqfjim6f4wrpwletnpojcasnn47prkww3k4nuz6byqwq@buuvvn7ls6j7> |
On Thu, Jul 30, 2026 at 03:54:44PM +0000, [email protected] wrote: > Thank you for your contribution! Sashiko AI review found 4 potential issue(s) to consider: > - [Critical] Mismatch between statically calculated vb2 buffer size and the firmware's requested buffer size causes a potential buffer overflow when the firmware writes to external buffers. I think the implementation is correct > - [High] Querying buffer requirements for AR50Lt overwrites the DPB buffer count (fw_min_count) with the display output buffer count. This is expected > - [High] The AR50LT platform uses `iris_vpu2_calculate_frequency` but provides capability fields intended for `iris_vpu3x_vpu4x_calculate_frequency`, resulting in severely under-calculated clock scaling. No, See codec_freq_data_lite, it also uses 0 for vsp > - [Medium] The hierarchical layer bitrates (LAYER0_BITRATE_H264 to LAYER5_BITRATE_H264) in `inst_fw_cap_gen1_ar50lt_enc` use the global `BITRATE_MAX` (160Mbps) instead of the AR50LT-specific limit. Corrected this one > -- > -- With best wishes Dmitry