[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250805103930.GD24627@pendragon.ideasonboard.com>
Date: Tue, 5 Aug 2025 13:39:30 +0300
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc: Bin Du <Bin.Du@....com>, mchehab@...nel.org, hverkuil@...all.nl,
bryan.odonoghue@...aro.org, prabhakar.mahadev-lad.rj@...renesas.com,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
pratap.nirujogi@....com, benjamin.chan@....com, king.li@....com,
gjorgji.rosikopulos@....com, Phil.Jawich@....com,
Dominic.Antony@....com, Svetoslav.Stoilov@....com
Subject: Re: [PATCH v2 3/8] media: platform: amd: Add helpers to configure
isp4 mipi phy
On Mon, Jul 28, 2025 at 06:33:30AM +0000, Sakari Ailus wrote:
> On Wed, Jun 18, 2025 at 05:19:54PM +0800, Bin Du wrote:
> > The helper functions is for configuring, starting and stop the MIPI PHY.
> > All configurations related to MIPI PHY configuration and calibration
> > parameters are encapsulated in two helper functions: start and stop
> > mipi phy.
> >
> > Signed-off-by: Bin Du <Bin.Du@....com>
> > Signed-off-by: Svetoslav Stoilov <Svetoslav.Stoilov@....com>
> > ---
> > drivers/media/platform/amd/isp4/Makefile | 1 +
> > drivers/media/platform/amd/isp4/isp4_phy.c | 1547 ++++++++++++++++++++
> > drivers/media/platform/amd/isp4/isp4_phy.h | 14 +
> > 3 files changed, 1562 insertions(+)
> > create mode 100644 drivers/media/platform/amd/isp4/isp4_phy.c
> > create mode 100644 drivers/media/platform/amd/isp4/isp4_phy.h
[snip]
> > diff --git a/drivers/media/platform/amd/isp4/isp4_phy.c b/drivers/media/platform/amd/isp4/isp4_phy.c
> > new file mode 100644
> > index 000000000000..8d31a21074bb
> > --- /dev/null
> > +++ b/drivers/media/platform/amd/isp4/isp4_phy.c
> > @@ -0,0 +1,1547 @@
[snip]
> > +union isp4phy_mipi_0 {
> > + struct {
> > + u32 shutdownz : 1;
> > + u32 rstz : 1;
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +union isp4phy_mipi_1 {
> > + struct {
> > + u32 mode : 1;
>
> Please pad these -- I don't think the ABI otherwise requires they're in a
> particular location of the container (u32).
Or better, ditch the structures, and use macros to define register
fields like all other drivers do.
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +union isp4phy_mipi_2 {
> > + struct {
> > + u32 rxdatawidthhs_0 : 2;
> > + u32 rxdatawidthhs_1 : 2;
> > + u32 rxdatawidthhs_2 : 2;
> > + u32 rxdatawidthhs_3 : 2;
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +struct isp4phy_mipi_3 {
> > + u32 reserved;
> > +};
> > +
> > +union isp4phy_mipi_4 {
> > + struct {
> > + u32 enableclk : 1;
> > + u32 enable_0 : 1;
> > + u32 enable_1 : 1;
> > + u32 enable_2 : 1;
> > + u32 enable_3 : 1;
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +union isp4phy_mipi_5 {
> > + struct {
> > + u32 forcerxmode_0 : 1;
> > + u32 forcerxmode_1 : 1;
> > + u32 forcerxmode_2 : 1;
> > + u32 forcerxmode_3 : 1;
> > + u32 forcerxmode_clk : 1;
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +union isp4phy_mipi_6 {
> > + struct {
> > + u32 turndisable_0 : 1;
> > + u32 turndisable_1 : 1;
> > + u32 turndisable_2 : 1;
> > + u32 turndisable_3 : 1;
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +union isp4phy_mipi_7 {
> > + struct {
> > + u32 ready : 1;
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +union isp4phy_mipi_ind_idx {
> > + struct {
> > + u32 addr : 16;
>
> u16 would seem appropriate here.
>
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +union isp4phy_mipi_ind_data {
> > + struct {
> > + u32 data : 16;
>
> Ditto.
>
> > + } bit;
> > + u32 value;
> > +};
> > +
> > +union isp4phy_mipi_ind_wack {
> > + struct {
> > + u32 ack : 1;
> > + u32 pslverr : 1;
> > + } bit;
> > + u32 value;
> > +};
[snip]
--
Regards,
Laurent Pinchart
Powered by blists - more mailing lists