Re: [PATCH 04/13] media: qcom: camss: csiphy: Add an init callback to CSI PHY devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/08/2024 15:02, Depeng Shao wrote:
I'm updating the code based on above comments, but I meet crash issue if I move the offset assignment to csiphy_gen2_config_lanes, since the csiphy->res->hw_ops->reset(csiphy) is called earlier than csiphy_gen2_config_lanes, so if we don't have the .init interface, we only can move this offset value to `struct csiphy_subdev_resources`, but if we add the offset to `struct csiphy_subdev_resources`, then below two patches are also can be dropped.


[PATCH 05/13] media: qcom: camss: csiphy-3ph: Move CSIPHY variables to data field inside csiphy struct [PATCH 06/13] media: qcom: camss: csiphy-3ph: Use an offset variable to find common control regs


Could you please comment on if I need to add the CSI_COMMON_CTR offset to res directly?
Or add back the .init interface?

Ah, I hadn't recalled why the .init was added -> because sequencing.

Lets retain the patch but expand the commit log to explain why the init is being added, instead of jumping through hoops to restructure to get rid of it.

---
bod




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux