RE: [PATCH v2 2/4] RTC MSECURE: msecure initialization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Charu -- possible bug

>-----Original Message-----
>From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of
>Varadarajan, Charu Latha
> /*
>+ * msecure line initialisation for TWL4030 RTC registers write access
>+ */
>+static int msecure_init(struct twl4030_rtc_platform_data *pdata)
>+{
>+	int ret = 0;
>+	if (pdata == NULL)
>+		goto out;
>+
>+	ret = gpio_request(pdata->msecure_gpio, "msecure");

What about other boards like: Beagle, EVM, Pandora, Zoom2, RX51
What about SDP/LDP with OMAP ES2.1 and above

For these boards, there is no msecure_gpio defined. 

What would be the value for msecure_gpio for these boards?


>+	if (ret) {
>+		pr_err("twl4030_rtc: can't reserve msecure GPIO:%d !\n"
>+			"RTC functionality will not be available\n",
>+			pdata->msecure_gpio);
>+		goto out;
>+	}
>+	/*
>+	 * TWL4030 will be in secure mode if msecure line from OMAP is low.
>+	 * Make msecure line high in order to change the TWL4030 RTC time
>+	 * and calender registers.
>+	 */
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux