From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: dts: da850: Add new ECAP and EPWM bindings
Date: Mon, 8 Aug 2016 16:21:13 +0530 [thread overview]
Message-ID: <57A86421.6030804@ti.com> (raw)
In-Reply-To: <1468264306-3806-1-git-send-email-fcooper@ti.com>
On Tuesday 12 July 2016 12:41 AM, Franklin S Cooper Jr wrote:
> From: "Cooper Jr., Franklin" <fcooper@ti.com>
>
> For some devices, the PWMSS is a parent of eCAP and ePWM and provided the
"and provides .."
> functional clocks for those submodules. The ti,am33xx-ecap and
> ti,am33xx-ehrpwm were based on this parent child relationship where the
"ti,am33xx-ehrpwm bindings were .."
> functional clock would be grabbed from the module's parent.
>
> However, DA850 doesn't have a PWMSS and the eCAP and ePWM provides their
> functional clock themselves. Therefore, prefer the new binding that doesn't
> assume this parent child relationship.
>
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> Acked-by: Rob Herring <robh@kernel.org>
Queuing this for v4.9 with above minor commit message fixes made locally.
Regards,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: Sekhar Nori <nsekhar@ti.com>
To: Franklin S Cooper Jr <fcooper@ti.com>,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: da850: Add new ECAP and EPWM bindings
Date: Mon, 8 Aug 2016 16:21:13 +0530 [thread overview]
Message-ID: <57A86421.6030804@ti.com> (raw)
In-Reply-To: <1468264306-3806-1-git-send-email-fcooper@ti.com>
On Tuesday 12 July 2016 12:41 AM, Franklin S Cooper Jr wrote:
> From: "Cooper Jr., Franklin" <fcooper@ti.com>
>
> For some devices, the PWMSS is a parent of eCAP and ePWM and provided the
"and provides .."
> functional clocks for those submodules. The ti,am33xx-ecap and
> ti,am33xx-ehrpwm were based on this parent child relationship where the
"ti,am33xx-ehrpwm bindings were .."
> functional clock would be grabbed from the module's parent.
>
> However, DA850 doesn't have a PWMSS and the eCAP and ePWM provides their
> functional clock themselves. Therefore, prefer the new binding that doesn't
> assume this parent child relationship.
>
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> Acked-by: Rob Herring <robh@kernel.org>
Queuing this for v4.9 with above minor commit message fixes made locally.
Regards,
Sekhar
WARNING: multiple messages have this Message-ID (diff)
From: Sekhar Nori <nsekhar@ti.com>
To: Franklin S Cooper Jr <fcooper@ti.com>, <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: dts: da850: Add new ECAP and EPWM bindings
Date: Mon, 8 Aug 2016 16:21:13 +0530 [thread overview]
Message-ID: <57A86421.6030804@ti.com> (raw)
In-Reply-To: <1468264306-3806-1-git-send-email-fcooper@ti.com>
On Tuesday 12 July 2016 12:41 AM, Franklin S Cooper Jr wrote:
> From: "Cooper Jr., Franklin" <fcooper@ti.com>
>
> For some devices, the PWMSS is a parent of eCAP and ePWM and provided the
"and provides .."
> functional clocks for those submodules. The ti,am33xx-ecap and
> ti,am33xx-ehrpwm were based on this parent child relationship where the
"ti,am33xx-ehrpwm bindings were .."
> functional clock would be grabbed from the module's parent.
>
> However, DA850 doesn't have a PWMSS and the eCAP and ePWM provides their
> functional clock themselves. Therefore, prefer the new binding that doesn't
> assume this parent child relationship.
>
> Signed-off-by: Franklin S Cooper Jr <fcooper@ti.com>
> Acked-by: Rob Herring <robh@kernel.org>
Queuing this for v4.9 with above minor commit message fixes made locally.
Regards,
Sekhar
next prev parent reply other threads:[~2016-08-08 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 19:11 [PATCH v2] ARM: dts: da850: Add new ECAP and EPWM bindings Franklin S Cooper Jr
2016-07-11 19:11 ` Franklin S Cooper Jr
2016-08-08 10:51 ` Sekhar Nori [this message]
2016-08-08 10:51 ` Sekhar Nori
2016-08-08 10:51 ` Sekhar Nori
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=57A86421.6030804@ti.com \
--to=nsekhar@ti.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 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.