From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, willy.mh.wolff.ml@gmail.com,
k.konieczny@samsung.com, cw00.choi@samsung.com,
b.zolnierkie@samsung.com, chanwoo@kernel.org,
myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
s.nawrocki@samsung.com, kgene@kernel.org
Subject: Re: [PATCH v2 2/2] memory: samsung: exynos5422-dmc: Add module param to control IRQ mode
Date: Mon, 20 Jul 2020 16:46:48 +0200 [thread overview]
Message-ID: <20200720144648.GC22791@kozik-lap> (raw)
In-Reply-To: <20200710191122.11029-3-lukasz.luba@arm.com>
On Fri, Jul 10, 2020 at 08:11:22PM +0100, Lukasz Luba wrote:
> The driver can operate in two modes relaying on devfreq monitoring
> mechanism which periodically checks the device status or it can use
> interrupts when they are provided by loaded Device Tree. The newly
> introduced module parameter can be used to choose between devfreq
> monitoring and internal interrupts without modifying the Device Tree.
> It also sets devfreq monitoring as default when the parameter is not set
> (also the case for default when the driver is not built as a module).
>
> Reported-by: Willy Wolff <willy.mh.wolff.ml@gmail.com>
> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
> ---
> drivers/memory/samsung/exynos5422-dmc.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Lukasz Luba <lukasz.luba@arm.com>
Cc: linux-samsung-soc@vger.kernel.org, s.nawrocki@samsung.com,
linux-pm@vger.kernel.org, k.konieczny@samsung.com,
b.zolnierkie@samsung.com, linux-kernel@vger.kernel.org,
cw00.choi@samsung.com, kyungmin.park@samsung.com,
willy.mh.wolff.ml@gmail.com, myungjoo.ham@samsung.com,
chanwoo@kernel.org, kgene@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] memory: samsung: exynos5422-dmc: Add module param to control IRQ mode
Date: Mon, 20 Jul 2020 16:46:48 +0200 [thread overview]
Message-ID: <20200720144648.GC22791@kozik-lap> (raw)
In-Reply-To: <20200710191122.11029-3-lukasz.luba@arm.com>
On Fri, Jul 10, 2020 at 08:11:22PM +0100, Lukasz Luba wrote:
> The driver can operate in two modes relaying on devfreq monitoring
> mechanism which periodically checks the device status or it can use
> interrupts when they are provided by loaded Device Tree. The newly
> introduced module parameter can be used to choose between devfreq
> monitoring and internal interrupts without modifying the Device Tree.
> It also sets devfreq monitoring as default when the parameter is not set
> (also the case for default when the driver is not built as a module).
>
> Reported-by: Willy Wolff <willy.mh.wolff.ml@gmail.com>
> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
> ---
> drivers/memory/samsung/exynos5422-dmc.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-20 14:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200710191144epcas1p30f82bf6371f7f09a4e1ea1262234f392@epcas1p3.samsung.com>
2020-07-10 19:11 ` [PATCH v2 0/2] Exynos5422 DMC: adjust to new devfreq monitoring mechanism Lukasz Luba
2020-07-10 19:11 ` Lukasz Luba
2020-07-10 19:11 ` [PATCH v2 1/2] memory: samsung: exynos5422-dmc: Adjust polling interval and uptreshold Lukasz Luba
2020-07-10 19:11 ` Lukasz Luba
2020-07-20 14:46 ` Krzysztof Kozlowski
2020-07-20 14:46 ` Krzysztof Kozlowski
2020-07-27 8:20 ` Lukasz Luba
2020-07-27 8:20 ` Lukasz Luba
2020-07-10 19:11 ` [PATCH v2 2/2] memory: samsung: exynos5422-dmc: Add module param to control IRQ mode Lukasz Luba
2020-07-10 19:11 ` Lukasz Luba
2020-07-14 7:42 ` Bartlomiej Zolnierkiewicz
2020-07-14 7:42 ` Bartlomiej Zolnierkiewicz
2020-07-14 9:01 ` Lukasz Luba
2020-07-14 9:01 ` Lukasz Luba
2020-07-14 9:32 ` Willy Wolff
2020-07-14 9:32 ` Willy Wolff
2020-07-14 9:50 ` Lukasz Luba
2020-07-14 9:50 ` Lukasz Luba
2020-07-17 11:53 ` Lukasz Luba
2020-07-17 11:53 ` Lukasz Luba
2020-07-17 12:31 ` Bartlomiej Zolnierkiewicz
2020-07-17 12:31 ` Bartlomiej Zolnierkiewicz
2020-07-20 14:46 ` Krzysztof Kozlowski [this message]
2020-07-20 14:46 ` Krzysztof Kozlowski
2020-08-03 15:30 ` Marek Szyprowski
2020-08-03 15:30 ` Marek Szyprowski
2020-08-03 15:35 ` Marek Szyprowski
2020-08-03 15:35 ` Marek Szyprowski
2020-08-04 8:06 ` Lukasz Luba
2020-08-04 8:06 ` Lukasz Luba
2020-07-24 1:40 ` [PATCH v2 0/2] Exynos5422 DMC: adjust to new devfreq monitoring mechanism Chanwoo Choi
2020-07-24 1:40 ` Chanwoo Choi
2020-07-27 8:21 ` Lukasz Luba
2020-07-27 8:21 ` Lukasz Luba
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=20200720144648.GC22791@kozik-lap \
--to=krzk@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=k.konieczny@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@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=lukasz.luba@arm.com \
--cc=myungjoo.ham@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=willy.mh.wolff.ml@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.