From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Keke Li <keke.li@amlogic.com>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Conor Dooley <conor+dt@kernel.org>,
Keke Li via B4 Relay <devnull+keke.li.amlogic.com@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, laurent.pinchart@ideasonboard.com,
dan.scally@ideasonboard.com, jacopo.mondi@ideasonboard.com
Subject: Re: [PATCH v7 00/10] Amlogic C3 ISP support
Date: Thu, 3 Apr 2025 08:01:18 +0200 [thread overview]
Message-ID: <2e2c30f9-a9f5-475f-8acb-b84c2776ba5f@linaro.org> (raw)
In-Reply-To: <ae77936c-e9a7-432f-89a0-b4b7574690ea@amlogic.com>
On 03/04/2025 03:58, Keke Li wrote:
> Hi Kieran
>
> Thanks for your reply.
>
> On 2025/4/3 01:01, Kieran Bingham wrote:
>> [ EXTERNAL EMAIL ]
>>
>> Hi all,
>>
>> Quoting Keke Li via B4 Relay (2025-03-11 09:11:10)
>>> The Amlogic C3 platform integrates an ISP capable of supporting
>>> multi-camera, multi-exposure high dynamic range (HDR) imaging with up to
>>> 14-bit raw RGB Bayer data.
>>>
>>> Capturing images on the C3 involves operating the CSI2 receiver and PHY,
>>> an adapter layer that integrates the inline processing from the PHY to
>>> the ISP, and the ISP driver itself.
>>>
>>> This implementation consists of several distinct module drivers and
>>> is expected to support different platforms in the future.
>>>
>> There is a corresponding series for libcamera based on this kernel
>> support.
>>
>> I chased to see what's needed to get this ISP driver merged, and saw
>> that the CI couldn't apply the patches. Does this need to be resent on a
>> specific base to support the CI?
>>
>> (https://patchwork.linuxtv.org/project/linux-media/list/?series=14706)
>>
>> https://patchwork.linuxtv.org/project/linux-media/patch/20250311-c3isp-v7-10-c3551bed9005@amlogic.com/
>> shows the CI failure : "Failed to cherry-pick patch series "
>
> This patch series is based on "linux-next specific files for 20250307".
> I am preparing the next version.
Please kindly trim the replies from unnecessary context. It makes it
much easier to find new content.
Why quoting entire 10k lines message below?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-03 6:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 9:11 [PATCH v7 00/10] Amlogic C3 ISP support Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 01/10] dt-bindings: media: Add amlogic,c3-mipi-csi2.yaml Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 02/10] media: platform: Add C3 MIPI CSI-2 driver Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 03/10] dt-bindings: media: Add amlogic,c3-mipi-adapter.yaml Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 04/10] media: platform: Add C3 MIPI adapter driver Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 05/10] dt-bindings: media: Add amlogic,c3-isp.yaml Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 06/10] media: Add C3ISP_PARAMS and C3ISP_STATS meta formats Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 07/10] media: uapi: Add stats info and parameters buffer for C3 ISP Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 08/10] media: platform: Add C3 ISP driver Keke Li via B4 Relay
2025-03-29 10:23 ` Markus Elfring
2025-03-31 2:09 ` Keke Li
2025-03-31 3:17 ` Keke Li
2025-03-31 6:10 ` [v7 " Markus Elfring
2025-03-31 10:53 ` Keke Li
2025-03-11 9:11 ` [PATCH v7 09/10] Documentation: media: add documentation file metafmt-c3-isp.rst Keke Li via B4 Relay
2025-03-11 9:11 ` [PATCH v7 10/10] Documentation: media: add documentation file c3-isp.rst Keke Li via B4 Relay
2025-04-02 17:01 ` [PATCH v7 00/10] Amlogic C3 ISP support Kieran Bingham
2025-04-03 1:58 ` Keke Li
2025-04-03 6:01 ` Krzysztof Kozlowski [this message]
2025-04-07 1:58 ` Keke Li
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=2e2c30f9-a9f5-475f-8acb-b84c2776ba5f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=devnull+keke.li.amlogic.com@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=keke.li@amlogic.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
/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).