From: Sascha Hauer <sha@pengutronix.de>
To: Michael Riesch <michael.riesch@wolfvision.net>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] aiodev: add driver for Rockchip SARADC
Date: Mon, 21 Jun 2021 06:30:36 +0200 [thread overview]
Message-ID: <20210621043036.GE9782@pengutronix.de> (raw)
In-Reply-To: <20210617143654.32616-1-michael.riesch@wolfvision.net>
Hi Michael,
On Thu, Jun 17, 2021 at 04:36:54PM +0200, Michael Riesch wrote:
> +static int rockchip_saradc_read(struct aiochannel *chan, int *val)
> +{
> + struct rockchip_saradc_data *data;
> + int timeout = SARADC_TIMEOUT;
> + u32 value = 0;
> + u32 control = 0;
> + u32 mask;
> +
> + if (!chan || !val)
> + return -EINVAL;
> +
> + data = container_of(chan->aiodev, struct rockchip_saradc_data, aiodev);
> + if (!data)
> + return -EINVAL;
> +
> + rockchip_saradc_reg_wr(data, 8, SARADC_DLY_PU_SOC);
> + rockchip_saradc_reg_wr(data,
> + (chan->index & SARADC_CTRL_CHN_MASK) |
> + SARADC_CTRL_IRQ_ENABLE |
> + SARADC_CTRL_POWER_CTRL,
> + SARADC_CTRL);
> +
> + do {
> + control = rockchip_saradc_reg_rd(data, SARADC_CTRL);
> +
> + if (--timeout == 0)
> + return -ETIMEDOUT;
> + mdelay(1);
> + } while (!(control & SARADC_CTRL_IRQ_STATUS));
You should do a timeout loop with
u64 start = get_time_ns();
do {
if (is_timeout(start, 100 * MSECOND)
return -ETIMEDOUT;
} while(bar);
We don't have any way nor need to put the CPU into idle, so we can poll
as fast as we can.
> +
> + mask = (1 << data->config->num_bits) - 1;
> + value = rockchip_saradc_reg_rd(data, SARADC_DATA) & mask;
> + rockchip_saradc_reg_wr(data, 0, SARADC_CTRL);
> +
> + printf("Raw value: %d\n", value);
Debugging leftover.
> +fail_channels:
> + kfree(data->channels);
> + kfree(data->aiodev.channels);
> +
> +fail_data:
> + kfree(data);
> + return ret;
> +}
> +
> +static const struct rockchip_saradc_cfg rk3568_saradc_cfg = {
> + .ref_voltage_mv = 1800,
>From looking at the downstream dts files this doesn't seem to be SoC
specific:
&saradc {
status = "okay";
vref-supply = <&vcca_1v8>;
};
I suggest doing the same here.
> + .num_bits = 10,
> + .num_channels = 8,
> +};
> +
> +static const struct of_device_id of_rockchip_saradc_match[] = {
> + { .compatible = "rockchip,rk3568-saradc", .data = &rk3568_saradc_cfg },
The device nodes in the downstream Kernel also contain some clocks.
These should be handled in the driver.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-06-21 4:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 14:36 Michael Riesch
2021-06-21 4:30 ` Sascha Hauer [this message]
2021-06-21 11:27 ` Michael Riesch
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=20210621043036.GE9782@pengutronix.de \
--to=sha@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
/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