public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Akihiro TSUKADA <tskd08@gmail.com>
To: linux-media@vger.kernel.org, mchehab@osg.samsung.com
Subject: dvb-core: how should i2c subdev drivers be attached?
Date: Thu, 9 Jun 2016 21:49:33 +0900	[thread overview]
Message-ID: <52775753-47c4-bfdf-b8f5-48bdf8ceb6e5@gmail.com> (raw)

Hi,
excuse me for taking up a very old post again,
but I'd like to know the status of the patch:
  https://patchwork.linuxtv.org/patch/27922/
, which provides helper code for defining/loading i2c DVB subdev drivers.

Was it rejected and 
each i2c demod/tuner drivers should provide its own version of "attach" code?
Or is it acceptable (with some modifications) ?

Although not many drivers currently use i2c binding model (and use dvb_attach()),
but I expect that coming DVB subdev drivers will have a similar attach code,
including module request/ref-counting, device creation,
(re-)using i2c_board_info.platformdata to pass around both config parameters
and the resulting i2c_client* & dvb_frontend*.

Since I have a plan to split out demod/tuner drivers from pci/pt1 dvb-usb/friio
integrated drivers (because those share the tc90522 demod driver with pt3, and
friio also shares the bridge chip with gl861),
it would be nice if I can use the helper code,
instead of re-iterating similar "attach" code.

--
akihiro

             reply	other threads:[~2016-06-09 12:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 12:49 Akihiro TSUKADA [this message]
2016-06-09 15:24 ` dvb-core: how should i2c subdev drivers be attached? Mauro Carvalho Chehab
2016-06-09 15:41   ` Antti Palosaari
2016-06-09 16:18     ` Mauro Carvalho Chehab
2016-06-09 16:38       ` Antti Palosaari
2016-06-09 18:30         ` Mauro Carvalho Chehab
2016-06-09 19:14           ` Antti Palosaari
2016-06-09 19:35             ` Mauro Carvalho Chehab
2016-06-09 20:24               ` Antti Palosaari
2016-06-09 17:38   ` Akihiro TSUKADA

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=52775753-47c4-bfdf-b8f5-48bdf8ceb6e5@gmail.com \
    --to=tskd08@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.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