From: Joshua Henderson <joshua.henderson@microchip.com>
To: Rob Herring <robh@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-mips@linux-mips.org>,
Purna Chandra Mandal <purna.mandal@microchip.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 03/14] DEVICETREE: Add PIC32 clock binding documentation
Date: Thu, 3 Dec 2015 10:37:57 -0700 [thread overview]
Message-ID: <56607DF5.1080804@microchip.com> (raw)
In-Reply-To: <20151130214344.GA13253@rob-hp-laptop>
Rob,
On 11/30/2015 02:43 PM, Rob Herring wrote:
> On Wed, Nov 25, 2015 at 10:36:55PM -0700, Joshua Henderson wrote:
>> Hi Rob,
>>
>> On 11/22/2015 2:31 PM, Rob Herring wrote:
>>> On Fri, Nov 20, 2015 at 05:17:15PM -0700, Joshua Henderson wrote:
>>>> From: Purna Chandra Mandal <purna.mandal@microchip.com>
>>>>
>>>> Document the devicetree bindings for the clock driver found on Microchip
>>>> PIC32 class devices.
>>>>
>>>> Signed-off-by: Purna Chandra Mandal <purna.mandal@microchip.com>
>>>> Signed-off-by: Joshua Henderson <joshua.henderson@microchip.com>
>>>> ---
>>>> .../devicetree/bindings/clock/microchip,pic32.txt | 263 ++++++++++++++++++++
>>>> 1 file changed, 263 insertions(+)
>>>> create mode 100644 Documentation/devicetree/bindings/clock/microchip,pic32.txt
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/clock/microchip,pic32.txt b/Documentation/devicetree/bindings/clock/microchip,pic32.txt
>>>> new file mode 100644
>>>> index 0000000..4cef72d
>>>> --- /dev/null
>>>> +++ b/Documentation/devicetree/bindings/clock/microchip,pic32.txt
>>>> @@ -0,0 +1,263 @@
>>>> +Binding for a Clock hardware block found on
>>>> +certain Microchip PIC32 MCU devices.
>>>> +
>>>> +Microchip SoC clocks-node consists of few oscillators, PLL, multiplexer
>>>> +and few divider nodes.
>>>
>>> [...]
>>>
>>>> +Required properties:
>>>> +- compatible : should have "microchip,pic32-clk".
>
> BTW, this should list out the actual compatible strings.
Ack. These are also being changed to microchip,pic32mzda-* due to other feedback.
>
>>> There is some discussion about this upstream with "critical-clocks"
>>> binding. Can you use and wait for that?
>>>
>>
>> The way this is going, we might not have to wait. :) Is there a patch available yet to try it out?
>
> Yes, googling "Lee Jones critical-clocks" should find it.
The change for this on our side is in the queue should the stars align on timing.
[...]
>
> Rob
>
Thanks,
Josh
next prev parent reply other threads:[~2015-12-03 17:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 0:17 [PATCH 00/14] Initial Microchip PIC32MZDA Support Joshua Henderson
2015-11-21 0:17 ` [PATCH 01/14] DEVICETREE: Add bindings for PIC32 interrupt controller Joshua Henderson
2015-11-21 20:47 ` Arnd Bergmann
2015-11-25 18:22 ` Joshua Henderson
2015-11-22 21:14 ` Rob Herring
2015-11-26 5:01 ` Joshua Henderson
2015-11-21 0:17 ` [PATCH 02/14] irqchip: irq-pic32-evic: Add support " Joshua Henderson
2015-11-22 11:45 ` Marc Zyngier
2015-11-25 18:22 ` Joshua Henderson
2015-11-21 0:17 ` [PATCH 03/14] DEVICETREE: Add PIC32 clock binding documentation Joshua Henderson
2015-11-21 20:49 ` Arnd Bergmann
2015-11-26 4:05 ` Joshua Henderson
2015-11-22 21:31 ` Rob Herring
2015-11-26 5:36 ` Joshua Henderson
2015-11-30 21:43 ` Rob Herring
2015-12-03 17:37 ` Joshua Henderson [this message]
2015-11-21 0:17 ` [PATCH 04/14] clk: clk-pic32: Add PIC32 clock driver Joshua Henderson
2015-11-21 0:17 ` [PATCH 05/14] DEVICETREE: Add bindings for PIC32/MZDA platforms Joshua Henderson
2015-11-22 21:35 ` Rob Herring
2015-11-21 0:17 ` [PATCH 06/14] MIPS: Add support for PIC32MZDA platform Joshua Henderson
2015-11-21 11:37 ` Alban
2015-11-22 16:29 ` Joshua Henderson
2015-11-21 0:17 ` [PATCH 07/14] DEVICETREE: Add bindings for PIC32 pin control and GPIO Joshua Henderson
2015-11-22 21:47 ` Rob Herring
2015-12-04 13:02 ` Andrei.Pistirica
2015-12-08 22:13 ` Joshua Henderson
2015-11-21 0:17 ` [PATCH 08/14] pinctrl: Add PIC32 pin control driver Joshua Henderson
2015-11-30 13:41 ` Linus Walleij
2015-12-08 22:15 ` Joshua Henderson
2015-11-21 0:17 ` [PATCH 09/14] DEVICETREE: Add bindings for PIC32 usart driver Joshua Henderson
2015-11-21 15:20 ` Sergei Shtylyov
2015-11-22 21:56 ` Rob Herring
2015-12-11 16:16 ` Joshua Henderson
2015-11-21 0:17 ` [PATCH 10/14] serial: pic32_uart: Add PIC32 uart driver Joshua Henderson
2015-11-21 0:17 ` [PATCH 11/14] mmc: sdhci-pic32: Add PIC32 SDHC host controller driver Joshua Henderson
2015-11-25 15:55 ` Ulf Hansson
2015-11-25 16:38 ` Ulf Hansson
2015-11-29 20:14 ` Paul.Thacker
2015-11-21 0:17 ` [PATCH 12/14] DEVICETREE: Add bindings for PIC32 SDHC host controller Joshua Henderson
2015-11-21 15:19 ` Sergei Shtylyov
2015-11-26 4:40 ` Joshua Henderson
2015-11-22 21:57 ` Rob Herring
2015-11-26 5:16 ` Joshua Henderson
2015-11-21 0:17 ` [PATCH 13/14] MIPS: dts: Add initial DTS for the PIC32MZDA Starter Kit Joshua Henderson
2015-11-21 0:17 ` [PATCH 14/14] MIPS: pic32mzda: Add initial PIC32MZDA Starter Kit defconfig Joshua Henderson
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=56607DF5.1080804@microchip.com \
--to=joshua.henderson@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=purna.mandal@microchip.com \
--cc=robh@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