From: Tomasz Figa <tomasz.figa@gmail.com>
To: Doug Anderson <dianders@chromium.org>,
Arun Kumar K <arun.kk@samsung.com>
Cc: linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Olof Johansson <olofj@google.com>,
Tomasz Figa <t.figa@samsung.com>,
Sachin Kamat <sachin.kamat@linaro.org>,
Tushar Behera <tushar.behera@linaro.org>,
Arun Kumar <arunkk.samsung@gmail.com>
Subject: Re: [PATCH v3 2/2] ARM: dts: Add peach-pit board support
Date: Thu, 01 May 2014 19:30:52 +0200 [thread overview]
Message-ID: <536284CC.80603@gmail.com> (raw)
In-Reply-To: <CAD=FV=UmWZapMZgpwdonr-JOE7BB8ELn5DQCFWos_sC1v-eLzw@mail.gmail.com>
On 01.05.2014 17:40, Doug Anderson wrote:
> Arun,
>
> On Wed, Apr 30, 2014 at 4:08 AM, Arun Kumar K <arun.kk@samsung.com> wrote:
>> + memory {
>> + reg = <0x20000000 0x80000000>;
>
> As mentioned in the other thread, I think this should be 0 0
I guess it may depend on your boards, but DT might contain safe default
configuration that would work on all variants, so if you have for
example 1 GiB and 2 GiB variants, 1 GiB configuration here should be
fine to get the board running even without a bootloader that could
inject remaining data.
>
>> +&pinctrl_0 {
>> + tpm_irq: tpm-irq {
>> + samsung,pins = "gpx1-0";
>> + samsung,pin-function = <0>;
>> + samsung,pin-pud = <0>;
>
> Is there any way to use the #defines PIN_PULL_NONE here?
I wonder if we already have this kind of #define defined. Keep in mind
that this value is specific for Exynos SoCs, so we would need to define
it in Exynos-specific header, like include/dt-bindings/pinctrl/exynos.h.
>
>> +&pinctrl_3 {
>> + backlight_pwm: backlight-pwm {
>> + samsung,pins = "gpb2-0";
>> + samsung,pin-function = <2>;
>> + samsung,pin-pud = <0>;
>> + samsung,pin-drv = <0>;
>> + };
>
> The PWM probably belongs in exynos5420-pinctrl.dtsi (though you'd need
> to call it by a more generic name since it could be used for something
> other than a backlight).
Yes, please add generic pinctrl nodes for all PWM outputs on the SoC to
exynos5420-pinctrl.dtsi, as done in exynos4x12-pinctrl.dtsi (see
pwmX-out nodes).
Best regards,
Tomasz
next prev parent reply other threads:[~2014-05-01 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 11:08 [PATCH v3 0/2] Add peach-pit board support Arun Kumar K
2014-04-30 11:08 ` [PATCH v3 1/2] ARM: dts: Add node references to 5420 Arun Kumar K
[not found] ` <1398856138-18837-2-git-send-email-arun.kk-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-05-01 15:09 ` Doug Anderson
2014-05-01 17:25 ` Tomasz Figa
2014-05-02 4:16 ` Arun Kumar K
2014-04-30 11:08 ` [PATCH v3 2/2] ARM: dts: Add peach-pit board support Arun Kumar K
2014-05-01 15:40 ` Doug Anderson
2014-05-01 17:30 ` Tomasz Figa [this message]
2014-05-01 17:45 ` Doug Anderson
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=536284CC.80603@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=arun.kk@samsung.com \
--cc=arunkk.samsung@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olofj@google.com \
--cc=sachin.kamat@linaro.org \
--cc=t.figa@samsung.com \
--cc=tushar.behera@linaro.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).