linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
To: Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>
Cc: Frank Rowand <frowand.list@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alon Ronen <aronen@juniper.net>,
	Debjit Ghosh <dghosh@juniper.net>,
	Dhruva Diveneni <ddevineni@juniper.net>,
	Georgi Vlaev <gvlaev@juniper.net>,
	Guenter Roeck <linux@roeck-us.net>, Yu-Lin Lu <ylu@juniper.net>,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	devel@driverdev.osuosl.org
Subject: [RFC 0/2] Juniper DT based connector driver
Date: Fri,  7 Oct 2016 18:16:10 +0300	[thread overview]
Message-ID: <1475853372-21997-1-git-send-email-pantelis.antoniou@konsulko.com> (raw)

Introduce a Juniper PTX router series DT overlay based
connector driver.

This is submitted as an RFC since some OF infrastructure
patches (like changeset helpers etc) are not yet mainlined.

The Juniper series of routers comprise of both x86 and powerpc
platforms that contain similar hardware components necessitating
common support methods.

Note that this is the first submission and we expect things to be
moved around as required.

This patchset is against mainline as of today: v4.8-9431-g3477d16
and is dependent on the "Juniper prerequisites",
"Juniper infrastructure" and "Juniper PCI methods" patchsets
sent earlier.

Guenter Roeck (2):
  staging: jnx: Add Juniper connector driver
  staging: jnx-connector: add device tree binding

 .../devicetree/bindings/jnx/jnx-connector          |   59 +
 drivers/staging/jnx/Kconfig                        |   15 +
 drivers/staging/jnx/Makefile                       |    1 +
 drivers/staging/jnx/jnx-connector.c                | 2172 ++++++++++++++++++++
 4 files changed, 2247 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/jnx/jnx-connector
 create mode 100644 drivers/staging/jnx/jnx-connector.c

-- 
1.9.1

             reply	other threads:[~2016-10-07 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 15:16 Pantelis Antoniou [this message]
2016-10-07 15:16 ` [RFC 1/2] staging: jnx: Add Juniper connector driver Pantelis Antoniou
2016-10-07 16:25   ` Joe Perches
2016-10-07 18:57     ` Pantelis Antoniou
2016-10-07 15:16 ` [RFC 2/2] staging: jnx-connector: add device tree binding Pantelis Antoniou
2016-10-08 16:05   ` Rob Herring
2016-10-07 15:30 ` [RFC 0/2] Juniper DT based connector driver Greg Kroah-Hartman
2016-10-08 16:10 ` Rob Herring
2016-10-08 16:11   ` Pantelis Antoniou

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=1475853372-21997-1-git-send-email-pantelis.antoniou@konsulko.com \
    --to=pantelis.antoniou@konsulko.com \
    --cc=aronen@juniper.net \
    --cc=ddevineni@juniper.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dghosh@juniper.net \
    --cc=frowand.list@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gvlaev@juniper.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=ylu@juniper.net \
    /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).