Re: [PATCH 1/2] dt-bindings: media: add axiado,ax3000-video

[Krzysztof Kozlowski <krzk@kernel.org>]

On Tue, Aug 04, 2026 at 07:31:25AM +0800, Tzu-Hao Wei wrote:
> >> There is no local register interface for this driver to program: frame
> >> delivery is controlled entirely by the host-side display engine and
> >> the PCIe endpoint mapping that feeds the shared region, both external
> >> to this driver. A software polling timer schedules a workqueue item at
> >> the configured framerate, which copies frames from the WC-mapped
> >> shared region into vmalloc-backed vb2 buffers. Running the copy in a
> >> work item rather than directly in the timer callback keeps potentially
> >> multi-megabyte memcpy and per-pixel conversion work out of softirq
> >> context.
> > 
> > Then this is not a separate device. You just described a Linux driver.
> > 
> > I still wait for answers of my question above. You described getting
> > buffers only.
> > 
> 
> Thank you for the continued review.
> 
> To correctly represent this in device tree without describing a
> software driver as a hardware device, would moving the schema into
> /reserved-memory be the preferred approach for v2?
> 
> Specifically, we are considering moving it to:
> Documentation/devicetree/bindings/reserved-memory/axiado,ax3000-video-mem.yaml

I would rather suggest this should be part of the device handling the
host side of the device. Or is there none?

Again, how do you configure the frame parameters or start capturing the
data?

> 
> This would follow the same Devicetree architectural pattern as
> qcom,rmtfs-mem:
> Documentation/devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml
> 
> Just as qcom,rmtfs-mem describes a reserved memory buffer used by
> remote processors and exports /dev/rmtfs_mem%d without hardware MMIO
> registers, clocks, or resets, axiado,ax3000-video describes the
> reserved memory buffer used by the AX3000 display pipeline and exports
> /dev/video0.
> 
> Does representing axiado,ax3000-video as a reserved-memory node look
> like the appropriate way to model this in v2?

So from a device we went now to pure memory... That's quite a change and
would prove this was completely bogus hardware description.

I actually fail to see any hardware here, because you could just
allocate whatever memory and pass it to your host, no? Why it has to be
a reserved memory?

Best regards,
Krzysztof