linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL v2] of: Add of-graph helpers to loop over endpoints and find ports by id
Date: Tue, 03 Mar 2015 08:59:52 +0100	[thread overview]
Message-ID: <1425369592.3146.14.camel@pengutronix.de> (raw)

Hi Grant, Rob,

this series has been around for quite some time now, basically unchanged
except for adding fixes for new users of the API that keep appearing
over time in different subsystems.

It would be really helpful to get this merged for v4.0. Could you still
make this happen?

Alternatively, could I please get your ack to allow this tag to be
merged into the other subsystem trees for v4.1 so that patches that
depend on it don't have to wait for yet another merge window?

best regards
Philipp

The following changes since commit
c517d838eb7d07bbe9507871fab3931deccff539:

  Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)

are available in the git repository at:

  git://git.pengutronix.de/git/pza/linux.git tags/of-graph-for-4.0

for you to fetch changes up to bfe446e37c4efd8ade454911e8f80414bcbfc10d:

  of: Add of_graph_get_port_by_id function (2015-02-23 11:42:24 +0100)

----------------------------------------------------------------
of: Add of-graph helpers to loop over endpoints and find ports by id

This series converts of_graph_get_next_endpoint to decrement the
refcount of
the passed prev parameter. This allows to add a
for_each_endpoint_of_node
helper macro to loop over all endpoints in a device tree node.
The of_graph_get_port_by_id function is added to retrieve a port by its
known
port id (contained in the reg property) from the device tree.

----------------------------------------------------------------
Philipp Zabel (3):
      of: Decrement refcount of previous endpoint in
of_graph_get_next_endpoint
      of: Add for_each_endpoint_of_node helper macro
      of: Add of_graph_get_port_by_id function

 drivers/coresight/of_coresight.c                  | 13 ++-----
 drivers/gpu/drm/imx/imx-drm-core.c                | 11 +-----
 drivers/gpu/drm/rcar-du/rcar_du_kms.c             | 15 +++------
 drivers/media/platform/am437x/am437x-vpfe.c       |  1 -
 drivers/media/platform/soc_camera/soc_camera.c    |  3 +-
 drivers/of/base.c                                 | 41
++++++++++++++++++-----
 drivers/video/fbdev/omap2/dss/omapdss-boot-init.c |  7 +---
 include/linux/of_graph.h                          | 18 ++++++++++
 8 files changed, 61 insertions(+), 48 deletions(-)

             reply	other threads:[~2015-03-03  7:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  7:59 Philipp Zabel [this message]
2015-03-10 15:24 ` [GIT PULL v2] of: Add of-graph helpers to loop over endpoints and find ports by id Philipp Zabel
2015-03-10 15:42   ` Russell King - ARM Linux
2015-03-10 19:05     ` Rob Herring
2015-03-11  8:51       ` Philipp Zabel
2015-03-23 16:29         ` Heiko Stuebner
2015-03-24  9:15           ` Russell King - ARM Linux
2015-03-25  4:42             ` Rob Herring
2015-03-25  9:15               ` Philipp Zabel
2015-03-25 15:16                 ` Rob Herring

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=1425369592.3146.14.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --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 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).