devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Russell King <linux@armlinux.org.uk>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 6/7] ARM: dts: imx6ul: add support for TXUL modules on TXUL-Mainboard
Date: Tue, 17 Oct 2017 11:50:14 +0200	[thread overview]
Message-ID: <20171017115014.5632584d@karo-electronics.de> (raw)
In-Reply-To: <CAOMZO5BbRwnggKPUo=evT=nHxo9k6v3d-zNLaiOPWabDNdLgpA@mail.gmail.com>

Hi,

On Mon, 16 Oct 2017 18:33:17 -0200 Fabio Estevam wrote:
> Hi Lothar,
> 
> On Fri, Oct 13, 2017 at 7:43 AM, Lothar Waßmann <LW@karo-electronics.de> wrote:
> 
> > +/ {
> > +       aliases {
> > +               lcdif_24bit_pins_a = &pinctrl_disp0_3;
> > +               mmc0 = &usdhc1;
> 
> Is this mmc0 alias really needed here?
> 
> I see it inside imx6ul.dtsi, but even inside imx6ul.dtsi: does it make
> sense to have mmc alias?
> 
It is not used by Linux, but it's a convenient way to address the mmc
devices with the U-Boot 'fdt' command.
E.g.:
fdt set mmc0 status disabled
rather than:
fdt set /soc/aips-bus@02100000/usdhc@02190000 status disabled


Lothar Waßmann

  reply	other threads:[~2017-10-17  9:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13 10:42 [PATCH 0/7] ARM: dts: imx6ul: Update dts files for the Ka-Ro TXUL module series Lothar Waßmann
     [not found] ` <1507891383-15452-1-git-send-email-LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
2017-10-13 10:42   ` [PATCH 1/7] ARM: dts: imx6ul-txul: enable I2C bus recovery Lothar Waßmann
2017-10-13 10:42   ` [PATCH 2/7] ARM: dts: imx6ul-txul: specify ethernet phy reset post-delay Lothar Waßmann
2017-10-13 10:42 ` [PATCH 3/7] ARM: dts: imx6ul: add support for TXUL-8013 Lothar Waßmann
2017-10-13 10:43 ` [PATCH 4/7] ARM: dts: imx6ul-txul: use panel-simple driver for LCD Lothar Waßmann
     [not found]   ` <1507891383-15452-5-git-send-email-LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
2017-10-14 15:38     ` Shawn Guo
2017-10-13 10:43 ` [PATCH 5/7] ARM: dts: imx6ul-txul: use interrupts-extended property Lothar Waßmann
2017-10-13 10:43 ` [PATCH 6/7] ARM: dts: imx6ul: add support for TXUL modules on TXUL-Mainboard Lothar Waßmann
     [not found]   ` <1507891383-15452-7-git-send-email-LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
2017-10-16 20:33     ` Fabio Estevam
2017-10-17  9:50       ` Lothar Waßmann [this message]
2017-10-13 10:43 ` [PATCH 7/7] ARM: dts: imx6ul-txul: add support for TXUL modules on MB7 baseboard Lothar Waßmann

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=20171017115014.5632584d@karo-electronics.de \
    --to=lw@karo-electronics.de \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.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).