public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Tero Kristo <t-kristo-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH 1/5] ARM: dts: dra7-evm-common: Enable relevant IPU and DSP MMU nodes
Date: Wed, 11 Oct 2017 11:22:46 -0700	[thread overview]
Message-ID: <20171011182246.GE4394@atomide.com> (raw)
In-Reply-To: <20170821235158.4968-2-s-anna-l0cyMroinI0@public.gmane.org>

* Suman Anna <s-anna-l0cyMroinI0@public.gmane.org> [170821 16:52]:
> The MMU nodes for the remote processors IPU1, IPU2, DSP1 and
> DSP2 have all been enabled. All these nodes are relevant and
> valid for both the DRA7 EVM and DRA76 EVM boards, so are added
> in the dra7 common evm dtsi file.
> 
> Signed-off-by: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
> ---
>  arch/arm/boot/dts/dra7-evm-common.dtsi | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/dra7-evm-common.dtsi b/arch/arm/boot/dts/dra7-evm-common.dtsi
> index 343e95f9a001..01a5d4e0b044 100644
> --- a/arch/arm/boot/dts/dra7-evm-common.dtsi
> +++ b/arch/arm/boot/dts/dra7-evm-common.dtsi
> @@ -256,3 +256,27 @@
>  		status = "okay";
>  	};
>  };
> +
> +&mmu0_dsp1 {
> +	status = "okay";
> +};
> +
> +&mmu1_dsp1 {
> +	status = "okay";
> +};
> +
> +&mmu0_dsp2 {
> +	status = "okay";
> +};
> +
> +&mmu1_dsp2 {
> +	status = "okay";
> +};
> +
> +&mmu_ipu1 {
> +	status = "okay";
> +};
> +
> +&mmu_ipu2 {
> +	status = "okay";
> +};

This is getting quite silly.. The default is "okay" so just remove the useless
"disabled" from the common file and all these patches are no longer needed.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-10-11 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21 23:51 [PATCH 0/5] Enable DRA7 processor MMU DT nodes Suman Anna
     [not found] ` <20170821235158.4968-1-s-anna-l0cyMroinI0@public.gmane.org>
2017-08-21 23:51   ` [PATCH 1/5] ARM: dts: dra7-evm-common: Enable relevant IPU and DSP MMU nodes Suman Anna
     [not found]     ` <20170821235158.4968-2-s-anna-l0cyMroinI0@public.gmane.org>
2017-10-11 18:22       ` Tony Lindgren [this message]
     [not found]         ` <20171011182246.GE4394-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2017-10-11 21:51           ` Suman Anna
2017-08-21 23:51   ` [PATCH 2/5] ARM: dts: dra72-evm-common: " Suman Anna
2017-08-21 23:51   ` [PATCH 3/5] ARM: dts: beagle-x15-common: " Suman Anna
2017-08-21 23:51   ` [PATCH 4/5] ARM: dts: am572x-idk: " Suman Anna
2017-08-21 23:51   ` [PATCH 5/5] ARM: dts: am571x-idk: " Suman Anna

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=20171011182246.GE4394@atomide.com \
    --to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=s-anna-l0cyMroinI0@public.gmane.org \
    --cc=t-kristo-l0cyMroinI0@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