Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Hiremath, Vaibhav" <hvaibhav@ti.com>
Cc: "dbrownell@users.sourceforge.net"
	<dbrownell@users.sourceforge.net>,
	"video4linux-list@redhat.com" <video4linux-list@redhat.com>,
	"davinci-linux-open-source-bounces@linux.davincidsp.com"
	<davinci-linux-open-source-bounces@linux.davincidsp.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Jadav, Brijesh R" <brijesh.j@ti.com>,
	"Shah, Hardik" <hardik.shah@ti.com>,
	"Hadli, Manjunath" <mrh@ti.com>, "R, Sivaraj" <sivaraj@ti.com>,
	"Karicheri, Muralidharan" <m-karicheri2@ti.com>
Subject: Re: [PATCH 2/2] TVP514x Driver with Review comments fixed
Date: Tue, 2 Dec 2008 00:34:52 -0800	[thread overview]
Message-ID: <200812020034.53544.david-b@pacbell.net> (raw)
In-Reply-To: <200812012238.54240.david-b@pacbell.net>

On Monday 01 December 2008, David Brownell wrote:
> >         - Pointer to init_reg_seq, which is pointer to array of structure
> >           for tvp514x_regs. This is little bit ugly, since will have to 
> >           export tvp514x_regs structure.
> 
> The platform_data should not hold such stuff; it's not board-specific.
> I'd expect platform_data to hold regulator_init_data as needed to
> instantiate the regulator; and maybe other stuff needed on this board
> too.  Floor and ceiling parameters, maybe, unless they change at runtime.

Apologies, I was confusing this driver with another.  For a video
codec, the platform_data should say things like which of the dozen
or so input channels are wired up, and how; and how the outputs
are encoded (8 bits, 2x 8 bits, 10 bits, 2x 10 bits, etc).  Nothing
to do with regulators or DVFS.

And the id parameter to probe() is enough to tell whether this is
a '46 device, with extra registers and input channels, or a '47
that's less capable (but lower power, etc).

 
> The init sequence wouldn't matter at all for i2c_get_clientdata(),
> since it should only kick in during probe().


--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-12-02  8:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 12:43 [PATCH 2/2] TVP514x Driver with Review comments fixed hvaibhav
2008-11-28 16:26 ` David Brownell
2008-11-28 16:33 ` David Brownell
2008-11-28 18:34   ` Hiremath, Vaibhav
2008-11-28 16:52 ` David Brownell
2008-11-28 18:51   ` Hiremath, Vaibhav
2008-11-28 19:50     ` David Brownell
2008-11-28 19:54       ` David Brownell
2008-12-02  5:39         ` Hiremath, Vaibhav
2008-12-02  6:38           ` David Brownell
2008-12-02  6:49             ` Hiremath, Vaibhav
2008-12-02  8:26               ` David Brownell
2008-12-02  8:34             ` David Brownell [this message]
2008-12-02  8:40               ` Hiremath, Vaibhav
     [not found] <hvaibhav@ti.com>
2008-11-26 17:05 ` hvaibhav
2008-11-26 17:48   ` Hans Verkuil

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=200812020034.53544.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=brijesh.j@ti.com \
    --cc=davinci-linux-open-source-bounces@linux.davincidsp.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=hardik.shah@ti.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=m-karicheri2@ti.com \
    --cc=mrh@ti.com \
    --cc=sivaraj@ti.com \
    --cc=video4linux-list@redhat.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