From nobody Wed Dec 17 00:17:15 2025 Delivered-To: importer2@patchew.org Received-SPF: pass (zohomail.com: domain of vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; envelope-from=linux-kernel-owner@vger.kernel.org; helo=vger.kernel.org; Authentication-Results: mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass(p=none dis=none) header.from=kernel.org ARC-Seal: i=1; a=rsa-sha256; t=1606216042; cv=none; d=zohomail.com; s=zohoarc; b=afU8dwpUiMa7Slct9z0TCXMwXYDcAZLHacvWaGopfWYktLA7/7T4O4TuH4+KH1Wd3p5REo89i+Z4Spqfl2GbQPqhr4UD50u7pML+oSGwLYnLH4dEuZ+gTRRFKPopAz+cTwmvfG0LWm0UqCQLH6ajwwg1sirDkmdGTRhnqjaUZaE= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1606216042; h=Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:List-Id:MIME-Version:Message-ID:References:Sender:Subject:To; bh=d2iTsU80eBg/KDovqhtyi33dqa1TDObgF08qzj15PLc=; b=mkygxdRKo2QOy9f2VDBWQ/UzfJSX4VKgFbxyb4eW0Y3/QPlmbx/qxBO0IvJRw8oReUacpM9qbRvfNCsMLNu2RRlkegyevNzKS3lD6xaoHsSEUFz07wBj4K+AZ2HkFEu1mT+Qg0UY05CWjqEFYkXcQMiaVuLu32cSyVcE/QSQSdo= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=fail; spf=pass (zohomail.com: domain of vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass header.from= (p=none dis=none) header.from= Return-Path: Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mx.zohomail.com with SMTP id 1606216042411538.4031069070705; Tue, 24 Nov 2020 03:07:22 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732629AbgKXLGu (ORCPT ); Tue, 24 Nov 2020 06:06:50 -0500 Received: from mail.kernel.org ([198.145.29.99]:33794 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732509AbgKXLGg (ORCPT ); Tue, 24 Nov 2020 06:06:36 -0500 Received: from mail.kernel.org (ip5f5ad5c3.dynamic.kabel-deutschland.de [95.90.213.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5B2222223C; Tue, 24 Nov 2020 11:06:31 +0000 (UTC) Received: from mchehab by mail.kernel.org with local (Exim 4.94) (envelope-from ) id 1khW9V-000Faf-Cl; Tue, 24 Nov 2020 12:06:29 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1606215991; bh=SSmmz+Xv/F8F5bLjxjkNpqvU2LAL2wcRypsC4tIZuDE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=JH6eT+V23GaGrPli0+hmLc1RlXUfVZ5rdsKgUVotOQWbL62j0YlIVBfDhoub4DQGQ 3PXdG8mwQAXlA8ouQNkEH04zFw/zcCZJX81LxsYgb47Gr16kfwLTiKn9OBmIKRGx1D XZL6tGBtbPHYl9P1wwopdVDkD4AY/qDzQJX68fWM= From: Mauro Carvalho Chehab Cc: Mauro Carvalho Chehab , "Daniel W. S. Almeida" , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, linux-media@vger.kernel.org Subject: [PATCH 29/31] media: vidtv.rst: update vidtv documentation Date: Tue, 24 Nov 2020 12:06:25 +0100 Message-Id: <9fa911fbdf90343f49fc1f284ea47fe0407a2b81.1606215584.git.mchehab+huawei@kernel.org> X-Mailer: git-send-email 2.28.0 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Sender: Mauro Carvalho Chehab To: unlisted-recipients:; (no To-header on input) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-ZohoMail-DKIM: fail (Header signature does not verify) Content-Type: text/plain; charset="utf-8" Update the vidtv documentation with the relevant changes after the last patches. Signed-off-by: Mauro Carvalho Chehab --- .../driver-api/media/drivers/vidtv.rst | 85 ++++++++++++++++--- 1 file changed, 72 insertions(+), 13 deletions(-) diff --git a/Documentation/driver-api/media/drivers/vidtv.rst b/Documentati= on/driver-api/media/drivers/vidtv.rst index edaceef2808c..52c201798d78 100644 --- a/Documentation/driver-api/media/drivers/vidtv.rst +++ b/Documentation/driver-api/media/drivers/vidtv.rst @@ -258,6 +258,42 @@ Using dvb-fe-tool The first step to check whether the demod loaded successfully is to run:: =20 $ dvb-fe-tool + Device Dummy demod for DVB-T/T2/C/S/S2 (/dev/dvb/adapter0/frontend0) capa= bilities: + CAN_FEC_1_2 + CAN_FEC_2_3 + CAN_FEC_3_4 + CAN_FEC_4_5 + CAN_FEC_5_6 + CAN_FEC_6_7 + CAN_FEC_7_8 + CAN_FEC_8_9 + CAN_FEC_AUTO + CAN_GUARD_INTERVAL_AUTO + CAN_HIERARCHY_AUTO + CAN_INVERSION_AUTO + CAN_QAM_16 + CAN_QAM_32 + CAN_QAM_64 + CAN_QAM_128 + CAN_QAM_256 + CAN_QAM_AUTO + CAN_QPSK + CAN_TRANSMISSION_MODE_AUTO + DVB API Version 5.11, Current v5 delivery system: DVBC/ANNEX_A + Supported delivery systems: + DVBT + DVBT2 + [DVBC/ANNEX_A] + DVBS + DVBS2 + Frequency range for the current standard: + From: 51.0 MHz + To: 2.15 GHz + Step: 62.5 kHz + Tolerance: 29.5 MHz + Symbol rate ranges for the current standard: + From: 1.00 MBauds + To: 45.0 MBauds =20 This should return what is currently set up at the demod struct, i.e.:: =20 @@ -316,7 +352,7 @@ For this, one should provide a configuration file known= as a 'scan file', here's an example:: =20 [Channel] - FREQUENCY =3D 330000000 + FREQUENCY =3D 474000000 MODULATION =3D QAM/AUTO SYMBOL_RATE =3D 6940000 INNER_FEC =3D AUTO @@ -337,6 +373,14 @@ You can browse scan tables online here: `dvb-scan-tabl= es Assuming this channel is named 'channel.conf', you can then run:: =20 $ dvbv5-scan channel.conf + dvbv5-scan ~/vidtv.conf + ERROR command BANDWIDTH_HZ (5) not found during retrieve + Cannot calc frequency shift. Either bandwidth/symbol-rate is unavailable = (yet). + Scanning frequency #1 330000000 + (0x00) Signal=3D -68.00dBm + Scanning frequency #2 474000000 + Lock (0x1f) Signal=3D -34.45dBm C/N=3D 33.74dB UCB=3D 0 + Service Beethoven, provider LinuxTV.org: digital television =20 For more information on dvb-scan, check its documentation online here: `dvb-scan Documentation `_. @@ -346,23 +390,38 @@ Using dvb-zap =20 dvbv5-zap is a command line tool that can be used to record MPEG-TS to dis= k. The typical use is to tune into a channel and put it into record mode. The exa= mple -below - which is taken from the documentation - illustrates that:: +below - which is taken from the documentation - illustrates that\ [1]_:: =20 - $ dvbv5-zap -c dvb_channel.conf "trilhas sonoras" -r - using demux '/dev/dvb/adapter0/demux0' + $ dvbv5-zap -c dvb_channel.conf "beethoven" -o music.ts -P -t 10 + using demux 'dvb0.demux0' reading channels from file 'dvb_channel.conf' - service has pid type 05: 204 - tuning to 573000000 Hz - audio pid 104 - dvb_set_pesfilter 104 - Lock (0x1f) Quality=3D Good Signal=3D 100.00% C/N=3D -13.80dB UCB=3D 70= postBER=3D 3.14x10^-3 PER=3D 0 - DVR interface '/dev/dvb/adapter0/dvr0' can now be opened + tuning to 474000000 Hz + pass all PID's to TS + dvb_set_pesfilter 8192 + dvb_dev_set_bufsize: buffer set to 6160384 + Lock (0x1f) Quality=3D Good Signal=3D -34.66dBm C/N=3D 33.41dB UCB=3D 0= postBER=3D 0 preBER=3D 1.05x10^-3 PER=3D 0 + Lock (0x1f) Quality=3D Good Signal=3D -34.57dBm C/N=3D 33.46dB UCB=3D 0= postBER=3D 0 preBER=3D 1.05x10^-3 PER=3D 0 + Record to file 'music.ts' started + received 24587768 bytes (2401 Kbytes/sec) + Lock (0x1f) Quality=3D Good Signal=3D -34.42dBm C/N=3D 33.89dB UCB=3D 0= postBER=3D 0 preBER=3D 2.44x10^-3 PER=3D 0 =20 -The channel can be watched by playing the contents of the DVR interface, w= ith -some player that recognizes the MPEG-TS format, such as *mplayer* or *vlc*. +.. [1] In this example, it records 10 seconds with all program ID's stored + at the music.ts file. + + +The channel can be watched by playing the contents of the stream with some +player that recognizes the MPEG-TS format, such as ``mplayer`` or ``vlc``. =20 By playing the contents of the stream one can visually inspect the working= s of -vidtv, e.g.:: +vidtv, e.g., to play a recorded TS file with:: + + $ mplayer music.ts + +or, alternatively, running this command on one terminal:: + + $ dvbv5-zap -c dvb_channel.conf "beethoven" -P -r & + +And, on a second terminal, playing the contents from DVR interface with:: =20 $ mplayer /dev/dvb/adapter0/dvr0 =20 --=20 2.28.0