From: Chris Desjardins <chris.desjardins-8HJrC8Or5ylBDgjK7y7TUQ@public.gmane.org>
To: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] ARM: tegra: Add basic support for carma devkit
Date: Tue, 25 Jun 2013 15:47:38 +0000 (UTC) [thread overview]
Message-ID: <loom.20130625T165829-570@post.gmane.org> (raw)
In-Reply-To: 51C87FA5.3000306@wwwdotorg.org
Stephen Warren <swarren@...> writes:
>
> On 06/23/2013 07:38 AM, Chris Desjardins wrote:
>
>
> > + serial <at> 70006200 {
> > + compatible = "ns16550";
>
> You shouldn't need to set the compatible value for this node;
> tegra30.dtsi has already set it.
True, but it is set to "nvidia,tegra30-uart", "nvidia,tegra20-uart" which
causes the nvidia high speed uart driver to be loaded, which sucks when you
are debugging over serial (which is my normal mode of operation) and half
way through the boot process your serial port goes away because the ns16550
driver you were using was unloaded and the high speed uart driver was loaded
instead... If it is all the same I would rather just keep the old reliable
driver loaded on this port (it is the only exposed serial port on the carma
devkit), and I suspect other developers will feel the same...
>
> > + tps62361 {
> ...
> > + regulator-min-microvolt = <500000>;
> > + regulator-max-microvolt = <1500000>;
> ...
> > + pmic: tps65911 <at> 2d {
> ...
> > + regulators {
> > + vdd1_reg: vdd1 {
> > + regulator-name = "vddio_ddr_1v2";
> > + regulator-min-microvolt = <1200000>;
> > + regulator-max-microvolt = <1200000>;
>
> Have you validated all these voltage levels, and *-supply properties
> against the schematic or other documentation for the board? I want to
> avoid accepting a DT file that sets up any of the voltages incorrectly,
> which could potentially cause damage to the board/components.
I have not, I will ask Seco if they can supply such documents or verify the
settings themselves, but the documentation they supply does not include any
information in this area. I can say that my board runs fine with these
settings...
> > + clocks {
> > + compatible = "simple-bus";
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + clk32k_in: clock {
> > + compatible = "fixed-clock";
> > + reg=<0>;
> > + #clock-cells = <0>;
> > + clock-frequency = <32768>;
> > + };
> > + };
>
> That doesn't seem to be used anywhere.
>
The clk32k_in is used in tegra30.dtsi...
>
> Out of curiosity, do you have upstream U-Boot support for Carma, or are
> you using our binary bootloader, or a downstream U-Boot?
>
The u-boot that was supplied by nvidia works fine for me, so I am just using
it. It is old, but it works and I don't have any reason to fiddle with it,
they also provided the source, so I can tweak it if necessary, but so far I
haven't had to touch it.
Stand by for 2 updated patches.
Thanks,
Chris D.
next prev parent reply other threads:[~2013-06-25 15:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 13:38 [PATCH 1/1] ARM: tegra: Add basic support for carma devkit Chris Desjardins
2013-06-23 13:54 ` Chris Desjardins
[not found] ` <1371994685-4997-1-git-send-email-chris.desjardins-8HJrC8Or5ylBDgjK7y7TUQ@public.gmane.org>
2013-06-24 17:19 ` Stephen Warren
2013-06-25 15:47 ` Chris Desjardins [this message]
[not found] ` <loom.20130625T165829-570-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2013-06-25 16:06 ` Stephen Warren
2013-06-27 16:59 ` Eric Brower
[not found] ` <51CC6F83.2010606-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-06-27 17:51 ` Stephen Warren
[not found] ` <51CC7B98.5090103-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-06-27 18:23 ` Thierry Reding
2013-08-27 7:56 ` Thierry Reding
[not found] ` <CAGjquTQe0_+oEtyuF0Q0T8rZnQmz1h45T18zePe+BHVTjVQW_Q@mail.gmail.com>
[not found] ` <CAGjquTQe0_+oEtyuF0Q0T8rZnQmz1h45T18zePe+BHVTjVQW_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-27 9:19 ` Fwd: " Chris Desjardins
2013-08-27 10:56 ` Thierry Reding
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=loom.20130625T165829-570@post.gmane.org \
--to=chris.desjardins-8hjrc8or5ylbdgjk7y7tuq@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.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