From: Tomasz Figa <t.figa@samsung.com>
To: Jingoo Han <jg1.han@samsung.com>, 'Arnd Bergmann' <arnd@arndb.de>
Cc: 'Tomasz Figa' <tomasz.figa@gmail.com>,
'Kukjin Kim' <kgene.kim@samsung.com>,
'Bjorn Helgaas' <bhelgaas@google.com>,
linux-samsung-soc@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
'Grant Likely' <grant.likely@secretlab.ca>,
'Andrew Murray' <andrew.murray@arm.com>,
'Thomas Petazzoni' <thomas.petazzoni@free-electrons.com>,
'Thierry Reding' <thierry.reding@avionic-design.de>,
'Jason Gunthorpe' <jgunthorpe@obsidianresearch.com>,
'Surendranath Gurivireddy Balla' <suren.reddy@samsung.com>,
'Siva Reddy Kallam' <siva.kallam@samsung.com>,
'Thomas Abraham' <thomas.abraham@linaro.org>
Subject: Re: [PATCH V6 3/3] ARM: dts: Add pcie controller node for Samsung EXYNOS5440 SoC
Date: Thu, 20 Jun 2013 13:42:43 +0200 [thread overview]
Message-ID: <1490597.TZb2cDc7ca@amdc1227> (raw)
In-Reply-To: <00d801ce6da5$fa792d80$ef6b8880$@samsung.com>
On Thursday 20 of June 2013 20:04:47 Jingoo Han wrote:
> On Thursday, June 20, 2013 7:17 PM, Arnd Bergmann wrote:
> > On Thursday 20 June 2013, Jingoo Han wrote:
> > > 2. patch adding label to the pinctrl node (which is a prerequisite)
> > > and
> > >
> > > board-specific properties of PCIe nodes.
> > >
> > > [PATCH] ARM: dts: Add pcie controller node for exynos5440-ssdk5440
> > >
> > > arch/arm/boot/dts/exynos5440-ssdk5440.dts
> > > +
> > > + pcie0@290000 {
> > > + reset-gpio = <&pin_ctrl 5 0>;
> > > + };
> > > +
> > > + pcie1@2a0000 {
> > > + reset-gpio = <&pin_ctrl 22 0>;
> > > + };
> > >
> > > arch/arm/boot/dts/exynos5440.dtsi
> > > - pinctrl {
> > > + pin_ctrl: pinctrl {
> >
> > Note that you don't really have to use a label, you can also refer
> > to the pinctrl node by its full path, which is just "/pinctrl"
> > or "/pinctrl@e0000".
Sure, you can, but this is ugly.
>
> I see.
>
> But, I have a question.
> Using phandle has been the usual way to referring to a node.
> Why do you want to do it differently?
Path is translated to a phandle as well.
--
Best regards,
Tomasz
next prev parent reply other threads:[~2013-06-20 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 7:12 [PATCH V6 3/3] ARM: dts: Add pcie controller node for Samsung EXYNOS5440 SoC Jingoo Han
2013-06-20 7:48 ` Thomas Petazzoni
2013-06-20 7:57 ` Jingoo Han
2013-06-20 8:00 ` Thomas Petazzoni
2013-06-20 8:40 ` Jingoo Han
2013-06-20 8:04 ` Tomasz Figa
2013-06-20 8:25 ` Jingoo Han
2013-06-20 9:36 ` Tomasz Figa
2013-06-20 10:16 ` Arnd Bergmann
2013-06-20 11:04 ` Jingoo Han
2013-06-20 11:42 ` Tomasz Figa [this message]
2013-06-20 9:03 ` Arnd Bergmann
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=1490597.TZb2cDc7ca@amdc1227 \
--to=t.figa@samsung.com \
--cc=andrew.murray@arm.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jg1.han@samsung.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=siva.kallam@samsung.com \
--cc=suren.reddy@samsung.com \
--cc=thierry.reding@avionic-design.de \
--cc=thomas.abraham@linaro.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tomasz.figa@gmail.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;
as well as URLs for NNTP newsgroup(s).