From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, linux-media@vger.kernel.org
Cc: linux-sh@vger.kernel.org, Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH 07/10] sh-vou: add support for log_status
Date: Fri, 05 Jun 2015 16:28:03 +0300 [thread overview]
Message-ID: <5571A3E3.6070805@cogentembedded.com> (raw)
In-Reply-To: <1433501966-30176-8-git-send-email-hverkuil@xs4all.nl>
Hello.
On 6/5/2015 1:59 PM, Hans Verkuil wrote:
> From: Hans Verkuil <hans.verkuil@cisco.com>
> Dump the VOU registers in log_status.
> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
> ---
> drivers/media/platform/sh_vou.c | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
> diff --git a/drivers/media/platform/sh_vou.c b/drivers/media/platform/sh_vou.c
> index 7ed5a8b..400efec 100644
> --- a/drivers/media/platform/sh_vou.c
> +++ b/drivers/media/platform/sh_vou.c
> @@ -951,6 +951,34 @@ static int sh_vou_g_std(struct file *file, void *priv, v4l2_std_id *std)
> return 0;
> }
>
> +static int sh_vou_log_status(struct file *file, void *priv)
> +{
> + struct sh_vou_device *vou_dev = video_drvdata(file);
> +
> + pr_info("PSELA: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUER));
> + pr_info("VOUER: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUER));
You're dumping the same register twice, under different names?
> + pr_info("VOUCR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUCR));
> + pr_info("VOUSTR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUSTR));
> + pr_info("VOUVCR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUVCR));
> + pr_info("VOUISR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUISR));
> + pr_info("VOUBCR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUBCR));
> + pr_info("VOUDPR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUDPR));
> + pr_info("VOUDSR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUDSR));
> + pr_info("VOUVPR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUVPR));
> + pr_info("VOUIR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUIR));
> + pr_info("VOUSRR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUSRR));
> + pr_info("VOUMSR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUMSR));
> + pr_info("VOUHIR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUHIR));
> + pr_info("VOUDFR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUDFR));
> + pr_info("VOUAD1R: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUAD1R));
> + pr_info("VOUAD2R: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUAD2R));
> + pr_info("VOUAIR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUAIR));
> + pr_info("VOUSWR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOUSWR));
> + pr_info("VOURCR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOURCR));
> + pr_info("VOURPR: 0x%08x\n", sh_vou_reg_a_read(vou_dev, VOURPR));
> + return 0;
> +}
> +
[...]
WBR, Sergei
next prev parent reply other threads:[~2015-06-05 13:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 10:59 [PATCH 00/10] sh-vou: fixes, convert to vb2 Hans Verkuil
2015-06-05 10:59 ` [PATCH 01/10] sh-vou: hook up the clock correctly Hans Verkuil
2015-06-06 21:42 ` Geert Uytterhoeven
2015-06-07 8:51 ` Hans Verkuil
2015-06-05 10:59 ` [PATCH 02/10] sh-vou: fix querycap support Hans Verkuil
2015-06-05 10:59 ` [PATCH 03/10] sh-vou: use v4l2_fh Hans Verkuil
2015-06-05 10:59 ` [PATCH 04/10] sh-vou: support compulsory G/S/ENUM_OUTPUT ioctls Hans Verkuil
2015-06-05 10:59 ` [PATCH 05/10] sh-vou: fix incorrect initial pixelformat Hans Verkuil
2015-06-05 10:59 ` [PATCH 06/10] sh-vou: replace g/s_crop/cropcap by g/s_selection Hans Verkuil
2015-06-05 10:59 ` [PATCH 07/10] sh-vou: add support for log_status Hans Verkuil
2015-06-05 13:28 ` Sergei Shtylyov [this message]
2015-06-05 14:37 ` Hans Verkuil
2015-06-05 10:59 ` [PATCH 08/10] sh-vou: let sh_vou_s_fmt_vid_out call sh_vou_try_fmt_vid_out Hans Verkuil
2015-06-05 10:59 ` [PATCH 09/10] sh-vou: fix bytesperline Hans Verkuil
2015-06-05 10:59 ` [PATCH 10/10] sh-vou: convert to vb2 Hans Verkuil
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=5571A3E3.6070805@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=linux-sh@vger.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