linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: i.MX: Make more robust against devicetree errors
Date: Fri,  9 Aug 2013 14:20:49 +0200	[thread overview]
Message-ID: <1376050854-3303-1-git-send-email-s.hauer@pengutronix.de> (raw)

When there is something wrong with pinctrl in the i.MX devicetree
files this usually means the i.MX pinctrl driver bails out completely.
In this case even the console is nonfunctional since it can't get
the pins. Enabling earlyprintk isn't very helpful since the driver
only prints that something is wrong, but not what is wrong.

With this series the i.MX pinctrl driver continues on errors so that
the system stays working and only the erroneous pinctrl groups fail
later. Also the error messages are supplemented with the offending
devicetree node to give a clue what went wrong.

Sascha

----------------------------------------------------------------
Sascha Hauer (5):
      pinctrl: imx: make error messages more informative
      pinctrl: imx: Catch no fsl,pins property
      pinctrl: imx: do not fail when parsing a group fails
      pinctrl: imx: do not fail when parsing a function fails
      pinctrl: imx: Use struct type for pins

 drivers/pinctrl/pinctrl-imx.c | 95 ++++++++++++++++++++-----------------------
 drivers/pinctrl/pinctrl-imx.h | 36 +++++++++-------
 2 files changed, 64 insertions(+), 67 deletions(-)

             reply	other threads:[~2013-08-09 12:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 12:20 Sascha Hauer [this message]
2013-08-09 12:20 ` [PATCH 1/5] pinctrl: imx: make error messages more informative Sascha Hauer
2013-08-14 20:33   ` Linus Walleij
2013-08-09 12:20 ` [PATCH 2/5] pinctrl: imx: Catch no fsl,pins property Sascha Hauer
2013-08-14 20:34   ` Linus Walleij
2013-08-09 12:20 ` [PATCH 3/5] pinctrl: imx: do not fail when parsing a group fails Sascha Hauer
2013-08-14 20:35   ` Linus Walleij
2013-08-09 12:20 ` [PATCH 4/5] pinctrl: imx: do not fail when parsing a function fails Sascha Hauer
2013-08-14 20:37   ` Linus Walleij
2013-08-15  5:04     ` Sascha Hauer
2013-08-15 20:10       ` Linus Walleij
2013-08-09 12:20 ` [PATCH 5/5] pinctrl: imx: Use struct type for pins Sascha Hauer
2013-08-14 20:41   ` Linus Walleij
2013-08-15  5:08     ` Sascha Hauer
2013-08-15 20:11       ` Linus Walleij
2013-08-16  6:37         ` Sascha Hauer
2013-08-16 12:43           ` Linus Walleij
2013-08-12  7:49 ` [PATCH] pinctrl: i.MX: Make more robust against devicetree errors Shawn Guo

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=1376050854-3303-1-git-send-email-s.hauer@pengutronix.de \
    --to=s.hauer@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).