From: Vignesh R <vigneshr@ti.com>
To: John Syne <john3909@gmail.com>
Cc: Lee Jones <lee.jones@linaro.org>,
"N, Mugunthan V" <mugunthanvnm@ti.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Jonathan Cameron <jic23@kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Nori, Sekhar" <nsekhar@ti.com>,
"Ujfalusi, Peter" <peter.ujfalusi@ti.com>
Subject: Re: [PATCH] drivers: mfd: ti_am335x_tscadc: increase ADC ref clock to 24MHz
Date: Fri, 11 Nov 2016 11:47:19 +0530 [thread overview]
Message-ID: <e83fb53b-94ab-4273-a7d0-410013bc0dc4@ti.com> (raw)
In-Reply-To: <30CF3CC1-A4F1-4C31-B51F-A1AB1D352AF5@gmail.com>
On Friday 11 November 2016 09:00 AM, John Syne wrote:
>
>> On Nov 9, 2016, at 9:07 PM, Vignesh R <vigneshr@ti.com> wrote:
>>
>> Hi,
>>
>> On Thursday 10 November 2016 05:23 AM, John Syne wrote:
>>> OK, then back to my original question. Given that these DT properties are supported in the driver
>>>
>>
>> Below properties are supported by only by ti_am3335x_adc driver and not
>> ti_am335x_tsc driver. As author of this patch pointed out in another
>> reply, there is no need to change step-opendelay for tsc. AFAIK, I don't
>> see a use case where these values needs to be tweaked for tsc channels,
>> therefore it does not make sense to be DT properties.
> Yeah, the confusion was mine because the author of this patch series was proposing to hard code these settings while DT properties already existed in the ti_am335x_adc driver. I use the ADC for sensor measurement and do not use the touchscreen features. I already pointed out where these DT parameters should be added by referencing how this was done in one of the BBB DT overlay files [1]. I am just proposing the same is done as a default in the AM33xx.dtsi and AM4372.dtsi files. Here is what I was proposing.
> Granted, the adc-channels should be restricted to the subset of channels not used by tsc, but you get the idea.
There are 4 wire, 5 wire and 8 wire touchscreens. Therefore there is no
way to know in advance, how many channels are available for adc. IMO,
this is not a SoC specific configuration but board dependent. Hence, all
channel related configurations need to be in board specific dts files
and not in top level dtsi files.
>
> tscadc: tscadc@44e0d000 {
> compatible = "ti,am3359-tscadc";
> reg = <0x44e0d000 0x1000>;
> interrupt-parent = <&intc>;
> interrupts = <16>;
> ti,hwmods = "adc_tsc";
> status = "disabled";
> dmas = <&edma 53 0>, <&edma 57 0>;
> dma-names = "fifo0", "fifo1”;
>
> tsc {
> compatible = "ti,am3359-tsc";
> };
> am335x_adc: adc {
> #io-channel-cells = <1>;
> ti,adc-channels = <0 1 2 3 4 5 6>;
> ti,chan-step-avg = <0x16 0x16 0x16 0x16 0x16 0x16 0x16>;
> ti,chan-step-opendelay = <0x98 0x98 0x98 0x98 0x98 0x98 0x98>;
> ti,chan-step-sampledelay = <0x0 0x0 0x0 0x0 0x0 0x0 0x0>;
> compatible = "ti,am3359-adc";
> };
> };
>
> [1]https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/BB-ADC-00A0.dts
>
--
Regards
Vignesh
next prev parent reply other threads:[~2016-11-11 6:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 6:02 Mugunthan V N
2016-10-24 20:58 ` John Syne
2016-10-25 5:52 ` Mugunthan V N
2016-10-25 6:01 ` John Syne
2016-10-25 6:16 ` John Syne
2016-10-25 6:37 ` Vignesh R
2016-10-25 15:39 ` John Syne
2016-10-25 6:38 ` Lee Jones
2016-10-25 15:47 ` John Syne
2016-10-26 8:48 ` Lee Jones
2016-10-27 21:17 ` John Syne
2016-10-31 11:39 ` Vignesh R
2016-11-09 23:53 ` John Syne
2016-11-10 5:07 ` Vignesh R
2016-11-11 3:30 ` John Syne
2016-11-11 6:17 ` Vignesh R [this message]
2016-10-27 11:20 ` Mugunthan V N
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=e83fb53b-94ab-4273-a7d0-410013bc0dc4@ti.com \
--to=vigneshr@ti.com \
--cc=jic23@kernel.org \
--cc=john3909@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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
all inboxes | Powered by JetHome®