linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: "Benoît Cousson" <bcousson@baylibre.com>,
	"Tony Lindgren" <tony@atomide.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Russell King" <linux@arm.linux.org.uk>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Marek Belisko <marek@goldelico.com>,
	Discussions about the Letux Kernel 
	<letux-kernel@openphoenux.org>
Subject: Re: [PATCH v2 0/5] DT Fixes for OMAP4 and OMAP5 boards
Date: Tue, 26 Apr 2016 17:00:33 +0200	[thread overview]
Message-ID: <1F57045F-FCD1-45F1-865B-E2324FACB581@goldelico.com> (raw)
In-Reply-To: <cover.1461003660.git.hns@goldelico.com>

ping.

> Am 18.04.2016 um 20:20 schrieb H. Nikolaus Schaller <hns@goldelico.com>:
> 
> This patch series adds DT nodes for:
> * twl6030 gpadc for omap4 based boards (Pandaboard ES)
> * twl6037 gpadc for omap5 based board (OMAP5EVM)
> * omap5-board-common: ckobuffer (needed for high quality twl6040 audio)
> * fix range problem with omap5 pinmux
> 
> 
> H. Nikolaus Schaller (5):
>  ARM: dts: twl6030: describe gpadc
>  ARM: dts: omap5-board-common: describe gpadc for Palmas
>  ARM: dts: omap5: fix range of permitted wakeup pinmux registers
>  ARM: dts: omap5: describe control for ckobuffer
>  ARM: dts: omap5-board-common: set up ckobuffer for twl6040
> 
> arch/arm/boot/dts/omap5-board-common.dtsi | 24 ++++++++++++++++++++++++
> arch/arm/boot/dts/omap5.dtsi              | 12 +++++++++++-
> arch/arm/boot/dts/twl6030.dtsi            |  6 ++++++
> 3 files changed, 41 insertions(+), 1 deletion(-)
> 
> -- 
> 2.7.3
> 

  parent reply	other threads:[~2016-04-26 15:00 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 18:20 [PATCH v2 0/5] DT Fixes for OMAP4 and OMAP5 boards H. Nikolaus Schaller
2016-04-18 18:20 ` [PATCH v2 1/5] ARM: dts: twl6030: describe gpadc H. Nikolaus Schaller
2016-04-26 17:26   ` Tony Lindgren
2016-04-18 18:20 ` [PATCH v2 2/5] ARM: dts: omap5-board-common: describe gpadc for Palmas H. Nikolaus Schaller
2016-04-18 18:20 ` [PATCH v2 3/5] ARM: dts: omap5: fix range of permitted wakeup pinmux registers H. Nikolaus Schaller
2016-04-26 17:23   ` Tony Lindgren
2016-04-18 18:21 ` [PATCH v2 4/5] ARM: dts: omap5: describe control for ckobuffer H. Nikolaus Schaller
2016-04-26 17:27   ` Tony Lindgren
2016-04-27  6:04     ` H. Nikolaus Schaller
2016-04-27 12:31       ` Tero Kristo
2016-04-27 13:10         ` H. Nikolaus Schaller
2016-04-27 14:10           ` Tero Kristo
2016-04-27 14:23             ` Peter Ujfalusi
2016-04-27 14:35               ` H. Nikolaus Schaller
2016-04-28  8:03                 ` Tero Kristo
2016-04-28  9:12                   ` H. Nikolaus Schaller
2016-04-28 13:23                     ` Tero Kristo
2016-05-09 11:18                       ` H. Nikolaus Schaller
2016-05-09 11:52                         ` Tero Kristo
2016-05-09 12:10                           ` Peter Ujfalusi
2016-05-09 12:32                             ` [Kernel] " Peter Ujfalusi
2016-05-09 12:46                               ` Peter Ujfalusi
2016-05-09 13:52                                 ` Peter Ujfalusi
2016-05-09 14:09                                   ` Tero Kristo
2016-05-09 15:28                                     ` Peter Ujfalusi
2016-05-09 19:44                               ` Peter Ujfalusi
2016-05-10  5:45                           ` H. Nikolaus Schaller
2016-04-18 18:21 ` [PATCH v2 5/5] ARM: dts: omap5-board-common: set up ckobuffer for twl6040 H. Nikolaus Schaller
2016-04-26 15:00 ` H. Nikolaus Schaller [this message]
2016-04-26 17:28   ` [PATCH v2 0/5] DT Fixes for OMAP4 and OMAP5 boards Tony Lindgren

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=1F57045F-FCD1-45F1-865B-E2324FACB581@goldelico.com \
    --to=hns@goldelico.com \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=ldewangan@nvidia.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marek@goldelico.com \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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).