From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Lukasz Majewski <l.majewski@samsung.com>
Cc: k.kozlowski.k@gmail.com, linux-samsung-soc@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Eduardo Valentin <edubezval@gmail.com>,
Kukjin Kim <kgene@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] thermal: exynos: fix register read in TMU
Date: Sat, 10 Oct 2015 13:36:16 +0900 [thread overview]
Message-ID: <561895C0.5030400@samsung.com> (raw)
In-Reply-To: <20151009140716.0c6e57b7@amdc2363>
W dniu 09.10.2015 o 21:07, Lukasz Majewski pisze:
> Hi Krzysztof,
>
>> 2015-10-08 23:21 GMT+09:00 Sudip Mukherjee
>> <sudipm.mukherjee@gmail.com>:
>>> On Fri, Oct 02, 2015 at 08:43:52AM +0900, Krzysztof Kozlowski wrote:
>>>> 2015-10-01 23:12 GMT+09:00 Sudip Mukherjee
>>>> <sudipm.mukherjee@gmail.com>:
>>>>> On Thu, Oct 01, 2015 at 10:18:57PM +0900, Krzysztof Kozlowski
>>>>> wrote:
>>>>>> 2015-10-01 20:39 GMT+09:00 Sudip Mukherjee
>>>>>> <sudipm.mukherjee@gmail.com>:
>>>>>>> The value of emul_con was getting overwritten if the selected
>>>>>>> soc is SOC_ARCH_EXYNOS5260. And so as a result we were
>>>>>>> reading from the wrong register in the case of
>>>>>>> SOC_ARCH_EXYNOS5260.
>>>>>>
>>>>>> How the value is overwritten if the soc is Exynos5260? I can't
>>>>>> see it (although the "else if" is still more obvious than "if"
>>>>>> but how does the description match the code?).
>>>>> The code here is:
>>>>> if (data->soc == SOC_ARCH_EXYNOS5260)
>>>>> emul_con = EXYNOS5260_EMUL_CON;
>>>>> if (data->soc == SOC_ARCH_EXYNOS5433)
>>>>> emul_con = EXYNOS5433_TMU_EMUL_CON;
>>>>> else if (data->soc == SOC_ARCH_EXYNOS7)
>>>>> emul_con = EXYNOS7_TMU_REG_EMUL_CON;
>>>>> else
>>>>> emul_con = EXYNOS_EMUL_CON;
>>>>>
>>>>> So if data->soc is SOC_ARCH_EXYNOS5260 , then emul_con becomes
>>>>> EXYNOS5260_EMUL_CON. But again for the else part it will become
>>>>> EXYNOS_EMUL_CON.
>>>>
>>>> Indeed!
>>>>
>>>> Fixes: 488c7455d74c ("thermal: exynos: Add the support for
>>>> Exynos5433 TMU")
>>>>
>>>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>>>
>>> Hi Krzysztof,
>>> Who will pick this one up? I still do not see it in linux-next.
>>
>> Hi!
>>
>> I guess it is a patch for Lukasz.
>>
>> Lukasz,
>> Do you plan to pick it up or maybe this should go through samsung-soc
>> tree?
>
> This is the only one patch, which is waiting in my queue. Since no more
> fixes available, please feel free to grab this patch to samsung-soc.
>
> Acked-by: Lukasz Majewski <l.majewski@samsung.com>
Okay, thanks! Applied to fixes for current cycle. I'll it send later to
Kukjin (unless he picks it as well).
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] thermal: exynos: fix register read in TMU
Date: Sat, 10 Oct 2015 13:36:16 +0900 [thread overview]
Message-ID: <561895C0.5030400@samsung.com> (raw)
In-Reply-To: <20151009140716.0c6e57b7@amdc2363>
W dniu 09.10.2015 o 21:07, Lukasz Majewski pisze:
> Hi Krzysztof,
>
>> 2015-10-08 23:21 GMT+09:00 Sudip Mukherjee
>> <sudipm.mukherjee@gmail.com>:
>>> On Fri, Oct 02, 2015 at 08:43:52AM +0900, Krzysztof Kozlowski wrote:
>>>> 2015-10-01 23:12 GMT+09:00 Sudip Mukherjee
>>>> <sudipm.mukherjee@gmail.com>:
>>>>> On Thu, Oct 01, 2015 at 10:18:57PM +0900, Krzysztof Kozlowski
>>>>> wrote:
>>>>>> 2015-10-01 20:39 GMT+09:00 Sudip Mukherjee
>>>>>> <sudipm.mukherjee@gmail.com>:
>>>>>>> The value of emul_con was getting overwritten if the selected
>>>>>>> soc is SOC_ARCH_EXYNOS5260. And so as a result we were
>>>>>>> reading from the wrong register in the case of
>>>>>>> SOC_ARCH_EXYNOS5260.
>>>>>>
>>>>>> How the value is overwritten if the soc is Exynos5260? I can't
>>>>>> see it (although the "else if" is still more obvious than "if"
>>>>>> but how does the description match the code?).
>>>>> The code here is:
>>>>> if (data->soc == SOC_ARCH_EXYNOS5260)
>>>>> emul_con = EXYNOS5260_EMUL_CON;
>>>>> if (data->soc == SOC_ARCH_EXYNOS5433)
>>>>> emul_con = EXYNOS5433_TMU_EMUL_CON;
>>>>> else if (data->soc == SOC_ARCH_EXYNOS7)
>>>>> emul_con = EXYNOS7_TMU_REG_EMUL_CON;
>>>>> else
>>>>> emul_con = EXYNOS_EMUL_CON;
>>>>>
>>>>> So if data->soc is SOC_ARCH_EXYNOS5260 , then emul_con becomes
>>>>> EXYNOS5260_EMUL_CON. But again for the else part it will become
>>>>> EXYNOS_EMUL_CON.
>>>>
>>>> Indeed!
>>>>
>>>> Fixes: 488c7455d74c ("thermal: exynos: Add the support for
>>>> Exynos5433 TMU")
>>>>
>>>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>>>
>>> Hi Krzysztof,
>>> Who will pick this one up? I still do not see it in linux-next.
>>
>> Hi!
>>
>> I guess it is a patch for Lukasz.
>>
>> Lukasz,
>> Do you plan to pick it up or maybe this should go through samsung-soc
>> tree?
>
> This is the only one patch, which is waiting in my queue. Since no more
> fixes available, please feel free to grab this patch to samsung-soc.
>
> Acked-by: Lukasz Majewski <l.majewski@samsung.com>
Okay, thanks! Applied to fixes for current cycle. I'll it send later to
Kukjin (unless he picks it as well).
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-10-10 4:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 11:39 [PATCH] thermal: exynos: fix register read in TMU Sudip Mukherjee
2015-10-01 11:39 ` Sudip Mukherjee
2015-10-01 13:18 ` Krzysztof Kozlowski
2015-10-01 13:18 ` Krzysztof Kozlowski
2015-10-01 14:12 ` Sudip Mukherjee
2015-10-01 14:12 ` Sudip Mukherjee
2015-10-01 23:43 ` Krzysztof Kozlowski
2015-10-01 23:43 ` Krzysztof Kozlowski
2015-10-08 14:21 ` Sudip Mukherjee
2015-10-08 14:21 ` Sudip Mukherjee
2015-10-09 11:35 ` Krzysztof Kozlowski
2015-10-09 11:35 ` Krzysztof Kozlowski
2015-10-09 12:07 ` Lukasz Majewski
2015-10-09 12:07 ` Lukasz Majewski
2015-10-10 4:36 ` Krzysztof Kozlowski [this message]
2015-10-10 4:36 ` Krzysztof Kozlowski
2015-10-02 0:03 ` Chanwoo Choi
2015-10-02 0:03 ` Chanwoo Choi
-- strict thread matches above, loose matches on Subject: below --
2015-10-12 23:51 [PATCH] thermal: exynos: Fix " Krzysztof Kozlowski
2015-10-12 23:51 ` Krzysztof Kozlowski
2015-10-16 23:20 ` Kukjin Kim
2015-10-16 23:20 ` Kukjin Kim
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=561895C0.5030400@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=edubezval@gmail.com \
--cc=k.kozlowski.k@gmail.com \
--cc=kgene@kernel.org \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rui.zhang@intel.com \
--cc=sudipm.mukherjee@gmail.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 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.