From: baruch@tkos.co.il (Baruch Siach)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: imx: make the imx timer driver implementation independent of SoCs.
Date: Wed, 29 Apr 2015 17:26:14 +0300 [thread overview]
Message-ID: <20150429142614.GE2258@tarshish> (raw)
In-Reply-To: <1430316881-4668-1-git-send-email-shenwei.wang@freescale.com>
Hi Shenwei Wang,
On Wed, Apr 29, 2015 at 09:14:41AM -0500, Shenwei Wang wrote:
> There are 4 versions of the timer hardware on Freescale MXC hardware.
> --Version 0: MX1/MXL
> --Version 1: MX21, MX27.
> --Version 2: MX25, MX31, MX35, MX37, MX51, MX6Q
> --Version 3: MX6DL, MX6SX
>
> This patch has removed the SoC related codes, and implemented the driver
> directly upon the hardware timer IP version.
>
> The new driver can be installed via device tree or the direct function
> call to mxc_timer_init in order to support imx legacy systems like MX21
> and MX27.
>
> For the device tree implementation, the driver is compatible with the current
> bindings like "fsl,imx6q-gpt", but for future dts file, the string like
> "fsl,imx-gpt-v2" without SoC information is recommended.
That is not the usual convention for IP block versions.
Please Cc the devicetree list (added).
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-04-29 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 14:14 [PATCH 1/1] ARM: imx: make the imx timer driver implementation independent of SoCs Shenwei Wang
2015-04-29 14:26 ` Baruch Siach [this message]
2015-04-29 14:55 ` Shenwei Wang
2015-04-29 15:08 ` Baruch Siach
2015-04-29 15:19 ` Shenwei Wang
2015-04-29 15:25 ` Baruch Siach
2015-04-29 16:34 ` Shenwei Wang
2015-04-29 18:57 ` Sascha Hauer
2015-04-29 19:56 ` Shenwei Wang
2015-04-30 5:15 ` Sascha Hauer
2015-04-30 15:16 ` Shenwei Wang
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=20150429142614.GE2258@tarshish \
--to=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
/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