From: Eduardo Valentin <eduardo.valentin@ti.com>
To: Lukasz Majewski <l.majewski@samsung.com>
Cc: Eduardo Valentin <eduardo.valentin@ti.com>,
Zhang Rui <rui.zhang@intel.com>,
kgene.kim@samsung.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM list <linux-pm@vger.kernel.org>,
Jonghwa Lee <jonghwa3.lee@samsung.com>,
Lukasz Majewski <l.majewski@majess.pl>,
linux-kernel <linux-kernel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Tomasz Figa <t.figa@samsung.com>,
Myungjoo Ham <myungjoo.ham@samsung.com>,
devicetree@vger.kernel.org,
Amit Daniel Kachhap <amit.daniel@samsung.com>,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 3/5] thermal: exynos: Provide initial setting for TMU's test MUX address at Exynos4412
Date: Mon, 14 Oct 2013 15:20:24 -0400 [thread overview]
Message-ID: <525C43F8.4010001@ti.com> (raw)
In-Reply-To: <20131014170032.7ed18cad@amdc308.digital.local>
[-- Attachment #1: Type: text/plain, Size: 6561 bytes --]
On 14-10-2013 11:00, Lukasz Majewski wrote:
> Hi Eduardo,
>
>> On 09-10-2013 02:29, Lukasz Majewski wrote:
>>> The commit d0a0ce3e77c795258d47f9163e92d5031d0c5221 ("thermal:
>>> exynos: Add missing definations and code cleanup") has removed
>>> setting of test MUX address value at TMU configuration setting.
>>>
>>> This field is not present on Exynos4210 and Exynos5 SoCs. However
>>> on Exynos4412 SoC it is required to set this field after reset
>>> because without it TMU shows maximal available temperature, which
>>> causes immediate platform shutdown.
>>>
>>> Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
>>> Reviewed-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
>>> Reviewed-by: Tomasz Figa <t.figa@samsung.com>
>>>
>>> ---
>>> Changes for v2:
>>> - Define test_mux and test_mux_addr_shift to not use direct
>>> register access
>>> - Remove pdata->type == SOC_ARCH_EXYNOS4412 check at
>>> exynos_tmu_control() and use only generic code
>>>
>>> drivers/thermal/samsung/exynos_tmu.c | 3 +++
>>> drivers/thermal/samsung/exynos_tmu.h | 4 ++++
>>> drivers/thermal/samsung/exynos_tmu_data.c | 2 ++
>>> drivers/thermal/samsung/exynos_tmu_data.h | 4 ++++
>>> 4 files changed, 13 insertions(+)
>>>
>>> diff --git a/drivers/thermal/samsung/exynos_tmu.c
>>> b/drivers/thermal/samsung/exynos_tmu.c index 1312b34..32f38b9 100644
>>> --- a/drivers/thermal/samsung/exynos_tmu.c
>>> +++ b/drivers/thermal/samsung/exynos_tmu.c
>>> @@ -317,6 +317,9 @@ static void exynos_tmu_control(struct
>>> platform_device *pdev, bool on)
>>> con = readl(data->base + reg->tmu_ctrl);
>>>
>>> + if (pdata->test_mux)
>>
>>
>> test_mux field is in fact an address, correct? Can 0 be a valid
>> address?
>
> No it isn't an address. It is the value which shall be written to
> test_mux field of TMU_CONTROL register.
>
>>
>> Why not using the feature flags to test for capabilities,
>
> It is easier to assign value to test_mux tmu_data struct, than write
> separate set of features for Exynos4412 and Exynos5250, which share the
> code.
>
It is harder to write, yes, but things that are easy to write are
usually harder to read. Besides, my concern is if 0x0 is a valid value
to be written. And if yes, then makes the patch you sent might be
incomplete.
> Also .features seems to define SoC independent features of TMU IP (like
> TMU_SUPPORT_EMULATION).
>
> The TEST_MUX setting is platform dependent (only Exynos4412 uses it),
> so this is the rationale to define it at tmu platform data.
>
Is test mux something pinctrl should be handling?
>> features and
>> required configurations instead of assuming obscure domain and address
>> ranges?
>
> TMU_MUX only uses
>
> (test_mux << test_mux_addr_shift) at tmu_ctrl register.
>
>
>>
>>
>>> + con |= (pdata->test_mux <<
>>> reg->test_mux_addr_shift); +
>>> if (pdata->reference_voltage) {
>>> con &= ~(reg->buf_vref_sel_mask <<
>>> reg->buf_vref_sel_shift); con |= pdata->reference_voltage <<
>>> reg->buf_vref_sel_shift; diff --git
>>> a/drivers/thermal/samsung/exynos_tmu.h
>>> b/drivers/thermal/samsung/exynos_tmu.h index b42ece4..3fb6554
>>> 100644 --- a/drivers/thermal/samsung/exynos_tmu.h +++
>>> b/drivers/thermal/samsung/exynos_tmu.h @@ -85,6 +85,7 @@ enum
>>> soc_type {
>>> * @triminfo_reload_shift: shift of triminfo reload enable bit in
>>> triminfo_ctrl reg.
>>> * @tmu_ctrl: TMU main controller register.
>>> + * @test_mux_addr_shift: shift bits of test mux address.
>>> * @buf_vref_sel_shift: shift bits of reference voltage in
>>> tmu_ctrl register.
>>> * @buf_vref_sel_mask: mask bits of reference voltage in tmu_ctrl
>>> register.
>>> * @therm_trip_mode_shift: shift bits of tripping mode in tmu_ctrl
>>> register. @@ -151,6 +152,7 @@ struct exynos_tmu_registers {
>>> u32 triminfo_reload_shift;
>>>
>>> u32 tmu_ctrl;
>>> + u32 test_mux_addr_shift;
>>> u32 buf_vref_sel_shift;
>>> u32 buf_vref_sel_mask;
>>> u32 therm_trip_mode_shift;
>>> @@ -258,6 +260,7 @@ struct exynos_tmu_registers {
>>> * @first_point_trim: temp value of the first point trimming
>>> * @second_point_trim: temp value of the second point trimming
>>> * @default_temp_offset: default temperature offset in case of no
>>> trimming
>>> + * @test_mux; information if SoC supports test MUX
>>> * @cal_type: calibration type for temperature
>>> * @cal_mode: calibration mode for temperature
>>> * @freq_clip_table: Table representing frequency reduction
>>> percentage. @@ -287,6 +290,7 @@ struct exynos_tmu_platform_data {
>>> u8 first_point_trim;
>>> u8 second_point_trim;
>>> u8 default_temp_offset;
>>> + u8 test_mux;
>>>
>>> enum calibration_type cal_type;
>>> enum calibration_mode cal_mode;
>>> diff --git a/drivers/thermal/samsung/exynos_tmu_data.c
>>> b/drivers/thermal/samsung/exynos_tmu_data.c index d8de5c1..073c292
>>> 100644 --- a/drivers/thermal/samsung/exynos_tmu_data.c
>>> +++ b/drivers/thermal/samsung/exynos_tmu_data.c
>>> @@ -98,6 +98,7 @@ static const struct exynos_tmu_registers
>>> exynos4412_tmu_registers = { .triminfo_ctrl =
>>> EXYNOS_TMU_TRIMINFO_CON, .triminfo_reload_shift =
>>> EXYNOS_TRIMINFO_RELOAD_SHIFT, .tmu_ctrl = EXYNOS_TMU_REG_CONTROL,
>>> + .test_mux_addr_shift = EXYNOS4412_MUX_ADDR_SHIFT,
>>> .buf_vref_sel_shift = EXYNOS_TMU_REF_VOLTAGE_SHIFT,
>>> .buf_vref_sel_mask = EXYNOS_TMU_REF_VOLTAGE_MASK,
>>> .therm_trip_mode_shift = EXYNOS_TMU_TRIP_MODE_SHIFT,
>>> @@ -174,6 +175,7 @@ struct exynos_tmu_init_data const
>>> exynos4412_default_tmu_data = { {
>>> EXYNOS4412_TMU_DATA,
>>> .type = SOC_ARCH_EXYNOS4412,
>>> + .test_mux = EXYNOS4412_MUX_ADDR_VALUE,
>>> },
>>> },
>>> .tmu_count = 1,
>>> diff --git a/drivers/thermal/samsung/exynos_tmu_data.h
>>> b/drivers/thermal/samsung/exynos_tmu_data.h index b130b1e..a1ea19d
>>> 100644 --- a/drivers/thermal/samsung/exynos_tmu_data.h
>>> +++ b/drivers/thermal/samsung/exynos_tmu_data.h
>>> @@ -95,6 +95,10 @@
>>>
>>> #define EXYNOS_MAX_TRIGGER_PER_REG 4
>>>
>>> +/* Exynos4412 specific */
>>> +#define EXYNOS4412_MUX_ADDR_VALUE 6
>>
>>> +#define EXYNOS4412_MUX_ADDR_SHIFT 20
>>> +
>>> /*exynos5440 specific registers*/
>>> #define EXYNOS5440_TMU_S0_7_TRIM 0x000
>>> #define EXYNOS5440_TMU_S0_7_CTRL 0x020
>>>
>>
>>
>
>
>
--
You have got to be excited about what you are doing. (L. Lamport)
Eduardo Valentin
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 295 bytes --]
next prev parent reply other threads:[~2013-10-14 19:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 8:08 [PATCH 0/6] thermal: exynos: Fixes for v3.12 Lukasz Majewski
2013-09-24 8:08 ` [PATCH 1/6] thermal: exynos: fix: Return from exynos_report_trigger() when therm_dev is NULL Lukasz Majewski
2013-09-30 10:52 ` amit daniel kachhap
2013-10-03 21:40 ` Eduardo Valentin
[not found] ` <524DE45E.1060606-l0cyMroinI0@public.gmane.org>
2013-10-04 9:56 ` Lukasz Majewski
2013-09-24 8:08 ` [PATCH 2/6] thermal: exynos: Provide separate TMU data for Exynos4412 Lukasz Majewski
2013-09-30 11:43 ` amit daniel kachhap
2013-10-03 22:01 ` Eduardo Valentin
2013-10-04 10:04 ` Lukasz Majewski
2013-09-24 8:08 ` [PATCH 3/6] thermal: exynos: Provide initial setting for TMU's test MUX address at Exynos4412 Lukasz Majewski
2013-09-30 11:59 ` amit daniel kachhap
[not found] ` <CADGdYn6a1jSR17v0N6kVFZFsn71FUbXJHjeSya-xy_wX9GtYpg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-01 6:55 ` Lukasz Majewski
[not found] ` <1380010102-25817-4-git-send-email-l.majewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-10-03 22:05 ` Eduardo Valentin
2013-10-04 10:20 ` Lukasz Majewski
2013-09-24 8:08 ` [PATCH 4/6] thermal: exynos: Replace SOC_ARCH_EXYNOS with SOC_ARCH_EXYNOS5250 Lukasz Majewski
[not found] ` <1380010102-25817-5-git-send-email-l.majewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-09-30 12:02 ` amit daniel kachhap
2013-10-03 22:08 ` Eduardo Valentin
2013-10-04 10:13 ` Bartlomiej Zolnierkiewicz
2013-10-04 10:23 ` Lukasz Majewski
2013-10-04 10:47 ` Bartlomiej Zolnierkiewicz
2013-10-04 15:07 ` Eduardo Valentin
2013-09-24 8:08 ` [PATCH 5/6] ARM: dts: exynos4x12: Device tree node definition for TMU on Exynos4x12 Lukasz Majewski
2013-09-24 8:08 ` [PATCH 6/6] ARM: dts: exynos4412-trats2: Enable TMU support at Trats2 Lukasz Majewski
2013-09-24 9:29 ` [PATCH 0/6] thermal: exynos: Fixes for v3.12 Tomasz Figa
2013-10-03 13:29 ` Lukasz Majewski
2013-10-09 6:29 ` [PATCH v2 0/5] " Lukasz Majewski
[not found] ` <1381300194-13134-1-git-send-email-l.majewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-10-09 6:29 ` [PATCH v2 1/5] thermal: exynos: Remove check for thermal device pointer at exynos_report_trigger() Lukasz Majewski
2013-10-09 6:29 ` [PATCH v2 2/5] thermal: exynos: Provide separate TMU data for Exynos4412 Lukasz Majewski
2013-10-14 14:20 ` Eduardo Valentin
2013-10-14 14:52 ` Lukasz Majewski
2013-10-09 6:29 ` [PATCH v2 3/5] thermal: exynos: Provide initial setting for TMU's test MUX address at Exynos4412 Lukasz Majewski
2013-10-14 14:24 ` Eduardo Valentin
2013-10-14 15:00 ` Lukasz Majewski
2013-10-14 19:20 ` Eduardo Valentin [this message]
2013-10-09 6:29 ` [PATCH v2 4/5] ARM: dts: exynos4x12: Device tree node definition for TMU on Exynos4x12 Lukasz Majewski
2013-10-15 6:27 ` Lukasz Majewski
2013-10-15 13:37 ` Eduardo Valentin
2013-11-27 7:11 ` Lukasz Majewski
2013-11-27 11:34 ` kgene
2013-11-27 12:39 ` Lukasz Majewski
2013-12-09 8:33 ` Lukasz Majewski
[not found] ` <1381300194-13134-5-git-send-email-l.majewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-11-14 10:03 ` [RESEND PATCH 1/2] " Lukasz Majewski
[not found] ` <1415959405-14157-1-git-send-email-l.majewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-11-14 10:03 ` [RESEND PATCH 2/2] ARM: dts: exynos4412-trats2: Enable TMU support at Trats2 Lukasz Majewski
2013-10-09 6:29 ` [PATCH v2 5/5] " Lukasz Majewski
2013-10-15 6:29 ` Lukasz Majewski
2013-11-27 7:12 ` Lukasz Majewski
2013-11-27 11:36 ` kgene
2014-11-14 9:26 ` Lukasz Majewski
2013-10-14 5:46 ` [PATCH v2 0/5] thermal: exynos: Fixes for v3.12 Lukasz Majewski
2013-10-14 5:52 ` Zhang, Rui
[not found] ` <744357E9AAD1214791ACBA4B0B90926301190077-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-10-14 19:13 ` Eduardo Valentin
2013-10-14 19:22 ` Eduardo Valentin
2013-10-15 6:23 ` Lukasz Majewski
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=525C43F8.4010001@ti.com \
--to=eduardo.valentin@ti.com \
--cc=amit.daniel@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=jonghwa3.lee@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=l.majewski@majess.pl \
--cc=l.majewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=t.figa@samsung.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;
as well as URLs for NNTP newsgroup(s).