linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv9 5/9] clk: mvebu: create parent-child relation for PCIe clocks on Armada 370
Date: Thu, 16 May 2013 09:44:17 +0200	[thread overview]
Message-ID: <20130516094417.24b1ca0d@skate> (raw)
In-Reply-To: <20130515214154.12127.73539@quantum>

Dear Mike Turquette,

On Wed, 15 May 2013 14:41:54 -0700, Mike Turquette wrote:
> Quoting Thomas Petazzoni (2013-05-15 06:25:19)
> > The Armada 370 has two gatable clocks for each PCIe interface, and we
> > want both of them to be enabled. We therefore make one of the two
> > clocks a child of the other, as we did for the sataX and sataXlnk
> > clocks on Armada XP.
> 
> Ack for patches #5 and #6.  Do you want me to take them?

I don't know, I guess with your Ack, it would be easier to carry them
through the Marvell maintainers and then the arm-soc tree, so that we
can test arm-soc and have all the pieces needed in here.

That said, Sebastian Hesselbarth has submitted a big rework of the
mvebu clock drivers, which would conflict with this patch, and
Sebastian's rework would most likely go through your tree. If that's
the case, I guess it would be better to let you take #5 and #6 in this
patch series.

That's something to be discussed with the Marvell maintainers (Jason
Cooper, Andrew Lunn, Gregory Clement).

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-05-16  7:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 13:25 [PATCHv9 0/9] PCIe support for the Armada 370 and Armada XP SoCs Thomas Petazzoni
2013-05-15 13:25 ` [PATCHv9 1/9] arm: mvebu: fix the 'ranges' property to handle PCIe Thomas Petazzoni
2013-05-15 13:25 ` [PATCHv9 2/9] of/pci: Provide support for parsing PCI DT ranges property Thomas Petazzoni
2013-05-15 13:25 ` [PATCHv9 3/9] of/pci: Add of_pci_get_devfn() function Thomas Petazzoni
2013-05-15 13:25 ` [PATCHv9 4/9] of/pci: Add of_pci_parse_bus_range() function Thomas Petazzoni
2013-05-15 13:25 ` [PATCHv9 5/9] clk: mvebu: create parent-child relation for PCIe clocks on Armada 370 Thomas Petazzoni
2013-05-15 21:41   ` Mike Turquette
2013-05-16  7:44     ` Thomas Petazzoni [this message]
2013-05-16  8:26       ` Sebastian Hesselbarth
2013-05-16 15:06         ` Jason Cooper
2013-05-17  7:08           ` Mike Turquette
2013-05-17 12:55             ` Jason Cooper
2013-05-15 13:25 ` [PATCHv9 6/9] clk: mvebu: add more PCIe clocks for Armada XP Thomas Petazzoni
2013-05-15 13:25 ` [PATCHv9 7/9] pci: PCIe driver for Marvell Armada 370/XP systems Thomas Petazzoni
2013-05-16  9:33   ` Ezequiel Garcia
2013-05-16 15:40     ` Jason Cooper
2013-05-16 15:49       ` Thomas Petazzoni
2013-05-16 15:56         ` Jason Cooper
2013-05-16 16:08           ` Thomas Petazzoni
2013-05-16 16:12             ` Jason Cooper
2013-05-16 20:18               ` Jason Cooper
2013-05-15 13:25 ` [PATCHv9 8/9] arm: mvebu: PCIe support is now available on mvebu Thomas Petazzoni
2013-05-15 13:25 ` [PATCHv9 9/9] arm: mvebu: update defconfig with PCI and USB support Thomas Petazzoni

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=20130516094417.24b1ca0d@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.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).