From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: mchehab@kernel.org, gregkh@linuxfoundation.org,
rfontana@redhat.com, kstewart@linuxfoundation.org,
tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Subject: [Linux-kernel-mentees] [PATCH] media: dummy_dvb_fe: register adapter/frontend
Date: Tue, 26 Nov 2019 12:31:57 -0300 [thread overview]
Message-ID: <20191126153157.26355-1-dwlsalmeida@gmail.com> (raw)
From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
Before using the DTV frontend core, a bridge driver should register the
new frontend at the subsystem and unregister it at device detach / removal.
Signed-off-by: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
---
drivers/media/dvb-frontends/dvb_dummy_fe.c | 39 ++++++++++++++++++++--
1 file changed, 37 insertions(+), 2 deletions(-)
diff --git a/drivers/media/dvb-frontends/dvb_dummy_fe.c b/drivers/media/dvb-frontends/dvb_dummy_fe.c
index 4db679cb70ad..1ccb58c67e8e 100644
--- a/drivers/media/dvb-frontends/dvb_dummy_fe.c
+++ b/drivers/media/dvb-frontends/dvb_dummy_fe.c
@@ -13,12 +13,12 @@
#include <media/dvb_frontend.h>
#include "dvb_dummy_fe.h"
+DVB_DEFINE_MOD_OPT_ADAPTER_NR(adapter_nr);
struct dvb_dummy_fe_state {
struct dvb_frontend frontend;
};
-
static int dvb_dummy_fe_read_status(struct dvb_frontend *fe,
enum fe_status *status)
{
@@ -84,7 +84,36 @@ static int dvb_dummy_fe_sleep(struct dvb_frontend* fe)
static int dvb_dummy_fe_init(struct dvb_frontend* fe)
{
- return 0;
+ int result = 0;
+ struct dvb_adapter *adapter = fe->dvb;
+
+ result = dvb_register_adapter(adapter,
+ KBUILD_MODNAME,
+ THIS_MODULE,
+ adapter->device,
+ adapter_nr);
+
+ if (!result) {
+ pr_err("DVB_DUMMY_FE: Failed to register the adapter, errno:%d",
+ result);
+ goto err;
+ }
+
+ result = dvb_register_frontend(adapter, fe);
+ if (!result) {
+ pr_err("DVB_DUMMY_FE: Failed to register the frontend, errno:%d",
+ result);
+ goto err;
+ }
+
+ return result;
+
+err:
+ dvb_unregister_adapter(adapter);
+ dvb_unregister_frontend(fe);
+ dvb_frontend_detach(fe);
+ return result;
+
}
static int dvb_dummy_fe_set_tone(struct dvb_frontend *fe,
@@ -102,6 +131,12 @@ static int dvb_dummy_fe_set_voltage(struct dvb_frontend *fe,
static void dvb_dummy_fe_release(struct dvb_frontend* fe)
{
struct dvb_dummy_fe_state* state = fe->demodulator_priv;
+ struct dvb_adapter *adapter = fe->dvb;
+
+ dvb_unregister_adapter(adapter);
+ dvb_unregister_frontend(fe);
+ dvb_frontend_detach(fe);
+
kfree(state);
}
--
2.24.0
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next reply other threads:[~2019-11-26 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 15:31 Daniel W. S. Almeida [this message]
2019-12-01 7:56 ` [Linux-kernel-mentees] [PATCH] media: dummy_dvb_fe: register adapter/frontend Mauro Carvalho Chehab
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=20191126153157.26355-1-dwlsalmeida@gmail.com \
--to=dwlsalmeida@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfontana@redhat.com \
--cc=tglx@linutronix.de \
/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).