From: Alexander Holler <holler@ahsoftware.de>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: Tony Lindgren <tony@atomide.com>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] arm: omap3: beagle: Ensure msecure is mux'd to be able to set the RTC
Date: Tue, 07 Jun 2011 13:15:36 +0200 [thread overview]
Message-ID: <4DEE0858.2020308@ahsoftware.de> (raw)
In-Reply-To: <4DEDF451.1080604@compulab.co.il>
Am 07.06.2011 11:50, schrieb Igor Grinberg:
> On 06/07/11 11:01, Alexander Holler wrote:
>
>> Am 31.05.2011 12:29, schrieb Tony Lindgren:
>>> * Alexander Holler<holler@ahsoftware.de> [110405 06:38]:
>>>> Without msecure beeing high it isn't possible to set (or start)
>>>> the RTC.
>>>>
>>>> Tested with a BeagleBoard C4.
>>>
>>> Adding this into fixes.
>>>
>>> Tony
>>>
>>>> Signed-off-by: Alexander Holler<holler@ahsoftware.de>
>>>> ---
>>>> arch/arm/mach-omap2/board-omap3beagle.c | 3 +++
>>>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
>>>> index 46d814a..ebe3a7e 100644
>>>> --- a/arch/arm/mach-omap2/board-omap3beagle.c
>>>> +++ b/arch/arm/mach-omap2/board-omap3beagle.c
>>>> @@ -628,6 +628,9 @@ static void __init omap3_beagle_init(void)
>>>> usb_ehci_init(&ehci_pdata);
>>>> omap3beagle_flash_init();
>>>>
>>>> + /* Ensure msecure is mux'd to be able to set the RTC. */
>>>> + omap_mux_init_signal("sys_drm_msecure", OMAP_PIN_OFF_OUTPUT_HIGH);
>>>> +
>>>> /* Ensure SDRC pins are mux'd for self-refresh */
>>>> omap_mux_init_signal("sdrc_cke0", OMAP_PIN_OUTPUT);
>>>> omap_mux_init_signal("sdrc_cke1", OMAP_PIN_OUTPUT);
>>>> --
>>>> 1.7.3.4
>>>>
>>
>> I've later switched to the following patch which muxes msecure as GPIO (the drm-mode isn't explained in the TRM) and also exports the GPIO, so root could easily switch it to prevent modifications on the RTC.
>>
>> (Warning, either my clipboard or the version of Thunderbird I'm currently using replaces the tabs with spaces in the pasted patch and I'm currently too lazy to search a workaround).
>>
>> ---
>> arch/arm/mach-omap2/board-omap3beagle.c | 6 ++++++
>> 1 files changed, 6 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/board-omap3beagle.c b/arch/arm/mach-omap2/board-omap3beagle.c
>> index 33007fd..24b4417 100644
>> --- a/arch/arm/mach-omap2/board-omap3beagle.c
>> +++ b/arch/arm/mach-omap2/board-omap3beagle.c
>> @@ -673,6 +673,12 @@ static void __init omap3_beagle_init(void)
>> usbhs_init(&usbhs_bdata);
>> omap3beagle_flash_init();
>>
>> + /* Ensure msecure is high to be able to set the RTC. */
>> + omap_mux_init_signal("gpio_22", OMAP_PIN_OFF_OUTPUT_HIGH);
>> + gpio_request(22, "msecure");
>> + gpio_direction_output(22, true);
>
> Can this be gpio_request_one() instead, please?
> Also, it will be nice to make a define for the magic 22.
You need the "gpio_22" in the mux_init, so using a define would imho
introduce a potential source for an error, at least when the define
would not be anywhere near the "gpio_22" and someone would forget change
the string too, when he changes the define. So I don't think a define
adds much value there.
>
>> + gpio_export(22, false);
>> +
>> /* Ensure SDRC pins are mux'd for self-refresh */
>> omap_mux_init_signal("sdrc_cke0", OMAP_PIN_OUTPUT);
>> omap_mux_init_signal("sdrc_cke1", OMAP_PIN_OUTPUT);
>
Regards,
Alexander
next prev parent reply other threads:[~2011-06-07 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 14:29 rtc-twl: catch22 in 2.6.37 and 2.6.38 when clock was never set Alexander Holler
2011-04-05 10:14 ` Alexander Holler
2011-04-05 13:40 ` [PATCH] arm: omap3: beagle: Ensure msecure is mux'd to be able to set the RTC Alexander Holler
2011-05-31 10:29 ` Tony Lindgren
2011-06-07 8:01 ` Alexander Holler
2011-06-07 9:50 ` Igor Grinberg
2011-06-07 11:15 ` Alexander Holler [this message]
2011-06-08 21:57 ` Igor Grinberg
2011-06-09 0:21 ` Alexander Holler
2011-06-09 7:40 ` Igor Grinberg
2011-06-09 9:23 ` Alexander Holler
2011-05-31 10:28 ` rtc-twl: catch22 in 2.6.37 and 2.6.38 when clock was never set Tony Lindgren
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=4DEE0858.2020308@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=grinberg@compulab.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).