From: Kevin Hilman <khilman@kernel.org>
To: Rajendra Nayak <rnayak@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
sboyd@codeaurora.org, srinivas.kandagatla@linaro.org,
nrajan@codeaurora.org, lina.iyer@linaro.org
Subject: Re: [RFC 1/7] thermal: qcom: tsens: Add a skeletal tsens drivers
Date: Fri, 05 Jun 2015 16:49:08 -0700 [thread overview]
Message-ID: <7hpp59zpfv.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1429796773-7151-2-git-send-email-rnayak@codeaurora.org> (Rajendra Nayak's message of "Thu, 23 Apr 2015 19:16:07 +0530")
Hi Rajendra,
Rajendra Nayak <rnayak@codeaurora.org> writes:
> tsens is qualcomms' thermal temperature sensor device. It
> supports reading temperatures from multiple thermal sensors
> present on various QCOM SoCs.
> Calibration data is generally read from a eeprom device.
>
> Add a skeleton driver with all the necessary abstractions so
> a variety of qcom device families which support tsens can
> add driver extensions.
>
> Also add the required device tree bindings which can be used
> to descibe the tsens device in DT.
>
> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
[...]
> + ret = tmdev->ops->calibrate(tmdev);
> + if (ret < 0) {
> + dev_err(&pdev->dev, "tsens calibration failed\n");
> + return ret;
> + }
I was trying this series on linux-next with Srini's eeprom v4 and my
first attempt was to build the eeprom, qfprom and tsens drivers as
built-in. Unfortunately, the tsens driver probed before the
eeprom/qfprom driver so failed here with the "calibration failed"
message.
Building things as modules worked better, but you might want to take a
look at possibly using -EPROBE_DEFER here?
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/7] thermal: qcom: tsens: Add a skeletal tsens drivers
Date: Fri, 05 Jun 2015 16:49:08 -0700 [thread overview]
Message-ID: <7hpp59zpfv.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1429796773-7151-2-git-send-email-rnayak@codeaurora.org> (Rajendra Nayak's message of "Thu, 23 Apr 2015 19:16:07 +0530")
Hi Rajendra,
Rajendra Nayak <rnayak@codeaurora.org> writes:
> tsens is qualcomms' thermal temperature sensor device. It
> supports reading temperatures from multiple thermal sensors
> present on various QCOM SoCs.
> Calibration data is generally read from a eeprom device.
>
> Add a skeleton driver with all the necessary abstractions so
> a variety of qcom device families which support tsens can
> add driver extensions.
>
> Also add the required device tree bindings which can be used
> to descibe the tsens device in DT.
>
> Signed-off-by: Rajendra Nayak <rnayak@codeaurora.org>
[...]
> + ret = tmdev->ops->calibrate(tmdev);
> + if (ret < 0) {
> + dev_err(&pdev->dev, "tsens calibration failed\n");
> + return ret;
> + }
I was trying this series on linux-next with Srini's eeprom v4 and my
first attempt was to build the eeprom, qfprom and tsens drivers as
built-in. Unfortunately, the tsens driver probed before the
eeprom/qfprom driver so failed here with the "calibration failed"
message.
Building things as modules worked better, but you might want to take a
look at possibly using -EPROBE_DEFER here?
Kevin
next prev parent reply other threads:[~2015-06-05 23:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 13:46 [RFC 0/7] qcom: Add support for tsens driver Rajendra Nayak
2015-04-23 13:46 ` Rajendra Nayak
2015-04-23 13:46 ` [RFC 1/7] thermal: qcom: tsens: Add a skeletal tsens drivers Rajendra Nayak
2015-04-23 13:46 ` Rajendra Nayak
2015-06-05 23:49 ` Kevin Hilman [this message]
2015-06-05 23:49 ` Kevin Hilman
2015-06-08 4:02 ` Rajendra Nayak
2015-06-08 4:02 ` Rajendra Nayak
2015-06-12 16:03 ` Lina Iyer
2015-06-12 16:03 ` Lina Iyer
2015-06-15 3:01 ` Rajendra Nayak
2015-06-15 3:01 ` Rajendra Nayak
2015-04-23 13:46 ` [RFC 2/7] thermal: qcom: tsens-8916: Add support for 8916 family of SoCs Rajendra Nayak
2015-04-23 13:46 ` Rajendra Nayak
2015-04-23 13:46 ` [RFC 3/7] thermal: qcom: tsens-8974: Add support for 8974 " Rajendra Nayak
2015-04-23 13:46 ` Rajendra Nayak
2015-04-23 13:46 ` [RFC 4/7] thermal: qcom: tsens-8960: Add support for 8960 " Rajendra Nayak
2015-04-23 13:46 ` Rajendra Nayak
2015-04-23 13:46 ` [RFC 5/7] arm: dts: msm8974: Add thermal zones, tsens and eeprom nodes Rajendra Nayak
2015-04-23 13:46 ` Rajendra Nayak
2015-04-23 16:51 ` Lina Iyer
2015-04-23 16:51 ` Lina Iyer
2015-04-24 2:49 ` Rajendra Nayak
2015-04-24 2:49 ` Rajendra Nayak
2015-04-23 13:46 ` [RFC 6/7] clk: qcom: gcc-msm8960: add child devices support Rajendra Nayak
2015-04-23 13:46 ` Rajendra Nayak
2015-04-23 13:46 ` [RFC 7/7] arm: dts: apq8064: Add thermal zones, tsens and eeprom nodes Rajendra Nayak
2015-04-23 13:46 ` Rajendra Nayak
2015-04-23 16:52 ` [RFC 0/7] qcom: Add support for tsens driver Lina Iyer
2015-04-23 16:52 ` Lina Iyer
2015-06-06 0:25 ` Kevin Hilman
2015-06-06 0:25 ` Kevin Hilman
2015-06-08 4:29 ` Rajendra Nayak
2015-06-08 4:29 ` Rajendra Nayak
2015-06-08 16:05 ` Kevin Hilman
2015-06-08 16:05 ` Kevin Hilman
2015-06-09 5:15 ` Rajendra Nayak
2015-06-09 5:15 ` Rajendra Nayak
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=7hpp59zpfv.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=lina.iyer@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nrajan@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=sboyd@codeaurora.org \
--cc=srinivas.kandagatla@linaro.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.