From: pankaj.dubey@samsung•com (pankaj.dubey)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 0/2] Remove static mapping of SCU from mach-exynos
Date: Tue, 08 Nov 2016 10:00:13 +0530 [thread overview]
Message-ID: <582154D5.7020501@samsung.com> (raw)
In-Reply-To: <1478574864-24683-1-git-send-email-pankaj.dubey@samsung.com>
Hi,
On Tuesday 08 November 2016 08:44 AM, Pankaj Dubey wrote:
> This patch series is part of patch series [1], which adds support of SCU
> device node for Cortex-A9 based Exynos4 SoC. First two patches of the same
> has been accepted and hence not included them in v2.
>
> This patch series does some cleanup for Exynos4 SoC based boards.
> We are currently statically mapping SCU SFRs in mach-exynos/exynos.c
> which can be avoided if map this from device node of SCU.
>
> This patch introduces exynos_scu_enable in firmware.c file,
> which will be called from exynos_resume, which in turn called by pm.c and
> suspend.c as firmware_ops.
>
Please ignore this patchset as just noticed that firmware_ops needs not
be present for all boards, in that case exynos_resume ops won't be
defined in some of Exynos4 based boards and scu_enable won't be called.
I will think about some other approach and submit again.
Sorry for noise.
Thanks,
Pankaj Dubey
prev parent reply other threads:[~2016-11-08 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161108031123epcas1p2d5f60a1903a6005a5cf7eb7f6b392119@epcas1p2.samsung.com>
2016-11-08 3:14 ` [PATCH v2 0/2] Remove static mapping of SCU from mach-exynos Pankaj Dubey
2016-11-08 3:14 ` [PATCH v2 1/2] ARM: EXYNOS: Remove static mapping of SCU SFR Pankaj Dubey
2016-11-08 3:14 ` [PATCH v2 2/2] ARM: EXYNOS: Remove unused soc_is_exynos{4,5} Pankaj Dubey
2016-11-08 4:30 ` pankaj.dubey [this message]
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=582154D5.7020501@samsung.com \
--to=pankaj.dubey@samsung$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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