LKML Archive mirror
 help / color / mirror / Atom feed
* [PATCH v2 0/8] Move camss version related defs in to resources
@ 2024-03-19 17:39 Gjorgji Rosikopulos
  2024-03-19 17:39 ` [PATCH v2 1/8] media: qcom: camss: Add per sub-device type resources Gjorgji Rosikopulos
                   ` (8 more replies)
  0 siblings, 9 replies; 12+ messages in thread
From: Gjorgji Rosikopulos @ 2024-03-19 17:39 UTC (permalink / raw
  To: rfoss, todor.too, bryan.odonoghue, andersson, konrad.dybcio,
	mchehab
  Cc: linux-media, linux-arm-msm, linux-kernel, laurent.pinchart,
	hverkuil-cisco, quic_hariramp

The different resources required for different camss soc versions are
split in to two groups:

1. Camss device related. In this group are all resources described
in the device tree, clocks, regulators etc.

2. Sub-device specific resources. In the initialization
of the each sub-device, the version of camss is passed.
Based on this version the sub-device adds: hw layer support,
per pad formats, number of dma's etc.

The code for "1" group lives in camss.c. However the "2" group
is spread across all sub-device implementations including video device.

This kind of separation is not very convenient when adding new camss soc
version. The reason is that you need to add support in all sub-device
implementations.

There were some improvements in this direction where some of the
hw version related definitions were moved in to the "1". One
example is attaching of the hw operations.

This series aim to improve the things more and add additional definitions
in to the "1".

What is included:

- Remove all format definitions from camss video. The will be passed
  by the parent sub-device

- Make camss generic format definition mapping, containing mbus to
  v4l2 mapping, mbus bpp and other required fields used by the
  sub-device and video node.

- Add per sub-device type union in the resources, different
  sub-devices are using different resources, as an example: is_lite flag.

- Move camss link operation in to the resources. Currently one
  function supports different topologies depending of the number
  of devices. As hw version support increases this is not good
  way of supporting different topologies.

- Add parent device ops in to the resources. This resolves
  inter-dependencies of vfe and csid. Csid requests the clocks
  regulators etc from parent device instead calling directly vfe
  functions.

- Some cleanups in csid code for split the configuration of
  RX and testgen and RDI.

Changes in V2:
- Rebased on top of sc8280xp v6.
- The change "Designate lite subdevices in resources" was dropped,
  it was already merged in previous series.

Atanas Filipov (1):
  media: qcom: camss: Decompose register and link operations

Milen Mitkov (2):
  media: qcom: camss: Split testgen, RDI and RX for CSID 170
  media: qcom: camss: Decouple VFE from CSID

Radoslav Tsvetkov (5):
  media: qcom: camss: Add per sub-device type resources
  media: qcom: camss: Attach formats to VFE resources
  media: qcom: camss: Attach formats to CSID resources
  media: qcom: camss: Attach formats to CSIPHY resources
  media: qcom: camss: Move format related functions

 drivers/media/platform/qcom/camss/Makefile    |   1 +
 .../platform/qcom/camss/camss-csid-4-1.c      | 132 +---
 .../platform/qcom/camss/camss-csid-4-7.c      | 160 +---
 .../platform/qcom/camss/camss-csid-gen2.c     | 410 ++++------
 .../media/platform/qcom/camss/camss-csid.c    | 512 ++++++++++++-
 .../media/platform/qcom/camss/camss-csid.h    |  32 +-
 .../media/platform/qcom/camss/camss-csiphy.c  |  74 +-
 .../media/platform/qcom/camss/camss-csiphy.h  |  23 +-
 .../media/platform/qcom/camss/camss-format.c  |  98 +++
 .../media/platform/qcom/camss/camss-format.h  |  67 ++
 .../media/platform/qcom/camss/camss-vfe-17x.c |  10 +-
 .../media/platform/qcom/camss/camss-vfe-4-1.c |   4 +-
 .../media/platform/qcom/camss/camss-vfe-4-7.c |   6 +-
 .../media/platform/qcom/camss/camss-vfe-4-8.c |   6 +-
 .../platform/qcom/camss/camss-vfe-gen1.c      |   8 +-
 drivers/media/platform/qcom/camss/camss-vfe.c | 483 +++++++-----
 drivers/media/platform/qcom/camss/camss-vfe.h |  22 +-
 .../media/platform/qcom/camss/camss-video.c   | 295 +-------
 .../media/platform/qcom/camss/camss-video.h   |   5 +-
 drivers/media/platform/qcom/camss/camss.c     | 709 +++++++++++++-----
 drivers/media/platform/qcom/camss/camss.h     |  28 +-
 21 files changed, 1747 insertions(+), 1338 deletions(-)
 create mode 100644 drivers/media/platform/qcom/camss/camss-format.c
 create mode 100644 drivers/media/platform/qcom/camss/camss-format.h

-- 
2.17.1


^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2024-04-03  9:54 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-03-19 17:39 [PATCH v2 0/8] Move camss version related defs in to resources Gjorgji Rosikopulos
2024-03-19 17:39 ` [PATCH v2 1/8] media: qcom: camss: Add per sub-device type resources Gjorgji Rosikopulos
2024-04-01 22:30   ` Bryan O'Donoghue
2024-03-19 17:39 ` [PATCH v2 2/8] media: qcom: camss: Attach formats to VFE resources Gjorgji Rosikopulos
2024-03-19 17:39 ` [PATCH v2 3/8] media: qcom: camss: Attach formats to CSID resources Gjorgji Rosikopulos
2024-03-19 17:39 ` [PATCH v2 4/8] media: qcom: camss: Attach formats to CSIPHY resources Gjorgji Rosikopulos
2024-03-19 17:39 ` [PATCH v2 5/8] media: qcom: camss: Move format related functions Gjorgji Rosikopulos
2024-03-19 17:39 ` [PATCH v2 6/8] media: qcom: camss: Split testgen, RDI and RX for CSID 170 Gjorgji Rosikopulos
2024-03-19 17:39 ` [PATCH v2 7/8] media: qcom: camss: Decompose register and link operations Gjorgji Rosikopulos
2024-03-19 17:39 ` [PATCH v2 8/8] media: qcom: camss: Decouple VFE from CSID Gjorgji Rosikopulos
2024-04-01 22:35 ` [PATCH v2 0/8] Move camss version related defs in to resources Bryan O'Donoghue
2024-04-03  9:54   ` Gjorgji Rosikopulos (Consultant)

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 read-only IMAP folder(s) and NNTP newsgroup(s).