Lars,
Thank you for your comments / thoughts...
On Thu, Jan 24, 2013 at 1:54 AM, Lars-Peter Clausen <lars@xxxxxxxxxx> wrote:
> adc: adc@12D10000 {
>
> #io-channel-cells = <1>;
> io-channel-output-names = "adc1", "adc2", ...;
>
> ncp15wb473@0 {
> compatible = "ntc,ncp15wb473";
> ...
> io-channels = <&adc 0>; // First ADC channel
I'm not an expert, but I think the typical way is:
* No need to include a handle to &adc. It's logically our parent. In
a similar way i2c devices don't specify their parent bus--they are
just listed under it.
* The "0" should be specified with reg = <0>
Everything else about this syntax looks good.
To implement this I'd imagine that we'll need a new API call, right?
In this case the thermistor driver won't know the name of the channel.
It can find the ADC (the struct device and probably other things) and
knows a channel index. Am I understanding properly?
I think Naveen expressed the same question, though he said it a bit
differently than me.
-Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
