linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: "Lars-Peter Clausen" <lars@metafoo.de>
Cc: Hector Palacios <hector.palacios@digi.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"alexandre.belloni@free-electrons.com"
	<alexandre.belloni@free-electrons.com>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"fabio.estevam@freescale.com" <fabio.estevam@freescale.com>
Subject: Re: [PATCH 2/4] iio: mxs-lradc: add scale attribute to channels
Date: Fri, 5 Jul 2013 19:39:21 +0200	[thread overview]
Message-ID: <201307051939.21455.marex@denx.de> (raw)
In-Reply-To: <51D6FDA7.5010301@metafoo.de>

Dear Lars-Peter Clausen,

> On 07/05/2013 06:59 PM, Marek Vasut wrote:
> [...]
> 
> >>> Should the above not be in DT ?
> >> 
> >> Do you mean for example:
> >> 	lradc@80050000 {
> >> 	
> >> 		compatible = "fsl,imx28-lradc";
> >> 		reg = <0x80050000 0x2000>;
> >> 		interrupts = <10 14 15 16 17 18 19
> >> 		
> >> 				20 21 22 23 24 25>;
> >> 		
> >> 		vref = <1850 1850 1850 1850
> >> 		
> >> 			1850 1850 1850 7400
> >> 			1850 1850 3700 1850
> >> 			3700 1850 1850 7400>
> >> 	
> >> 	};
> >> 
> >> I'm ok with it, but are there other examples of driver using a similar
> >> 
> >> approach? I see for example the spear-adc which reads:
> >> 	Optional properties:
> >> 	- vref-external: External voltage reference in milli-volts. If omitted
> >> 	
> >> 	  the internal voltage reference will be used.
> >> 
> >> which makes me believe the 'internal voltage reference' is hardcoded in
> >> the driver. More opinions?
> > 
> > I'd duke this one out on devicetree-discuss@ list. In general, I'd use
> > something like fsl,vref prop, but this really better be discussed in a
> > separate thread.
> > 
> > On the other hand, I'd hate to keep these patches here waiting , so maybe
> > we should apply them as-is and remove this part from the driver in a
> > subsequent patch? What do you say, Lars ?
> 
> I'd leave it as it is. I don't see much point in putting them into the
> devicetree, it would have made sense if the scales were board specific.

They are CPU specific, therefore if we have a new CPU with different scale setup 
(again), we will need to add another table here. That's why I'd vouch for having 
them in DT. As we already saw in the past, FSL did merge some MX23/28 components 
into MX53 and MX6Q.

Best regards,
Marek Vasut

  reply	other threads:[~2013-07-05 17:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05  8:30 [PATCH 0/4] iio: mxs-lradc: add support to optional divider_by_two Hector Palacios
2013-07-05  8:30 ` [PATCH 1/4] iio: mxs-lradc: change the realbits to 12 Hector Palacios
2013-07-05 11:37   ` Marek Vasut
2013-07-05 12:40     ` Hector Palacios
2013-07-05 13:10       ` Marek Vasut
2013-07-05 14:35         ` Hector Palacios
2013-07-05 17:17           ` Lars-Peter Clausen
2013-07-06 10:08             ` Jonathan Cameron
2013-07-06 10:13               ` Marek Vasut
2013-07-10 10:47         ` Hector Palacios
2013-07-10 11:49           ` Marek Vasut
2013-07-10 14:45             ` Hector Palacios
2013-07-10 15:22               ` Marek Vasut
2013-07-05  8:30 ` [PATCH 2/4] iio: mxs-lradc: add scale attribute to channels Hector Palacios
2013-07-05 10:32   ` Lars-Peter Clausen
2013-07-05 15:49     ` Hector Palacios
2013-07-05 16:56       ` Marek Vasut
2013-07-05 11:41   ` Marek Vasut
2013-07-05 16:42     ` Hector Palacios
2013-07-05 16:59       ` Marek Vasut
2013-07-05 17:08         ` Lars-Peter Clausen
2013-07-05 17:39           ` Marek Vasut [this message]
2013-07-06  9:59         ` Jonathan Cameron
2013-07-05  8:30 ` [PATCH 3/4] iio: mxs-lradc: add scale_available file " Hector Palacios
2013-07-05 10:40   ` Lars-Peter Clausen
2013-07-08  8:27     ` Hector Palacios
2013-07-08  8:42       ` Lars-Peter Clausen
2013-07-05 11:46   ` Marek Vasut
2013-07-08  8:51     ` Hector Palacios
2013-07-08 13:05       ` Marek Vasut
2013-07-05  8:30 ` [PATCH 4/4] iio: mxs-lradc: add write_raw function to modify scale Hector Palacios
2013-07-05 10:41   ` Lars-Peter Clausen

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=201307051939.21455.marex@denx.de \
    --to=marex@denx.de \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=fabio.estevam@freescale.com \
    --cc=hector.palacios@digi.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    /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).