From: Wolfram Sang <wsa@the-dreams.de>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, Marek Vasut <marek.vasut+renesas@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Simon Horman <horms+renesas@verge.net.au>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: Re: [PATCH] ARM: dts: stout: Initial r8a7790 Stout board support
Date: Wed, 14 Feb 2018 07:05:47 +0100 [thread overview]
Message-ID: <20180214060547.bf6upib2mbgoexas@katana> (raw)
In-Reply-To: <20180213232948.31521-1-marek.vasut+renesas@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
> + chosen {
> + bootargs = "ignore_loglevel rw root=/dev/nfs ip=dhcp";
> + stdout-path = "serial0:38400n8";
Hmm, that would be our first board to not have 115200, or? We already
have some other boards upstream where UBoot has 38400 and Linux 115200.
I'd prefer consistency here a little, but no strong opinion and asking
for other opinions.
> + vcc_sdhi0: regulator-vcc-sdhi0 {
> + compatible = "regulator-fixed";
> +
> + regulator-name = "SDHI0 Vcc";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> +
> + gpio = <&gpio5 24 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> + };
Just double checking: No 1.8V for SDR50/104?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-14 6:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 23:29 [PATCH] ARM: dts: stout: Initial r8a7790 Stout board support Marek Vasut
2018-02-14 6:05 ` Wolfram Sang [this message]
2018-02-14 8:28 ` Geert Uytterhoeven
[not found] ` <CAMuHMdUYDWXF9uSzsYEOeOVysQKRSFhJ+bLbPhwFbMs-qBjbcA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-14 8:52 ` Wolfram Sang
2018-02-14 10:21 ` Marek Vasut
2018-02-14 9:11 ` Geert Uytterhoeven
[not found] ` <CAMuHMdUuuokCjJ-uz1+JMFLF5zytiB6gjhVC1Xtys_rWdFnPhg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-02-15 9:59 ` Marek Vasut
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=20180214060547.bf6upib2mbgoexas@katana \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=marek.vasut@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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