From: joshua.clayton@uniwest.com (Joshua Clayton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] i.MX6: WEIM: put node reference on early loop exit
Date: Tue, 17 Feb 2015 09:51:05 -0800 [thread overview]
Message-ID: <21911320.10lVZQzK19@jclayton-pc> (raw)
In-Reply-To: <60BA5429A0E1584BA3633194F6F993B5576E8DB6@NA-MBX-03.mgc.mentorg.com>
On Tuesday, February 17, 2015 04:28:28 PM Chaiken, Alison wrote:
> Sascha Hauer <s.hauer@pengutronix.de>
>
> >Looking at the code I get the question why the current code bails out on
> >error. Wouldn't it be better to just skip erroneous child devices and
> >issue a warning?
>
> The WEIM connects only one child at any given time. Since it is a platform
Not true. WEIM is designed to connect to up to 4 children each with its own
chipselect and io memory area.
> device, any child is cold-plugged. If the probe of the child that is
> marked 'status = "okay"' in the device-tree fails, then the WEIM itself has
> no function, which sounds more like an error than a warning state.
Is it possible to set 'status = disabled' per child if the call to
weim_timing_setup() fails, or something like that, so that
of_platform_populate() will skip it?
>
> -- Alison
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Joshua Clayton
Software Engineer
UniWest
122 S. 4th Avenue
Pasco, WA 99301
Ph: (509) 544-0720
Fx: (509) 544-0868
next prev parent reply other threads:[~2015-02-17 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 17:33 [PATCH] i.MX6: WEIM: put node reference on early loop exit alison at she-devel.com
2015-02-16 5:47 ` Sascha Hauer
2015-02-17 16:28 ` Chaiken, Alison
2015-02-17 17:51 ` Joshua Clayton [this message]
2015-02-18 8:37 ` [PATCH] i.MX6: WEIM: improve error handling upon child probe-failure alison at she-devel.com
2015-02-18 16:30 ` Joshua Clayton
2015-02-19 7:19 ` [PATCH v3 0/1] " alison at she-devel.com
2015-02-19 7:24 ` [PATCH v3 1/1] " alison at she-devel.com
2015-02-23 7:17 ` Sascha Hauer
2015-03-02 13:51 ` 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=21911320.10lVZQzK19@jclayton-pc \
--to=joshua.clayton@uniwest.com \
--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