From: "Du, Bin" <bin.du@amd.com>
To: Mario Limonciello <superm1@kernel.org>,
Sashank Karri <sashank.karri@gmail.com>
Cc: Dominic.Antony@amd.com, Phil.Jawich@amd.com, anson.tsao@amd.com,
benjamin.chan@amd.com, bryan.odonoghue@linaro.org,
gjorgji.rosikopulos@amd.com, hverkuil@xs4all.nl, king.li@amd.com,
laurent.pinchart+renesas@ideasonboard.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
mario.limonciello@amd.com, mchehab@kernel.org,
prabhakar.mahadev-lad.rj@bp.renesas.com, pratap.nirujogi@amd.com,
richard.gong@amd.com, sakari.ailus@linux.intel.com,
sultan@kerneltoast.com, "Adam J. Sypniewski" <ajsyp@syptech.net>
Subject: Re: [PATCH v6 0/7] Add AMD ISP4 driver
Date: Mon, 1 Dec 2025 14:46:54 +0800 [thread overview]
Message-ID: <17db5acd-2bb7-45cf-b8e4-b796c49e3baf@amd.com> (raw)
In-Reply-To: <3a671359-b05a-4d58-84ca-f29385088e5c@kernel.org>
On 12/1/2025 10:43 AM, Mario Limonciello wrote:
> + "Adam J. Sypniewski" <ajsyp@syptech.net>
>
> On 11/28/25 9:12 PM, Sashank Karri wrote:
>> Dear Bin,
>>
>> I apologize if this is the wrong place to ask this question and
>> suggest this very slight edit if I understand how ISP4 on the Ryzen AI
>> Max+ 300 series SoCs works. So the ASUS Rog Flow Z13 2025 also uses
>> the same Strix Halo chips, albeit using the non-PRO series. On the
>> Windows side, the 13MP sensor, also from Omnivision, requires an AMD
>> Camera Driver, something speciifcally also required by the 5.2 MP
>> camera on the HP ZBook Ultra G1a. So if both MIPI-capable cameras use
>> the ISP4 technology on the Strix Halo SoC (do they?), this Linux ISP4
>> driver should apply to both cameras, right? If so, shouldn't the ACPI
>> ID for the 13MP sensor also be hardcoded into this code
>>
>>> drm/amd/amdgpu: Declare isp firmware binary file (https://
>>> gitlab.freedesktop.org/agd5f/linux/-/
>>> commit/35345917bc9f7c86152b270d9d93c220230b667f)
>>
>> Adam J. Sypniewski suggested hardcoding the ACPI ID into the I2C
>> driver here to have the 13MP camera to work (the ASUS specific ACPI ID
>> for the sensor can be found here):
>> https://lore.kernel.org/lkml/aPeqy11m-TxwbzJV@garrus/
>
> Two things:
>
> 1) Does this work? I wouldn't expect it's enough to make everything
> work 100%.
>
> 2) AFAICT the Flow Z13 has a USB camera for the front camera, but the
> rear camera is the one that uses the ISP4.
>
> So I'm confused by the commit message saying that the front facing
> camera needs it. Is that a mistake?
>
>>
>> I'm entirely new to the Linux kernel mailing list and very unfamiliar
>> with webcam interfaces and how ASUS has chosen to interface the 13 MP
>> sensor with the system, but I can confirm that it does not work yet in
>> the Linux desktop, so I was wondering if the work on this new driver
>> is necessary to get it to work.
>>
>> Sashank
>>
>
> I think it's going to be a bit more than just an ACPI ID the ISP4 driver
> though to enable it however. amdgpu has a list of sensors that it
> supports (you can see isp_v4_1_1.c for details). This currently only
> will recognize and configure the GPIOs for ACPI _HID OMNI5C10.
>
> For ACPI _HID OMNI13B1 a new entry would be needed there along with the
> correct GPIO tables that match. This will wire up the pinctrl-amdisp
> driver to have the right GPIOs.
>
> Bin and Pratap can comment more on the feasibility. But for now I think
> we should treat this as TODO for after the initial series lands with
> support for the sensor in the HP ZBook Ultra G1a.
Thanks, Mario. Some more comments, Windows and Linux have different
architectures. Windows uses ISP and dedicated sensor drivers, while
Linux places all sensor initialization and control in the ISP firmware,
functioning like a webcam. Adding new sensors requires updates to both
the ISP firmware and kernel drivers. For now, only Ov05c10 is supported
on HP ZBook Ultra G1a.
--
Regards,
Bin
next prev parent reply other threads:[~2025-12-01 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 3:12 [PATCH v6 0/7] Add AMD ISP4 driver Sashank Karri
2025-12-01 2:43 ` Mario Limonciello
2025-12-01 6:46 ` Du, Bin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-28 9:19 Bin Du
2025-11-29 3:09 ` Sultan Alsawaf
2025-12-01 6:16 ` Du, Bin
2025-12-02 7:22 ` Sultan Alsawaf
2025-12-03 8:19 ` Du, Bin
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=17db5acd-2bb7-45cf-b8e4-b796c49e3baf@amd.com \
--to=bin.du@amd.com \
--cc=Dominic.Antony@amd.com \
--cc=Phil.Jawich@amd.com \
--cc=ajsyp@syptech.net \
--cc=anson.tsao@amd.com \
--cc=benjamin.chan@amd.com \
--cc=bryan.odonoghue@linaro.org \
--cc=gjorgji.rosikopulos@amd.com \
--cc=hverkuil@xs4all.nl \
--cc=king.li@amd.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mchehab@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=pratap.nirujogi@amd.com \
--cc=richard.gong@amd.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sashank.karri@gmail.com \
--cc=sultan@kerneltoast.com \
--cc=superm1@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