From: Paul Walmsley <pwalmsley@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Andrew Chew <achew@nvidia.com>,
Matthew Longnecker <mlongnecker@nvidia.com>
Subject: Re: [PATCH] regulator: core: add regulator_get_linear_step()
Date: Fri, 7 Jun 2013 10:11:51 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1306071010380.32163@utopia.booyaka.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1306071000330.32163@utopia.booyaka.com>
On Fri, 7 Jun 2013, Paul Walmsley wrote:
> The IP block has an I2C controller embedded in it that autonomously sends
> set-voltage commands (across a range of voltages) to the PMIC. To enable
> that, the driver must first initialize the IP block with a
> voltage-to-selector table.
Here's the table loading code -
+/**
+ * _load_lut - load voltage lookup table into DFLL RAM
+ * @pdev: DFLL instance
+ *
+ * Load the voltage-to-PMIC register value lookup table into the DFLL
+ * IP block LUT memory. td->lut_min and td->lut_max are used to cap
+ * the minimum and maximum voltage requested. This function shouldn't
+ * be called directly by code other than dfll_load_lut(), since this
+ * function doesn't handle the necessary pre- and post-requisites. No
+ * return value.
+ */
+static void _load_lut(struct platform_device *pdev)
+{
+ struct tegra_dfll *td = dev_get_drvdata(&pdev->dev);
+ int i;
+ u32 val;
+
+ val = td->out_map[td->lut_min]->reg_value;
+ for (i = 0; i <= td->lut_min; i++)
+ dfll_writel(td, val, DFLL_OUTPUT_LUT + i * 4);
+
+ for (; i < td->lut_max; i++) {
+ val = td->out_map[i]->reg_value;
+ dfll_writel(td, val, DFLL_OUTPUT_LUT + i * 4);
+ }
+
+ val = td->out_map[td->lut_max]->reg_value;
+ for (; i < td->num_voltages; i++)
+ dfll_writel(td, val, DFLL_OUTPUT_LUT + i * 4);
+
+ dfll_wmb(td);
+}
- Paul
next prev parent reply other threads:[~2013-06-07 10:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 8:06 Paul Walmsley
2013-06-07 9:09 ` Mark Brown
2013-06-07 9:38 ` Paul Walmsley
2013-06-07 9:59 ` Mark Brown
2013-06-07 10:03 ` Paul Walmsley
2013-06-07 10:11 ` Paul Walmsley [this message]
2013-06-07 10:18 ` Mark Brown
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=alpine.DEB.2.02.1306071010380.32163@utopia.booyaka.com \
--to=pwalmsley@nvidia.com \
--cc=achew@nvidia.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mlongnecker@nvidia.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®