From: Jonathan Cameron <jic23@kernel.org>
To: Andreas Klinger <ak@it-klinger.de>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
robh+dt@kernel.org, mark.rutland@arm.com, mchehab@kernel.org,
davem@davemloft.net, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, linus.walleij@linaro.org,
rdunlap@infradead.org, devicetree@vger.kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/3] iio: hx711: add delay until DOUT is ready
Date: Sun, 15 Jul 2018 09:38:43 +0100 [thread overview]
Message-ID: <20180715093843.11e86d5f@archlinux> (raw)
In-Reply-To: <20180710181903.GA5386@arbeit>
On Tue, 10 Jul 2018 20:19:03 +0200
Andreas Klinger <ak@it-klinger.de> wrote:
> On a system with parasitic capacitance it turned out that DOUT is not ready
> after 100 ns after PD_SCK has raised. A measurement showed almost 1000 ns
> until DOUT has reached its correct value.
>
> With this patch its now possible to wait until data is ready.
>
> The wait time should not be higher than the maximum PD_SCK high time which
> is corresponding to the datasheet 50000 ns.
>
> Signed-off-by: Andreas Klinger <ak@it-klinger.de>
Applied, thanks.
Jonathan
> ---
> drivers/iio/adc/hx711.c | 39 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
>
> diff --git a/drivers/iio/adc/hx711.c b/drivers/iio/adc/hx711.c
> index 9430b54121e0..36b59d8957fb 100644
> --- a/drivers/iio/adc/hx711.c
> +++ b/drivers/iio/adc/hx711.c
> @@ -97,6 +97,14 @@ struct hx711_data {
> * 2x32-bit channel + 64-bit timestamp
> */
> u32 buffer[4];
> + /*
> + * delay after a rising edge on SCK until the data is ready DOUT
> + * this is dependent on the hx711 where the datasheet tells a
> + * maximum value of 100 ns
> + * but also on potential parasitic capacities on the wiring
> + */
> + u32 data_ready_delay_ns;
> + u32 clock_frequency;
> };
>
> static int hx711_cycle(struct hx711_data *hx711_data)
> @@ -110,6 +118,14 @@ static int hx711_cycle(struct hx711_data *hx711_data)
> */
> preempt_disable();
> gpiod_set_value(hx711_data->gpiod_pd_sck, 1);
> +
> + /*
> + * wait until DOUT is ready
> + * it turned out that parasitic capacities are extending the time
> + * until DOUT has reached it's value
> + */
> + ndelay(hx711_data->data_ready_delay_ns);
> +
> val = gpiod_get_value(hx711_data->gpiod_dout);
> /*
> * here we are not waiting for 0.2 us as suggested by the datasheet,
> @@ -120,6 +136,12 @@ static int hx711_cycle(struct hx711_data *hx711_data)
> gpiod_set_value(hx711_data->gpiod_pd_sck, 0);
> preempt_enable();
>
> + /*
> + * make it a square wave for addressing cases with capacitance on
> + * PC_SCK
> + */
> + ndelay(hx711_data->data_ready_delay_ns);
> +
> return val;
> }
>
> @@ -458,6 +480,7 @@ static const struct iio_chan_spec hx711_chan_spec[] = {
> static int hx711_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> + struct device_node *np = dev->of_node;
> struct hx711_data *hx711_data;
> struct iio_dev *indio_dev;
> int ret;
> @@ -530,6 +553,22 @@ static int hx711_probe(struct platform_device *pdev)
> hx711_data->gain_set = 128;
> hx711_data->gain_chan_a = 128;
>
> + hx711_data->clock_frequency = 400000;
> + ret = of_property_read_u32(np, "clock-frequency",
> + &hx711_data->clock_frequency);
> +
> + /*
> + * datasheet says the high level of PD_SCK has a maximum duration
> + * of 50 microseconds
> + */
> + if (hx711_data->clock_frequency < 20000) {
> + dev_warn(dev, "clock-frequency too low - assuming 400 kHz\n");
> + hx711_data->clock_frequency = 400000;
> + }
> +
> + hx711_data->data_ready_delay_ns =
> + 1000000000 / hx711_data->clock_frequency;
> +
> platform_set_drvdata(pdev, indio_dev);
>
> indio_dev->name = "hx711";
prev parent reply other threads:[~2018-07-15 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 18:19 [PATCH v5 2/3] iio: hx711: add delay until DOUT is ready Andreas Klinger
2018-07-15 8:38 ` Jonathan Cameron [this message]
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=20180715093843.11e86d5f@archlinux \
--to=jic23@kernel.org \
--cc=ak@it-klinger.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=rdunlap@infradead.org \
--cc=robh+dt@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).