From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Stefan Ringel <linuxtv@stefanringel.de>
Cc: linux-media@vger.kernel.org, Oliver Endriss <o.endriss@gmx.de>
Subject: Re: [PATCH 2/3] drxk: correction frontend attatching
Date: Thu, 05 Jan 2012 18:46:37 -0200 [thread overview]
Message-ID: <4F060C2D.6070107@redhat.com> (raw)
In-Reply-To: <4EED829E.6020407@stefanringel.de>
On 18-12-2011 04:05, Stefan Ringel wrote:
> Am 18.12.2011 00:47, schrieb Oliver Endriss:
>> On Sunday 18 December 2011 00:39:49 Oliver Endriss wrote:
>>> On Saturday 17 December 2011 21:57:16 linuxtv@stefanringel.de wrote:
>>>> From: Stefan Ringel<linuxtv@stefanringel.de>
>>>>
>>>> all drxk have dvb-t, but not dvb-c.
>>>>
>>>> Signed-off-by: Stefan Ringel<linuxtv@stefanringel.de>
>>>> ---
>>>> drivers/media/dvb/frontends/drxk_hard.c | 6 ++++--
>>>> 1 files changed, 4 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/media/dvb/frontends/drxk_hard.c b/drivers/media/dvb/frontends/drxk_hard.c
>>>> index 038e470..8a59801 100644
>>>> --- a/drivers/media/dvb/frontends/drxk_hard.c
>>>> +++ b/drivers/media/dvb/frontends/drxk_hard.c
>>>> @@ -6460,9 +6460,11 @@ struct dvb_frontend *drxk_attach(const struct drxk_config *config,
>>>> init_state(state);
>>>> if (init_drxk(state)< 0)
>>>> goto error;
>>>> - *fe_t =&state->t_frontend;
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>
>>>> - return&state->c_frontend;
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> + if (state->m_hasDVBC)
>>>> + *fe_t =&state->c_frontend;
>>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>> +
>>>> + return&state->t_frontend;
>>> ^^^^^^^^^^^^^^^^^^^
>>>>
>>>> error:
>>>> printk(KERN_ERR "drxk: not found\n");
>>> NAK, this changes the behaviour for existing drivers.
>>>
>>> What is the point to swap DVB-T and DVB-C frontends?
>>> If you really need this, please add an option to the config struct
>>> with default that does not change anything for existing drivers.
>> Correction:
>> Better do something like this (untested):
>>
>> if (state->m_hasDVBC) {
>> *fe_t =&state->t_frontend;
>> return state->c_frontend;
>> } else
>> return&state->t_frontend;
>>
>> CU
>> Oliver
>>
> What shall be that, explain? For me not practicable.
The right thing to do here is to create just one frontend per DRX-K.
This were already discussed in the past. Now that we have enough
dvb-core infrastructure to support it, I've made the patches for it:
http://news.gmane.org/gmane.linux.drivers.video-input-infrastructure
I took the m_hasDVBC and m_hasDVBT states into account, so DRX-K
drivers that implement just one of the types should now be properly
reported.
It also made the attachment logic simpler.
Regards,
Mauro
next prev parent reply other threads:[~2012-01-05 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 20:57 [PATCH 1/3] mt2063: add get_if_frequency call linuxtv
2011-12-17 20:57 ` [PATCH 2/3] drxk: correction frontend attatching linuxtv
2011-12-17 23:39 ` Oliver Endriss
2011-12-17 23:47 ` Oliver Endriss
[not found] ` <4EED829E.6020407@stefanringel.de>
2012-01-05 20:46 ` Mauro Carvalho Chehab [this message]
2011-12-18 6:03 ` Stefan Ringel
2011-12-17 20:57 ` [PATCH 3/3] cx23885: add Terratec Cinergy T pcie dual linuxtv
2011-12-17 21:54 ` [PATCH 1/3] mt2063: add get_if_frequency call Antti Palosaari
2011-12-17 21:59 ` 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=4F060C2D.6070107@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=linuxtv@stefanringel.de \
--cc=o.endriss@gmx.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 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.