From: fabio.estevam@freescale.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: I.MX35 PDK
Date: Tue, 6 Mar 2012 12:26:08 -0300 [thread overview]
Message-ID: <4F562C90.6090103@freescale.com> (raw)
In-Reply-To: <4875438356E7CA4A8F2145FCD3E61C0B2CBD666A26@MEP-EXCH.meprolight.com>
Alex Gershgorin wrote:
> Hi Fabio,
>
>
>
> How I can get information about accesses to CMOS_RST_B and CSI_PWDN bits
> of MC9S08DZ60 processor.
>
> I need address of this register and bits mapping in this register.
You can check Freescale kernel to get this information:
http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=shortlog;h=refs/heads/imx_2.6.31
Search for "pmic_gpio_set_bit_val"
Wu Guoxing submitted the mc9s08dz60 driver patch to mainline:
drivers/gpio/gpio-mc9s08dz60.c
Regards,
Fabio Estevam
next parent reply other threads:[~2012-03-06 15:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4875438356E7CA4A8F2145FCD3E61C0B2CBD666A26@MEP-EXCH.meprolight.com>
2012-03-06 15:26 ` Fabio Estevam [this message]
2012-03-06 15:35 ` I.MX35 PDK Alex Gershgorin
2012-03-07 12:18 ` Fabio Estevam
2012-03-07 14:05 ` Alex Gershgorin
2012-03-07 14:17 ` Fabio Estevam
2012-03-08 11:16 ` Alex Gershgorin
2012-03-08 11:16 ` Alex Gershgorin
2012-03-08 11:26 ` Fabio Estevam
2012-03-08 11:26 ` Fabio Estevam
2012-03-08 12:10 ` Alex Gershgorin
2012-03-08 12:10 ` Alex Gershgorin
2012-03-08 15:36 ` Alex Gershgorin
2012-03-08 15:36 ` Alex Gershgorin
2012-03-08 15:46 ` Fabio Estevam
2012-03-08 15:46 ` Fabio Estevam
[not found] ` <4875438356E7CA4A8F2145FCD3E61C0B2CBD666A29@MEP-EXCH.meprolight.com>
2012-03-12 13:24 ` Fabio Estevam
2012-03-12 13:24 ` Fabio Estevam
2012-03-12 16:06 ` Alex Gershgorin
2012-03-12 16:06 ` Alex Gershgorin
2012-03-08 11:34 ` Guennadi Liakhovetski
2012-03-08 11:34 ` Guennadi Liakhovetski
2012-03-08 13:43 ` Alex Gershgorin
2012-03-08 13:43 ` Alex Gershgorin
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=4F562C90.6090103@freescale.com \
--to=fabio.estevam@freescale.com \
--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 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.