From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Andrew Chew <achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2 v4] ARM: tegra: fix the status of PWM nodes
Date: Wed, 13 Mar 2013 10:19:10 -0600 [thread overview]
Message-ID: <5140A6FE.8070504@wwwdotorg.org> (raw)
In-Reply-To: <1363131651-13734-2-git-send-email-achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 03/12/2013 05:40 PM, Andrew Chew wrote:
> We should be defining the PWM nodes with status as "disabled" in the
> chip-specific dtsi file, since we don't know whether specific boards
> will use the PWM or not. This patch fixes the PWM node status for
> Tegra20 and Tegra30.
>
> Also fixed the one user of PWM, which is the Tegra20 medcom-wide board,
> so that PWM is set to "okay" in the board-specific dts file.
I've applied this series to Tegra's for-3.10/dt branch.
> diff --git a/arch/arm/boot/dts/tegra20-medcom-wide.dts b/arch/arm/boot/dts/tegra20-medcom-wide.dts
> + pwm: pwm {
> + status = "okay";
> + }
> +
There's also a syntax error here; there needs to be a ; after the }. I
also fixed this up when I applied it.
BTW, "PATCH 2/2 v4" is more typically written "PATCH V4 2/2". Using "git
format-patch --subject-prefix='PATCH V4'" can help automate that a little.
prev parent reply other threads:[~2013-03-13 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 23:40 [PATCH 1/2 v4] ARM: tegra: add PWM nodes to Tegra114 DT Andrew Chew
[not found] ` <1363131651-13734-1-git-send-email-achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-03-12 23:40 ` [PATCH 2/2 v4] ARM: tegra: fix the status of PWM nodes Andrew Chew
[not found] ` <1363131651-13734-2-git-send-email-achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-03-13 16:07 ` Stephen Warren
2013-03-13 16:19 ` Stephen Warren [this message]
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=5140A6FE.8070504@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=achew-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=hdoyu-DDmLM1+adcrQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.