From: edubezval@gmail.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] thermal: exynos: add optional sclk support
Date: Tue, 25 Nov 2014 01:18:06 -0400 [thread overview]
Message-ID: <20141125051803.GA29240@developer> (raw)
In-Reply-To: <CAM4voamP98hs+5Ey-qhy++HnmS0+8YLK8Fey_YCuzgBWDvzPKA@mail.gmail.com>
Abhilash,
Hi,
On Tue, Nov 25, 2014 at 08:00:50AM +0530, Abhilash Kesavan wrote:
<big cut>
> >>
> >> Lukasz, thanks for the review.
> >>
> >> Chanwoo, are you OK with this ? If so, I will post a v2 with this and
> >> the other changes you suggested.
> >
> > Is this a mandatory or a optional clk? What happens if the chip has the
> > clock, but you fail to get it in this code?
>
> This is mandatory on Exynos7 but not on the older SoCs. On Exynos7 if
> this clock is disabled then the TMU will not function.
>
It means, that only on Exynos7, outputing a dev_err is the right thing
to do. On other SoCs versions, it does not make sense at all requesting
this clock.
> >
> > Think the rule of thumb is to at least warn the user that you are
> > bailing to the defaults, because you failed to get the clock, when you
> > were supposed to.
> >
> > Besides, warning / logging (even if it is in debugging mode) the user
> > that you failed to get a clock, when the board / platform does not
> > support it, sounds at least bogus for them.
>
> So, you would rather that I go with Chanwoo's approach of adding a
> per-soc flag indicating the presence of this clock ?
>
Yes.
BR,
Eduardo Valentin
> Regards,
> Abhilash
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141125/975c460d/attachment.sig>
next prev parent reply other threads:[~2014-11-25 5:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 7:45 [PATCH] thermal: exynos: add optional sclk support Abhilash Kesavan
2014-11-23 4:51 ` Chanwoo Choi
2014-11-23 5:32 ` Abhilash Kesavan
2014-11-24 10:48 ` Lukasz Majewski
2014-11-24 16:10 ` Abhilash Kesavan
2014-11-24 17:52 ` Eduardo Valentin
2014-11-25 2:30 ` Abhilash Kesavan
2014-11-25 5:18 ` Eduardo Valentin [this message]
2014-11-25 17:23 ` Abhilash Kesavan
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=20141125051803.GA29240@developer \
--to=edubezval@gmail.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;
as well as URLs for NNTP newsgroup(s).