Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Martin Kepplinger <martink@posteo.de>
To: laurent.pinchart@ideasonboard.com, mchehab@kernel.org,
	shawnguo@kernel.org,  s.hauer@pengutronix.de,
	kernel@pengutronix.de, festevam@gmail.com
Cc: linux-media@vger.kernel.org, imx@lists.linux.dev,
	 linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: nxp: imx8-isi: check return value of media_pad_remote_pad_first()
Date: Thu, 06 Feb 2025 08:49:37 +0000	[thread overview]
Message-ID: <1f4b4e707762c0926c0acece18cb9cc3ecc242bc.camel@posteo.de> (raw)
In-Reply-To: <20250205172957.182362-1-martink@posteo.de>

Am Mittwoch, dem 05.02.2025 um 17:29 +0000 schrieb Martin Kepplinger-
Novaković:
> media_pad_remote_pad_first() return NULL if "no enabled link has been
> found".
> Check for that.
> 
> backstory
> =========
> While trying to get a (Y10 grey) sensor working on imx8mp (v6.12.12
> now and
> I know the hardware works on an ancient nxp-kernel),
> I tried to enable the sensor link, set formats and stream:
> 

btw, that's roughly the
driver: https://github.com/VC-MIPI-modules/vc_mipi_nxp/tree/master/src
that might need additions to with recent mainline kernels. Will the
sensor be the reason for the link not being found here?

                         martin

  reply	other threads:[~2025-02-06  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 17:29 [PATCH] media: nxp: imx8-isi: check return value of media_pad_remote_pad_first() Martin Kepplinger-Novaković
2025-02-06  8:49 ` Martin Kepplinger [this message]
2025-08-20 14:01   ` Laurent Pinchart
2025-08-20 14:54     ` Martin Kepplinger-Novakovic
2025-08-20 19:25       ` Laurent Pinchart

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=1f4b4e707762c0926c0acece18cb9cc3ecc242bc.camel@posteo.de \
    --to=martink@posteo.de \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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