All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	Ezequiel Garcia <ezequiel@collabora.com>,
	Nicolas Dufresne <nicolas@ndufresne.ca>,
	Jonas Karlman <jonas@kwiboo.se>,
	devicetree@vger.kernel.org, kernel@pengutronix.de
Subject: [PATCH v4 02/10] media: hantro: print video device name in addition to device node
Date: Tue, 11 Jun 2019 14:50:50 +0200	[thread overview]
Message-ID: <20190611125058.13470-3-p.zabel@pengutronix.de> (raw)
In-Reply-To: <20190611125058.13470-1-p.zabel@pengutronix.de>

It can be helpful to know which video device was registered at which
device node.

Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Reviewed-by: Boris Brezillon <boris.brezillon@collabora.com>
---
 drivers/staging/media/hantro/hantro_drv.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/staging/media/hantro/hantro_drv.c b/drivers/staging/media/hantro/hantro_drv.c
index 34a646da834b..c248ce4f7ca6 100644
--- a/drivers/staging/media/hantro/hantro_drv.c
+++ b/drivers/staging/media/hantro/hantro_drv.c
@@ -608,7 +608,8 @@ static int hantro_add_func(struct hantro_dev *vpu, unsigned int funcid)
 		goto err_unreg_dev;
 	}
 
-	v4l2_info(&vpu->v4l2_dev, "registered as /dev/video%d\n", vfd->num);
+	v4l2_info(&vpu->v4l2_dev, "registered %s as /dev/video%d\n", vfd->name,
+		  vfd->num);
 
 	return 0;
 
-- 
2.20.1

  parent reply	other threads:[~2019-06-11 12:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 12:50 [PATCH v4 00/10] Rename Rockchip VPU driver to Hantro, add initial i.MX8M support Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 01/10] rockchip/vpu: rename from rockchip to hantro Philipp Zabel
2019-06-12  8:14   ` Jonas Karlman
2019-06-12  8:23     ` Boris Brezillon
2019-06-11 12:50 ` Philipp Zabel [this message]
2019-06-11 12:50 ` [PATCH v4 03/10] media: hantro: add PM runtime resume callback Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 04/10] media: hantro: make irq names configurable Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 05/10] media: hantro: add support for named register ranges Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 06/10] media: hantro: add support for separate control block Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 07/10] media: hantro: allow arbitrary number of clocks Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 08/10] media: dt-bindings: Document i.MX8MQ and i.MX8MM VPU bindings Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 09/10] media: hantro: add initial i.MX8MQ support Philipp Zabel
2019-06-11 12:50 ` [PATCH v4 10/10] media: hantro: add initial i.MX8MM support (untested) Philipp Zabel
2019-06-12  7:55 ` [PATCH v4 00/10] Rename Rockchip VPU driver to Hantro, add initial i.MX8M support Hans Verkuil
2019-06-12  8:00   ` Hans Verkuil
2019-06-12  8:30     ` Boris Brezillon
2019-06-12  9:46     ` Philipp Zabel

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=20190611125058.13470-3-p.zabel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=boris.brezillon@collabora.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ezequiel@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jonas@kwiboo.se \
    --cc=kernel@pengutronix.de \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    /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.