From: Sascha Hauer <s.hauer@pengutronix.de>
To: Shawn Guo <shawn.guo@freescale.com>
Cc: Dong Aisheng-B29396 <B29396@freescale.com>,
Guo Shawn-R65073 <r65073@freescale.com>,
Linus Walleij <linus.walleij@linaro.org>,
"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [RFC PATCH v2 4/4] mmc: sdhci-esdhc-imx: using pinmux subsystem
Date: Thu, 15 Dec 2011 14:23:36 +0100 [thread overview]
Message-ID: <20111215132336.GR27267@pengutronix.de> (raw)
In-Reply-To: <20111215121752.GD10522@S2101-09.ap.freescale.net>
On Thu, Dec 15, 2011 at 08:17:54PM +0800, Shawn Guo wrote:
> On Thu, Dec 15, 2011 at 12:54:28PM +0100, Sascha Hauer wrote:
> > On Thu, Dec 15, 2011 at 07:53:05PM +0800, Shawn Guo wrote:
> > > On Thu, Dec 15, 2011 at 07:28:18PM +0800, Dong Aisheng-B29396 wrote:
> > > > > -----Original Message-----
> > > > >
> > > > My understanding is that pinmux_get will return an error if no proper pinmux
> > > > Found without dummy pinmux. That's a real error.
> > > > But with dummy pinmux, if no proper pinmux found, the pinctrl core may check
> > > > If dummy pinmux is supported, if supported, it will fakely success with returning
> > > > a dummy pinmux. Then real error is hiden.
> > > > This is due to for supporting one single image, the dummy pinmux may also be enabled
> > > > For platforms like mx6q with real pinmux.
> > > >
> > > Got your point. So your concern is about the fake success when dummy
> > > pinmux comes to play rather than 'fake error'. I'm not concerned about
> > > that case much, since we will know the failure with a simple debug/info
> > > message in the pinmux core, saying 'I do not find any available pinmux,
> > > and I'm falling into the dummy pinmux'. When you see this message
> > > imx6q, you know something goes wrong.
> >
> > So i.MX3/5 people must know that it's safe to ignore this message
> > whereas i.MX6 people must know there's something wrong Adding messages
> > saying "there might or might not be something wrong" is not good.
> > People will frequently ask on the mailing list about these messages.
> >
> Usually, people checking the serial output and asking question on list
> are developers not users. It's not too hard for developers to figure
> out such message. Or we can making it a debug message, and when some
> driver is not working, turn on debug option, you know where it goes
> wrong.
So we as developers have to figure out ourselves what can go wrong and
the users, well who cares about users?
>
> Anyway, it's not a problem to me. I have seen similar messages on my
> kernel serial output. I fail to see why pinmux can not do something
> that other subsystems are doing.
Yes, and everytime I see such a message I dig through the sourcecode
trying to find out if that's important or not. That's easy for me on
the systems I work with, but on my PC I am only a user, and honestly
on my PC I *want* to be only a user.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-12-15 13:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 16:03 [RFC PATCH v2 0/4] pinctrl: imx: add pinnmux support Dong Aisheng
2011-12-14 16:03 ` [RFC PATCH v2 1/4] dt: add of_get_child_number helper function Dong Aisheng
2011-12-14 18:04 ` Rob Herring
2011-12-14 21:41 ` Grant Likely
2011-12-15 5:49 ` Dong Aisheng-B29396
2011-12-14 16:03 ` [RFC PATCH v2 2/4] pinctrl: imx: add pinmux imx driver Dong Aisheng
2011-12-14 16:01 ` Fabio Estevam
2011-12-15 5:48 ` Dong Aisheng-B29396
2011-12-14 18:00 ` Linus Walleij
2011-12-14 21:47 ` Grant Likely
2011-12-15 7:38 ` Dong Aisheng-B29396
2011-12-15 7:35 ` Dong Aisheng-B29396
2011-12-15 8:18 ` Shawn Guo
2011-12-15 8:16 ` Dong Aisheng-B29396
2011-12-14 16:03 ` [RFC PATCH v2 3/4] ARM: imx6q: using pinmux subsystem Dong Aisheng
2011-12-14 18:02 ` Linus Walleij
2011-12-15 7:36 ` Dong Aisheng-B29396
2011-12-14 16:03 ` [RFC PATCH v2 4/4] mmc: sdhci-esdhc-imx: " Dong Aisheng
2011-12-14 17:46 ` Linus Walleij
2011-12-14 21:11 ` Sascha Hauer
2011-12-14 22:15 ` Linus Walleij
2011-12-15 7:05 ` Shawn Guo
2011-12-15 8:26 ` Linus Walleij
2011-12-15 8:59 ` Dong Aisheng-B29396
2011-12-15 9:33 ` Sascha Hauer
2011-12-15 11:21 ` Shawn Guo
2011-12-15 11:28 ` Dong Aisheng-B29396
2011-12-15 11:53 ` Shawn Guo
2011-12-15 11:54 ` Sascha Hauer
2011-12-15 12:17 ` Shawn Guo
2011-12-15 13:23 ` Sascha Hauer [this message]
2011-12-15 14:00 ` Shawn Guo
2011-12-15 16:34 ` Sascha Hauer
2011-12-15 9:03 ` Shawn Guo
2011-12-15 7:23 ` Dong Aisheng-B29396
2011-12-15 8:28 ` Linus Walleij
2011-12-15 8:55 ` Dong Aisheng-B29396
2011-12-15 9:32 ` Sascha Hauer
2011-12-15 10:40 ` Dong Aisheng-B29396
2011-12-14 17:40 ` [RFC PATCH v2 0/4] pinctrl: imx: add pinnmux support Linus Walleij
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=20111215132336.GR27267@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=B29396@freescale.com \
--cc=grant.likely@secretlab.ca \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r65073@freescale.com \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@freescale.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
Powered by JetHome