public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Antti Laakso <antti.laakso@linux.intel.com>,
	linux-media@vger.kernel.org, linux-gpio@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, linusw@kernel.org,
	brgl@kernel.org, mchehab@kernel.org, dan.scally@ideasonboard.com,
	ilpo.jarvinen@linux.intel.com, hverkuil+cisco@kernel.org,
	sre@kernel.org, hao.yao@intel.com, jason.z.chen@intel.com,
	jimmy.su@intel.com, miguel.vadillo@intel.com, kees@kernel.org,
	ribalda@chromium.org
Subject: Re: [PATCH 1/5] media: i2c: ov5675: Wait for endpoint
Date: Tue, 10 Mar 2026 14:12:14 +0100	[thread overview]
Message-ID: <d17261f5-a423-433b-8595-0de63200011b@kernel.org> (raw)
In-Reply-To: <abAX3WVzKgTIynW7@kekkonen.localdomain>

Hi,

On 10-Mar-26 14:08, Sakari Ailus wrote:
> Hi Hans,
> 
> On Tue, Mar 10, 2026 at 02:03:30PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> Thank you for your patches for this, cool to see someone working
>> on supporting this!
>>
>> On 10-Mar-26 13:44, Antti Laakso wrote:
>>> Defer probe if endpoint is not yet available. And do it before acquiring
>>> clock, gpio and regulators.
>>>
>>> Signed-off-by: Antti Laakso <antti.laakso@linux.intel.com>
>>> ---
>>>  drivers/media/i2c/ov5675.c | 16 +++++++---------
>>>  1 file changed, 7 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/drivers/media/i2c/ov5675.c b/drivers/media/i2c/ov5675.c
>>> index ea26df328189..81916fa8c117 100644
>>> --- a/drivers/media/i2c/ov5675.c
>>> +++ b/drivers/media/i2c/ov5675.c
>>> @@ -1181,6 +1181,13 @@ static int ov5675_get_hwcfg(struct ov5675 *ov5675)
>>>  	if (!fwnode)
>>>  		return -ENXIO;
>>>  
>>> +	ep = fwnode_graph_get_endpoint_by_id(fwnode, 0, 0,
>>> +					     FWNODE_GRAPH_ENDPOINT_NEXT);
>>> +	ret = v4l2_fwnode_endpoint_alloc_parse(ep, &bus_cfg);
>>> +	fwnode_handle_put(ep);
>>> +	if (ret)
>>> +		return ret;
>>
>> This should be:
>>
>> 		return dev_err_probe(dev, ret, "failed to parse endpoint\n");
> 
> I'd keep it as-is; see
> <URL:https://lore.kernel.org/linux-media/20260310080038.1182695-1-sakari.ailus@linux.intel.com/T/#u>.
> V4l2-fwnode also prints errors (albeit on debug level) on failures.

Ok, keeping this as is is fine with me.

There still is the issue of adding the goto-s to properly free
the bus_cfg on errors.

Regards,

Hans




  reply	other threads:[~2026-03-10 13:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-10 12:44 [PATCH 0/5] platform: int3472: Add MSI prestige 14 AI EVO data Antti Laakso
2026-03-10 12:44 ` [PATCH 1/5] media: i2c: ov5675: Wait for endpoint Antti Laakso
2026-03-10 13:03   ` Hans de Goede
2026-03-10 13:08     ` Sakari Ailus
2026-03-10 13:12       ` Hans de Goede [this message]
2026-03-10 12:44 ` [PATCH 2/5] media: ipu-bridge: Add ov5675 sensor Antti Laakso
2026-03-10 13:06   ` Hans de Goede
2026-03-10 13:25   ` Dan Scally
2026-03-10 12:44 ` [PATCH 3/5] platform: int3472: Add gpio platform data Antti Laakso
2026-03-10 13:06   ` Hans de Goede
2026-03-10 13:32   ` Bartosz Golaszewski
2026-03-11 11:17     ` Antti Laakso
2026-03-10 14:27   ` Dan Scally
2026-03-10 12:44 ` [PATCH 4/5] gpio: tps68470: Add i2c daisy chain support Antti Laakso
2026-03-10 13:07   ` Hans de Goede
2026-03-10 14:33   ` Dan Scally
2026-03-10 12:44 ` [PATCH 5/5] platform: int3472: Add MSI prestige board data Antti Laakso
2026-03-10 13:09   ` Hans de Goede
2026-03-10 13:17     ` Sakari Ailus
2026-03-10 14:24       ` Hans de Goede
2026-03-10 14:32   ` Dan Scally
2026-03-10 15:02     ` Hans de Goede
2026-03-11 11:20     ` Antti Laakso

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=d17261f5-a423-433b-8595-0de63200011b@kernel.org \
    --to=hansg@kernel.org \
    --cc=antti.laakso@linux.intel.com \
    --cc=brgl@kernel.org \
    --cc=dan.scally@ideasonboard.com \
    --cc=hao.yao@intel.com \
    --cc=hverkuil+cisco@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jason.z.chen@intel.com \
    --cc=jimmy.su@intel.com \
    --cc=kees@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=miguel.vadillo@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=ribalda@chromium.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sre@kernel.org \
    /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