All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Tanmay Inamdar <tinamdar@apm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Grant Likely <grant.likely@linaro.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Rob Landley <rob@landley.net>,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-pci@vger.kernel.org, patches <patches@apm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jon Masters <jcm@redhat.com>
Subject: Re: [RFC PATCH 3/3] dt-bindings: pci: xgene pcie device tree bindings
Date: Sat, 11 Jan 2014 14:06:52 +0100	[thread overview]
Message-ID: <201401111406.52935.arnd@arndb.de> (raw)
In-Reply-To: <CACoXjckkovQdB5Pk3Tn4uGkm5+HuEfWYb6E1MiUOPpuZ2b7qNA@mail.gmail.com>

On Saturday 11 January 2014, Tanmay Inamdar wrote:
> On Tue, Jan 7, 2014 at 7:35 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 07 January 2014, Tanmay Inamdar wrote:
> >> On Fri, Jan 3, 2014 at 1:49 AM, Arnd Bergmann <arnd@arndb.de> wrote:

> >> >
> >> > Better use an anonymous clock?
> >>
> >> Sorry. Can you please elaborate?
> >
> > I mean drop the "clock-names" property.
> >
> Did you mean clock-names in pcie-clock node or pcie node? I can drop
> clock-names from pcie clock node. However if I drop clock-names from
> pcie node, then clk_get call from pcie host driver would result in
> failure. Right?

I meant drop it from the pcie node, and change the clk_get call
to pass NULL instead of the name, which will get the handle for
the only clock provided. You only need clock-names if you have
more than one clock in the device node and want to identify them.

The pcie-clock node should not have a "clock-names" property at
all, unless it has a "clocks" property as well and refers to
its clock parent with it.

I already noticed in another review that the xgene clocks get this
part wrong and that should be fixed for all those clock provides,
but it's unrelated to what I was talking about here.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 3/3] dt-bindings: pci: xgene pcie device tree bindings
Date: Sat, 11 Jan 2014 14:06:52 +0100	[thread overview]
Message-ID: <201401111406.52935.arnd@arndb.de> (raw)
In-Reply-To: <CACoXjckkovQdB5Pk3Tn4uGkm5+HuEfWYb6E1MiUOPpuZ2b7qNA@mail.gmail.com>

On Saturday 11 January 2014, Tanmay Inamdar wrote:
> On Tue, Jan 7, 2014 at 7:35 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 07 January 2014, Tanmay Inamdar wrote:
> >> On Fri, Jan 3, 2014 at 1:49 AM, Arnd Bergmann <arnd@arndb.de> wrote:

> >> >
> >> > Better use an anonymous clock?
> >>
> >> Sorry. Can you please elaborate?
> >
> > I mean drop the "clock-names" property.
> >
> Did you mean clock-names in pcie-clock node or pcie node? I can drop
> clock-names from pcie clock node. However if I drop clock-names from
> pcie node, then clk_get call from pcie host driver would result in
> failure. Right?

I meant drop it from the pcie node, and change the clk_get call
to pass NULL instead of the name, which will get the handle for
the only clock provided. You only need clock-names if you have
more than one clock in the device node and want to identify them.

The pcie-clock node should not have a "clock-names" property at
all, unless it has a "clocks" property as well and refers to
its clock parent with it.

I already noticed in another review that the xgene clocks get this
part wrong and that should be fixed for all those clock provides,
but it's unrelated to what I was talking about here.

	Arnd

  reply	other threads:[~2014-01-11 13:07 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23  8:02 [RFC PATCH 0/3] APM X-Gene PCIe driver Tanmay Inamdar
2013-12-23  8:02 ` Tanmay Inamdar
2013-12-23  8:02 ` [RFC PATCH 1/3] pci: APM X-Gene PCIe controller driver Tanmay Inamdar
2013-12-23  8:02   ` Tanmay Inamdar
2014-01-02 21:08   ` Bjorn Helgaas
2014-01-02 21:08     ` Bjorn Helgaas
2014-01-03 12:07   ` Arnd Bergmann
2014-01-03 12:07     ` Arnd Bergmann
2014-01-07  2:41     ` Tanmay Inamdar
2014-01-07  2:41       ` Tanmay Inamdar
2014-01-07  9:27       ` Arnd Bergmann
2014-01-07  9:27         ` Arnd Bergmann
2014-01-10  1:20         ` Tanmay Inamdar
2014-01-10  1:20           ` Tanmay Inamdar
2014-01-06  1:47   ` Jingoo Han
2014-01-06  1:47     ` Jingoo Han
2014-01-07  2:45     ` Tanmay Inamdar
2014-01-07  2:45       ` Tanmay Inamdar
2014-01-07  3:31       ` Jingoo Han
2014-01-07  3:31         ` Jingoo Han
2013-12-23  8:02 ` [RFC PATCH 2/3] arm64: dts: APM X-Gene PCIe device tree nodes Tanmay Inamdar
2013-12-23  8:02   ` Tanmay Inamdar
2013-12-23 17:46   ` Jason Gunthorpe
2013-12-23 17:46     ` Jason Gunthorpe
2014-01-02 21:56     ` Tanmay Inamdar
2014-01-02 21:56       ` Tanmay Inamdar
2014-01-03  0:52       ` Jason Gunthorpe
2014-01-03  0:52         ` Jason Gunthorpe
2014-01-07  2:56         ` Tanmay Inamdar
2014-01-07  2:56           ` Tanmay Inamdar
2014-01-07 17:27           ` Jason Gunthorpe
2014-01-07 17:27             ` Jason Gunthorpe
2014-01-10  1:30             ` Tanmay Inamdar
2014-01-10  1:30               ` Tanmay Inamdar
2013-12-23  8:02 ` [RFC PATCH 3/3] dt-bindings: pci: xgene pcie device tree bindings Tanmay Inamdar
2013-12-23  8:02   ` Tanmay Inamdar
2014-01-03  9:49   ` Arnd Bergmann
2014-01-03  9:49     ` Arnd Bergmann
2014-01-03  9:49     ` Arnd Bergmann
2014-01-07  3:04     ` Tanmay Inamdar
2014-01-07  3:04       ` Tanmay Inamdar
2014-01-07 15:35       ` Arnd Bergmann
2014-01-07 15:35         ` Arnd Bergmann
2014-01-07 15:44         ` Arnd Bergmann
2014-01-07 15:44           ` Arnd Bergmann
2014-01-07 18:31         ` Jason Gunthorpe
2014-01-07 18:31           ` Jason Gunthorpe
2014-01-10  1:32           ` Tanmay Inamdar
2014-01-10  1:32             ` Tanmay Inamdar
2014-01-11  0:12         ` Tanmay Inamdar
2014-01-11  0:12           ` Tanmay Inamdar
2014-01-11 13:06           ` Arnd Bergmann [this message]
2014-01-11 13:06             ` Arnd Bergmann
2013-12-23  8:56 ` [RFC PATCH 0/3] APM X-Gene PCIe driver Tanmay Inamdar
2013-12-23  8:56   ` Tanmay Inamdar

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=201401111406.52935.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=jcm@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=patches@apm.com \
    --cc=rob@landley.net \
    --cc=tinamdar@apm.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 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.