From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Andy Shevchenko
<andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Cc: Christian Ruppert
<christian.ruppert-Yycd8EPnGM5BDgjK7y7TUQ@public.gmane.org>,
Alexey Brodkin
<Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>,
"christian.ruppert-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org"
<christian.ruppert-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org"
<mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
"Vineet.Gupta1-HKixBCOQz3hWk0Htik3J/w@public.gmane.org"
<Vineet.Gupta1-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] i2c: designware: Suppress error message if platform_get_irq() returns -EPROBE_DEFER
Date: Tue, 3 Mar 2015 20:11:53 +0100 [thread overview]
Message-ID: <20150303191153.GA7862@katana> (raw)
In-Reply-To: <1425409412.14897.157.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
> > > I am all for centralizing printouts. I recommended this at my ELCE
> > > talk last year, too. However, you need to keep in mind that irqs
> > > are sometimes optional and you don't want error messages for those
> > > irqs. IMO worthwhile, but not a low hanging fruit...
> >
> > There is a lot of truth in that. Thus the initial dev_dbg() suggestion
> > to go half way. I still think that Andy's proposal (or a variation
> > thereof to catch the optional irqs case) should be the ultimate goal
> > but I agree that this is more than a quick patch and that it's
> > probably way out of scope here.
>
> Yes, I was thinking even about some wrapper on top of platform_get_irq()
> since it seems there are no messaging done inside platform.c, though
> devm_* functions usually have it.
When I had a look a few months ago, the situation with devm_* was messy.
Some rightfully printed errors, some rightfully didn't, some vice versa,
some the other way around, and some did something else...
For driver authors, it is hard to see/remember which devm function does
it and which doesn't. IMO a good cleanup will get rid of this mess. I
started sketching something but especially clks and irqs are basically
everywhere and so it easily grew out of the fun-time project scale,
sadly.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Christian Ruppert <christian.ruppert@alitech.com>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"christian.ruppert@abilis.com" <christian.ruppert@abilis.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>
Subject: Re: [PATCH] i2c: designware: Suppress error message if platform_get_irq() returns -EPROBE_DEFER
Date: Tue, 3 Mar 2015 20:11:53 +0100 [thread overview]
Message-ID: <20150303191153.GA7862@katana> (raw)
In-Reply-To: <1425409412.14897.157.camel@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
> > > I am all for centralizing printouts. I recommended this at my ELCE
> > > talk last year, too. However, you need to keep in mind that irqs
> > > are sometimes optional and you don't want error messages for those
> > > irqs. IMO worthwhile, but not a low hanging fruit...
> >
> > There is a lot of truth in that. Thus the initial dev_dbg() suggestion
> > to go half way. I still think that Andy's proposal (or a variation
> > thereof to catch the optional irqs case) should be the ultimate goal
> > but I agree that this is more than a quick patch and that it's
> > probably way out of scope here.
>
> Yes, I was thinking even about some wrapper on top of platform_get_irq()
> since it seems there are no messaging done inside platform.c, though
> devm_* functions usually have it.
When I had a look a few months ago, the situation with devm_* was messy.
Some rightfully printed errors, some rightfully didn't, some vice versa,
some the other way around, and some did something else...
For driver authors, it is hard to see/remember which devm function does
it and which doesn't. IMO a good cleanup will get rid of this mess. I
started sketching something but especially clks and irqs are basically
everywhere and so it easily grew out of the fun-time project scale,
sadly.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-03 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 15:27 [PATCH] i2c: designware: Suppress error message if platform_get_irq() returns -EPROBE_DEFER Alexey Brodkin
2015-03-03 16:28 ` Christian Ruppert
[not found] ` <54F5E120.3090705-Yycd8EPnGM5BDgjK7y7TUQ@public.gmane.org>
2015-03-03 16:37 ` Alexey Brodkin
2015-03-03 16:37 ` Alexey Brodkin
[not found] ` <1425400650.17965.53.camel-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2015-03-03 16:50 ` christian.ruppert-Yycd8EPnGM5BDgjK7y7TUQ
2015-03-03 16:50 ` christian.ruppert
2015-03-03 17:21 ` Wolfram Sang
2015-03-03 17:46 ` Christian Ruppert
2015-03-03 19:03 ` Andy Shevchenko
[not found] ` <1425409412.14897.157.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2015-03-03 19:11 ` Wolfram Sang [this message]
2015-03-03 19:11 ` Wolfram Sang
2015-03-03 19:34 ` Andy Shevchenko
2015-03-03 19:34 ` Andy Shevchenko
2015-03-07 0:24 ` Wolfram Sang
2015-03-07 0:24 ` Wolfram Sang
2015-03-09 8:29 ` Alexey Brodkin
2015-03-09 8:29 ` Alexey Brodkin
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=20150303191153.GA7862@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=Alexey.Brodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
--cc=Vineet.Gupta1-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
--cc=andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=christian.ruppert-Yycd8EPnGM5BDgjK7y7TUQ@public.gmane.org \
--cc=christian.ruppert-ux6zf3SgZrrQT0dZR+AlfA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.