From: Wolfram Sang <wsa@the-dreams.de>
To: linux-sh@vger.kernel.org
Subject: Re: [RFC v4 1/4] watchdog: renesas-rwdt: add driver
Date: Thu, 17 Mar 2016 10:09:49 +0000 [thread overview]
Message-ID: <20160317100949.GC1402@katana> (raw)
In-Reply-To: <1452287553-18895-2-git-send-email-wsa@the-dreams.de>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
> > What about "renesas,rcar-gen2-rwdt" since Gen2 and Gen3 are identical?
>
> Are they? :-) Yes, at the datasheet level, FWIW...
OK.
> > But why "r8a7795-rwdt" with SoC first? Looking at the r8a7795.dtsi,
> > "<ip_core>-<soc_type>" seems to be more dominant than
> > "<soc_type>-<ip_core>"? Ah, confusing again...
>
> For new bindings, we follow practices set by the rest of the DT crowd.
OK.
> >> > + if (!rate)
> >> > + return -ENOENT;
> >>
> >> -EINVAL?
> >
> > Too generic.
>
> A clock with a zero rate doesn't mean that the clock doesn't exist.
Using different ERRNOs, you see immediately which error path was taken
and what you need to fix (without adding printouts to the driver because
you don't know which -EINVAL triggered). I consider this more helpful
than being pedantic on the error namings (since they are only reported
by the driver core and not exposed to userspace).
So, I don't wanna change this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-17 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 21:12 [RFC v4 1/4] watchdog: renesas-rwdt: add driver Wolfram Sang
2016-01-14 17:30 ` Geert Uytterhoeven
2016-03-17 9:34 ` Wolfram Sang
2016-03-17 9:48 ` Geert Uytterhoeven
2016-03-17 10:09 ` Wolfram Sang [this message]
2016-03-18 0:18 ` Simon Horman
2016-03-18 8:27 ` Wolfram Sang
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=20160317100949.GC1402@katana \
--to=wsa@the-dreams.de \
--cc=linux-sh@vger.kernel.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).