From: Antti Laakso <antti.laakso@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, hao.yao@intel.com, dongcheng.yan@intel.com
Subject: Re: [PATCH 1/1] media: i2c: Add Omnivision ov05c10 sensor driver
Date: Wed, 30 Sep 2026 15:48:54 +0300 [thread overview]
Message-ID: <ar0FNjatXOfRCBVB@alaakso-desk> (raw)
In-Reply-To: <ar0BZ4MAut3fnS86@kekkonen.localdomain>
On Wed, Sep 30, 2026 at 03:32:39PM +0300, Sakari Ailus wrote:
> Hei Antti,
>
> Thanks for the review.
>
> On Wed, Sep 30, 2026 at 03:27:38PM +0300, Antti Laakso wrote:
> ...
> > > +static int ov05c10_parse_fwnode(struct ov05c10 *ov05c10, struct device *dev)
> > > +{
> > > + struct fwnode_handle *endpoint;
> > > + struct v4l2_fwnode_endpoint bus_cfg = {
> > > + .bus_type = V4L2_MBUS_CSI2_DPHY,
> > > + };
> > > + int ret;
> > > +
> > > + endpoint = fwnode_graph_get_endpoint_by_id(dev_fwnode(dev), 0, 0,
> > > + FWNODE_GRAPH_ENDPOINT_NEXT);
> >
> > Should this return -EPROBE_DEFER in case endpoint is not found?
>
> v4l2_fwnode_endpoint_alloc_parse() will return that if endpoint is NULL.
>
Ah, indeed.
Reviewed-by: Antti Laakso <antti.laakso@linux.intel.com>
> >
> > > + ret = v4l2_fwnode_endpoint_alloc_parse(endpoint, &bus_cfg);
> > > + fwnode_handle_put(endpoint);
> > > + if (ret) {
> > > + dev_err(dev, "parsing endpoint node failed\n");
> > > + goto out_err;
> > > + }
>
> --
> Regards,
>
> Sakari Ailus
next prev parent reply other threads:[~2026-09-30 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:18 [PATCH 1/1] media: i2c: Add Omnivision ov05c10 sensor driver Sakari Ailus
2026-09-30 12:27 ` Antti Laakso
2026-09-30 12:32 ` Sakari Ailus
2026-09-30 12:48 ` Antti Laakso [this message]
2026-09-30 16:38 ` Mehdi Djait
2026-09-30 17:28 ` Sakari Ailus
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=ar0FNjatXOfRCBVB@alaakso-desk \
--to=antti.laakso@linux.intel.com \
--cc=dongcheng.yan@intel.com \
--cc=hao.yao@intel.com \
--cc=linux-media@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.