devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vignesh R <vigneshr@ti.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Santosh Shilimkar <ssantosh@kernel.org>
Cc: Vignesh R <vigneshr@ti.com>,
	linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] K2G: Add support for PWM ECAP
Date: Mon, 7 Aug 2017 17:19:39 +0530	[thread overview]
Message-ID: <20170807114943.22612-1-vigneshr@ti.com> (raw)

This series adds support for TI ECAP PWM IP present in 66AK2G SoC.
Based on linux-next.

Vignesh R (4):
  pwm: pwm-tiecap: Add TI 66AK2G SoC specific compatible
  ARM: dts: keystone-k2g: Add ECAP PWM DT nodes
  ARM: dts: keystone-k2g-evm: Enable PWM ECAP0
  ARM: configs: keystone: Enable TIECAP PWM driver

 Documentation/devicetree/bindings/pwm/pwm-tiecap.txt |  1 +
 arch/arm/boot/dts/keystone-k2g-evm.dts               | 12 ++++++++++++
 arch/arm/boot/dts/keystone-k2g.dtsi                  | 20 ++++++++++++++++++++
 arch/arm/configs/keystone_defconfig                  |  2 ++
 4 files changed, 35 insertions(+)

-- 
2.13.3

             reply	other threads:[~2017-08-07 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 11:49 Vignesh R [this message]
2017-08-07 11:49 ` [PATCH 1/4] pwm: pwm-tiecap: Add TI 66AK2G SoC specific compatible Vignesh R
     [not found]   ` <20170807114943.22612-2-vigneshr-l0cyMroinI0@public.gmane.org>
2017-08-10 20:52     ` Rob Herring
2017-08-21  6:12     ` Thierry Reding
2017-08-07 11:49 ` [PATCH 2/4] ARM: dts: keystone-k2g: Add ECAP PWM DT nodes Vignesh R
2017-08-07 11:49 ` [PATCH 3/4] ARM: dts: keystone-k2g-evm: Enable PWM ECAP0 Vignesh R
2017-08-07 11:49 ` [PATCH 4/4] ARM: configs: keystone: Enable TIECAP PWM driver Vignesh R

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=20170807114943.22612-1-vigneshr@ti.com \
    --to=vigneshr@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=ssantosh@kernel.org \
    --cc=thierry.reding@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).