From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media <linux-media@vger.kernel.org>,
Patrick Boettcher <pboettcher@kernellabs.com>
Subject: Re: [RFCv1] DVB-USB improvements [alternative 2]
Date: Fri, 25 May 2012 20:44:29 +0300 [thread overview]
Message-ID: <4FBFC4FD.50108@iki.fi> (raw)
In-Reply-To: <4FB9BB75.9040703@redhat.com>
On 21.05.2012 06:50, Mauro Carvalho Chehab wrote:
> Em 20-05-2012 17:55, Antti Palosaari escreveu:
>> I did some more planning and made alternative RFC.
>> As the earlier alternative was more like changing old functionality that new one goes much more deeper.
>>
>> As a basic rule I designed it to reduce stuff from the current struct dvb_usb_device_properties. Currently there is many nested structs introducing same callbacks. For that one I dropped all frontend and adapter level callbacks to device level. Currently struct contains 2 adapters and 3 frontends - which means we have 2 * 3 = 6 "similar" callbacks and only 1 is used. It wastes some space since devices having more than one adapter or frontend are rather rare. Making callback selection inside individual driver is very trivial even without a designated callback. Here is common example from the use of .frontend_attach() callback in case of only one callback used:
>> static int frontend_attach(struct dvb_usb_adapter *adap)
>> {
>> if (adap->id == 0)
>> return frontend_attach_1();
>> else
>> return frontend_attach_2();
>> }
>>
>> Functionality enhancement mentioned earlier RFC are valid too:
>> http://www.mail-archive.com/linux-media@vger.kernel.org/msg46352.html
>>
>> As I was a little bit lazy I wrote only quick skeleton code to represent new simplified "struct dvb_usb_device_properties":
>>
>> struct dvb_usb_device_properties = {
>> /* download_firmware() success return values to signal what happens next */
>> #define RECONNECTS_USB (1<< 0)
>> #define RECONNECTS_USB_USING_NEW_ID (1<< 1)
>>
>> .size_of_priv = sizeof(struct 'state'),
>>
>> /* firmware download */
>> .identify_state(struct dvb_usb_device *d, int *cold),
>> .get_firmware_name(struct dvb_usb_device *d, char *firmware_name),
>> .download_firmware(struct dvb_usb_device *d, const struct firmware *fw),
>> .allow_dynamic_id = true,
>>
>> .power_ctrl(struct dvb_usb_device *d, int onoff),
>> .read_config(struct dvb_usb_device *d, u8 mac[6]),
>> .get_adapter_count(struct dvb_usb_device *d, int *count),
>>
>> .frontend_attach(struct dvb_usb_adapter *adap),
>> .tuner_attach(struct dvb_usb_adapter *adap),
>>
>> .init(struct dvb_usb_device *d),
>>
>> .get_rc(struct dvb_rc *),
>> .i2c_algo = (struct i2c_algorithm),
>>
>> .frontend_ctrl(struct dvb_frontend *fe, int onoff),
>> .get_stream_props(struct usb_data_stream_properties *),
>> .streaming_ctrl(struct dvb_usb_adapter *adap, int onoff),
>>
>> .generic_bulk_ctrl_endpoint = (int),
>> .generic_bulk_ctrl_endpoint_response = (int),
>>
>> .devices = (struct dvb_usb_device)[],
>> };
>>
>> struct dvb_usb_device dvb_usb_devices {
>> char *name = "name",
>> .rc_map = RC_MAP_EMPTY,
>> .device_id = (struct usb_device_id),
>> }
>
> It looks OK to me. It may make sense to add an optional
> per-device field, to allow drivers to add more board-specific
> information, if they need, in order to avoid duplicating
> things there.
>
> Another option would be for the drivers to do:
>
> struct dvb_usb_drive_foo dvb_usb_driver_foo {
> struct dvb_usb_device dvb_usb_devices dvb_usb_dev;
> int foo;
> long bar;
> ...
> }
>
> And, inside the core, use the container_of() macro to go from
> the device-specific table to struct dvb_usb_device.
>
> This way, simple drivers can do just:
>
> struct dvb_usb_drive_foo dvb_usb_driver_foo {
> struct dvb_usb_device dvb_usb_devices dvb_usb_dev;
> }
>
> And complex drivers can add more stuff there.
I have now implemented some basic stuff. Most interesting is new way of
map device id and properties for it. I found that I can use .driver_info
field from the (struct usb_device_id) to carry pointer. I used it to
carry all the other data to the DVB USB core. Thus that one big issue is
now resolved. It reduces something like 8-9 kB of binary size which is
huge improvement. Same will happen for every driver using multiple
(struct dvb_usb_device_properties) - for more you are used more you save.
Here is 3 example drivers I have converted to that new style:
http://palosaari.fi/linux/v4l-dvb/dvb-usb-2012-05-25/
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-05-25 17:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 20:55 [RFCv1] DVB-USB improvements [alternative 2] Antti Palosaari
2012-05-20 22:30 ` VDR User
2012-05-20 23:10 ` Devin Heitmueller
2012-05-21 0:36 ` VDR User
2012-05-21 2:22 ` Antti Palosaari
2012-05-21 2:42 ` VDR User
2012-05-21 3:20 ` Antti Palosaari
2012-05-21 3:44 ` Mauro Carvalho Chehab
2012-05-21 3:50 ` Mauro Carvalho Chehab
2012-05-25 17:44 ` Antti Palosaari [this message]
2012-05-25 17:48 ` Antti Palosaari
2012-05-25 18:32 ` Mauro Carvalho Chehab
2012-05-25 18:38 ` Mauro Carvalho Chehab
2012-05-25 18:51 ` Antti Palosaari
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=4FBFC4FD.50108@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=pboettcher@kernellabs.com \
/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).