From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH RESEND] phy: exynos-mipi-video: simplify check for coupled phy status
Date: Tue, 08 Nov 2016 07:27:12 +0100 [thread overview]
Message-ID: <35688181-78f1-b1c4-5824-e878052d88eb@samsung.com> (raw)
In-Reply-To: <2d8a48d1-2ecf-ad27-1e5a-a4233612c602@osg.samsung.com>
Hi Javier,
On 2016-11-07 19:50, Javier Martinez Canillas wrote:
> On 11/07/2016 07:48 AM, Marek Szyprowski wrote:
>> There is no need to access regmap of coupled phy to check its state - such
>> information is already in the phy device itself, so use it directly. This
>> let us to avoid possible access to registers of the device in the disabled
>> power domain if the coupled phy is already disabled.
>>
> Do you think this patch needs also go to stable?
Nope, there is no such need, because the problem with potential power domain
is specific for Exynos 5433, which is not yet merged to mainline.
>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>> Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
>> ---
> Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2016-11-08 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161107104844eucas1p2b5571119dff76e33d6ec038c359224f7@eucas1p2.samsung.com>
2016-11-07 10:48 ` Marek Szyprowski
2016-11-07 18:50 ` Javier Martinez Canillas
2016-11-08 6:27 ` Marek Szyprowski [this message]
2016-11-08 11:33 ` Javier Martinez Canillas
2016-11-15 13:33 ` Kishon Vijay Abraham I
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=35688181-78f1-b1c4-5824-e878052d88eb@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=javier@osg.samsung.com \
--cc=kishon@ti.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=s.nawrocki@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
all inboxes | Powered by JetHome®