From: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: <linux-media@vger.kernel.org>, Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [RFC PATCH] media: ti: cal: Deprecate non-MC API usage
Date: Wed, 2 Sep 2026 20:23:16 +0530 [thread overview]
Message-ID: <561ff30f-6119-4698-a719-139bf279ea10@ti.com> (raw)
In-Reply-To: <20260902122454.GA335893@killaraus.ideasonboard.com>
Hi Laurent,
Thanks for the patch.
On 02/09/26 17:54, Laurent Pinchart wrote:
> Yemike, are you fine with this patch ?
>
Yes, I apologize for missing this.
Reviewed-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Thanks and regards,
Yemike Abhilash Chandra
> On Tue, Jul 28, 2026 at 03:26:47PM +0300, Tomi Valkeinen wrote:
>> On 23/07/2026 14:19, Laurent Pinchart wrote:
>>> The MC API was introduced in the CAL driver more than five years ago in
>>> commit 38e89e790fe2 ("media: ti-vpe: cal: Implement media controller
>>> centric API") as a disabled by default option. Five years later, it's
>>> time to give users another nudge to move to the MC API. Deprecate non-MC
>>> API usage by printing a warning at probe time, and defaulting to the MC
>>> API. The legacy API can still be selected through the mc_api module
>>> parameter.
>>>
>>> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>>> ---
>>> drivers/media/platform/ti/Kconfig | 11 -----------
>>> drivers/media/platform/ti/cal/cal.c | 10 +++-------
>>> 2 files changed, 3 insertions(+), 18 deletions(-)
>>
>> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
>
next prev parent reply other threads:[~2026-09-02 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 11:19 [RFC PATCH] media: ti: cal: Deprecate non-MC API usage Laurent Pinchart
2026-07-28 12:26 ` Tomi Valkeinen
2026-09-02 12:24 ` Laurent Pinchart
2026-09-02 14:53 ` Yemike Abhilash Chandra [this message]
2026-09-02 15:14 ` Laurent Pinchart
2026-09-02 19:18 ` Sakari Ailus
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=561ff30f-6119-4698-a719-139bf279ea10@ti.com \
--to=y-abhilashchandra@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=tomi.valkeinen@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.