linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacopo Mondi <jacopo@jmondi.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: jacopo+renesas@jmondi.org,
	kieran.bingham+renesas@ideasonboard.com,
	laurent.pinchart+renesas@ideasonboard.com,
	niklas.soderlund+renesas@ragnatech.se, mchehab@kernel.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: i2c: max9286: Pass default bus type when parsing fwnode endpoint
Date: Wed, 2 Oct 2019 09:54:32 +0200	[thread overview]
Message-ID: <20191002075432.bkee4fl6cfcr25iv@uno.localdomain> (raw)
In-Reply-To: <20191001145503.5170-1-manivannan.sadhasivam@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]

Hello Manivannan,

On Tue, Oct 01, 2019 at 08:25:03PM +0530, Manivannan Sadhasivam wrote:
> The caller of v4l2_fwnode_endpoint_alloc_parse() is expected to pass a
> valid bus_type parameter for proper working of this API. Hence, pass
> V4L2_MBUS_CSI2_DPHY as the bus_type parameter as this driver only supports
> MIPI CSI2 for now. Without this commit, the API fails on 96Boards
> Dragonboard410c connected to MAX9286 deserializer.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
>
> This patch depends on the latest "MAX9286 GMSL Support" series posted
> by Kieran Bingham.
>
>  drivers/media/i2c/max9286.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/i2c/max9286.c b/drivers/media/i2c/max9286.c
> index 9390edf5ad9c..6e1299f15493 100644
> --- a/drivers/media/i2c/max9286.c
> +++ b/drivers/media/i2c/max9286.c
> @@ -976,7 +976,9 @@ static int max9286_parse_dt(struct max9286_device *max9286)
>
>  		/* For the source endpoint just parse the bus configuration. */
>  		if (ep.port == MAX9286_SRC_PAD) {
> -			struct v4l2_fwnode_endpoint vep;
> +			struct v4l2_fwnode_endpoint vep = {
> +				.bus_type = V4L2_MBUS_CSI2_DPHY
> +			};

Isn't the bus_type just an hint ? __v4l2_fwnode_endpoint_parse()
should try to parse CSI2 first, and should be able to to deduct the bus
type from the properties specified in DT...

Anyway, I'm not against this change, the contrary actually, I'm just
afraid it might hide some more subtile bug, as we don't need this on
our platforms...

Is the db410c mainline ? Do you have DT snippets for db410c+max9286 to
share?

Thanks
  j

>  			int ret;
>
>  			ret = v4l2_fwnode_endpoint_alloc_parse(
> --
> 2.17.1
>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-10-02  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 14:55 [PATCH] media: i2c: max9286: Pass default bus type when parsing fwnode endpoint Manivannan Sadhasivam
2019-10-02  7:54 ` Jacopo Mondi [this message]
2019-10-02  8:56   ` 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=20191002075432.bkee4fl6cfcr25iv@uno.localdomain \
    --to=jacopo@jmondi.org \
    --cc=jacopo+renesas@jmondi.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=mchehab@kernel.org \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    /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;
as well as URLs for NNTP newsgroup(s).