From: khilman@deeprootsystems•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/2] ARM: OMAP: SmartReflex: pass device dependent data via platform data
Date: Thu, 04 Oct 2012 16:40:20 -0700 [thread overview]
Message-ID: <87r4pdst5n.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1349369231-25204-1-git-send-email-j-pihet@ti.com> (jean pihet's message of "Thu, 4 Oct 2012 18:47:09 +0200")
jean.pihet at newoldbits.com writes:
> From: Jean Pihet <j-pihet@ti•com>
>
> Remove the device dependent code (ex. cpu_is_xxx()) and settings
> from the driver code and instead pass them via the platform
> data. This allows a clean separation of the driver code and the platform
> code, as required by the move of the platform header files to
> include/linux/platform_data.
>
> Note about the smartreflex functional clocks: the smartreflex fclks
> are derived from sys_clk and have the same name as the main_clk from
> the hwmod entry, in order for the SmartReflex driver to request the
> fclk (using clk_get(dev, "fck")).
>
> Based on mainline 3.6.0. Boot tested on OMAP3&4 platforms.
Thanks, queuing this version for v3.8 (branch: for_3.8/pm/sr)
Kevin
P.S. in the future, It helps reviewers and maintainers if there's some
versioning in the patches (e.g. PATCH v3 0/2]), especially when updated
versions come in quick succession. Thanks.
next prev parent reply other threads:[~2012-10-04 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 16:47 [PATCH 0/2] ARM: OMAP: SmartReflex: pass device dependent data via platform data jean.pihet at newoldbits.com
2012-10-04 16:47 ` [PATCH 1/2] ARM: OMAP: hwmod: align the SmartReflex fck names jean.pihet at newoldbits.com
2012-10-04 16:47 ` [PATCH 2/2] ARM: OMAP: SmartReflex: pass device dependent data via platform data jean.pihet at newoldbits.com
2012-10-04 23:40 ` Kevin Hilman [this message]
2012-10-05 8:10 ` [PATCH 0/2] " Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2012-10-03 15:47 jean.pihet at newoldbits.com
2012-09-20 14:47 Jean Pihet
2012-09-24 14:16 ` Jean Pihet
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=87r4pdst5n.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems$(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