mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Hardevsinh Palaniya <hardevsinh.palaniya@siliconsignals.io>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	sakari.ailus@linux.intel.com
Subject: Re: [PATCH v5 2/2] media: i2c: add ov2735 image sensor driver
Date: Sat, 26 Jul 2025 18:10:50 +0100	[thread overview]
Message-ID: <175354985094.1609430.13921131213777523371@ping.linuxembedded.co.uk> (raw)
In-Reply-To: <PN3P287MB3519055FE42890F5F577B51BFF58A@PN3P287MB3519.INDP287.PROD.OUTLOOK.COM>

Quoting Hardevsinh Palaniya (2025-07-26 07:06:05)
> > Quoting Hardevsinh Palaniya (2025-07-25 06:55:23)
> > <snip>
> > > > > +static int ov2735_page_access(struct ov2735 *ov2735,
> > > > > +�������������������������� u32 reg, void *val, int *err, bool is_read)
> > > > > +{
> > > > > +���� u8 page = (reg >> CCI_REG_PRIVATE_SHIFT) & 0xff;
> > > >
> > > > ' & 0xff' part is redundant.
> > > >
> > > > > +���� u32 addr = reg & ~CCI_REG_PRIVATE_MASK;
> > > > > +���� int ret = 0;
> > > >
> > > > How is this assignment being used?
> > > >
> > > > > +���� if (err && *err)
> > > > > +������������ return *err;
> > > > > +
> > > > > +���� mutex_lock(&ov2735->page_lock);
> > > > > +
> > > > > +���� /* Perform page access before read/write */
> > > > > +���� if (ov2735->current_page != page) {
> > > > > +������������ ret = cci_write(ov2735->cci, OV2735_REG_PAGE_SELECT, page, err);
> > > > > +������������ if (ret)
> > > > > +�������������������� goto err_mutex_unlock;
> > > > > +������������ ov2735->current_page = page;
> > > > > +���� }
> > > > > +
> > > > > +���� if (is_read)
> > > > > +������������ ret = cci_read(ov2735->cci, addr, (u64 *)val, err);
> > > > > +���� else
> > > > > +������������ ret = cci_write(ov2735->cci, addr, *(u64 *)val, err);
> > > >
> > > > Do you really need this castings?
> > >
> > > Do you really think this casting is unnecessary?
> > >
> > 
> > Yes? Well quite probably - I haven't checked myself yet but ..
> > 
> > 
> > > Please check the definitions of cci_read/write
> > >
> > > without this, we can't even build the driver.
> > 
> > How about ... changing the function prototype of ov2735_page_access ?
> 
> Of course, changing the function prototype would work.
> 
> My intention is to keep a single ov2735_page_access() function that can
> handle both read and write operations. The cci_read() function expects 
> a u64 *, whereas cci_write() expects a u64 value. To support both cases
> within one function, I’ve used a void *val and cast it appropriately 
> depending on the operation.
> 
> If we were to remove the casting, we would need to split this into two
> separate functions, one for read and one for write, even though the only 
> difference between them would be a single line. I’d prefer to avoid that
> redundancy and keep the code compact. 
> 
> Let me know if you see a better way to handle this without duplicating
> the logic. 

ov2735_page_access() {
	if (ov2735->page != page)
		cci_write(PAGE, page)
	ov2735->page = page;
}

oc2735_read() {
	ov2735_page_access();
	cci_read()
}

ov2735_write() {
	ov2735_page_access();
	cci_write()
}

> 
> Best Regards,
> Hardev

  parent reply	other threads:[~2025-07-26 17:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 10:47 [PATCH v5 0/2] media: i2c: Add ov2735 camera " Hardevsinh Palaniya
2025-07-24 10:47 ` [PATCH v5 1/2] dt-bindings: media: i2c: Add ov2735 sensor Hardevsinh Palaniya
2025-07-24 10:47 ` [PATCH v5 2/2] media: i2c: add ov2735 image sensor driver Hardevsinh Palaniya
2025-07-24 21:17   ` Andy Shevchenko
2025-07-25  5:55     ` Hardevsinh Palaniya
2025-07-25 14:40       ` Kieran Bingham
2025-07-26  6:06         ` Hardevsinh Palaniya
2025-07-26  9:43           ` Laurent Pinchart
2025-07-26 17:10           ` Kieran Bingham [this message]
2025-07-29  6:35       ` Hardevsinh Palaniya

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=175354985094.1609430.13921131213777523371@ping.linuxembedded.co.uk \
    --to=kieran.bingham@ideasonboard.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=hardevsinh.palaniya@siliconsignals.io \
    --cc=sakari.ailus@linux.intel.com \
    /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

all inboxes | Powered by JetHome®