From: Thomas Gleixner <hidden> Date: 2011-03-25 13:27:22
These functions are unused and in the way of cleanups in the core
code. If you have special requirements vs. irqs and PM then please
talk to me. Access to the generic core internals is going away.
Signed-off-by: Thomas Gleixner <redacted>
Cc: Colin Cross <redacted>
Cc: linux-tegra@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
---
arch/arm/mach-tegra/gpio.c | 63 -----------------------------
arch/arm/mach-tegra/include/mach/suspend.h | 2
2 files changed, 65 deletions(-)
Index: linux-2.6/arch/arm/mach-tegra/gpio.c
===================================================================
Thomas, then how do you think we should handle restoring of gpio states
across suspend-resume cycles?
On Friday 25 March 2011 06:51 PM, Thomas Gleixner wrote:
quoted hunk
These functions are unused and in the way of cleanups in the core
code. If you have special requirements vs. irqs and PM then please
talk to me. Access to the generic core internals is going away.
Signed-off-by: Thomas Gleixner <redacted>
Cc: Colin Cross <redacted>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
---
arch/arm/mach-tegra/gpio.c | 63 -----------------------------
arch/arm/mach-tegra/include/mach/suspend.h | 2
2 files changed, 65 deletions(-)
Index: linux-2.6/arch/arm/mach-tegra/gpio.c
===================================================================
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Thomas Gleixner <hidden> Date: 2011-03-26 20:25:04
On Sun, 27 Mar 2011, Varun Wadekar wrote:
Thomas, then how do you think we should handle restoring of gpio states
across suspend-resume cycles?
That code is unused. Period. No caller, nothing nada. So what does it
handle?
quoted
-
- for (i = INT_GPIO_BASE; i < (INT_GPIO_BASE + TEGRA_NR_GPIOS); i++) {
- struct irq_desc *desc = irq_to_desc(i);
- if (!desc || (desc->status & IRQ_WAKEUP))
- continue;
- enable_irq(i);
- }
And this part is totally unacceptable and should have never been
merged. Further it is in the way of cleanups to the core code and as
there is no user I'm not willing to even think about what it does and
why it is there.
FYI, the core code deals with interrupt suspending/resuming
already. So if there is a problem with that which does not cover your
specific problem, then you better talk to me before hacking up such
private workarounds and expecting that I tolerate them in unused code.
Thanks,
tglx
From: Colin Cross <hidden> Date: 2011-03-26 22:37:41
On Sat, Mar 26, 2011 at 1:24 PM, Thomas Gleixner [off-list ref] wrote:
On Sun, 27 Mar 2011, Varun Wadekar wrote:
quoted
Thomas, then how do you think we should handle restoring of gpio states
across suspend-resume cycles?
That code is unused. Period. No caller, nothing nada. So what does it
handle?
Tegra suspend support didn't make it into 2.6.39, but should get
merged in 2.6.40, and will call tegra_gpio_suspend/resume.
quoted
quoted
-
- for (i = INT_GPIO_BASE; i < (INT_GPIO_BASE + TEGRA_NR_GPIOS); i++) {
- struct irq_desc *desc = irq_to_desc(i);
- if (!desc || (desc->status & IRQ_WAKEUP))
- continue;
- enable_irq(i);
- }
And this part is totally unacceptable and should have never been
merged. Further it is in the way of cleanups to the core code and as
there is no user I'm not willing to even think about what it does and
why it is there.
FYI, the core code deals with interrupt suspending/resuming
already. So if there is a problem with that which does not cover your
specific problem, then you better talk to me before hacking up such
private workarounds and expecting that I tolerate them in unused code.
Yes, the existing code wrong, and unnecessary. It was copied from
mach-tegra/irq.c, which I later fixed, but I missed this one. I'll
take this patch for 2.6.39-rc1, which will prevent merge conflicts
between your tree and the tegra tree in 2.6.40.
From: Thomas Gleixner <hidden> Date: 2011-03-27 08:07:34
On Sat, 26 Mar 2011, Colin Cross wrote:
On Sat, Mar 26, 2011 at 1:24 PM, Thomas Gleixner [off-list ref] wrote:
quoted
On Sun, 27 Mar 2011, Varun Wadekar wrote:
quoted
Thomas, then how do you think we should handle restoring of gpio states
across suspend-resume cycles?
That code is unused. Period. No caller, nothing nada. So what does it
handle?
Tegra suspend support didn't make it into 2.6.39, but should get
merged in 2.6.40, and will call tegra_gpio_suspend/resume.
quoted
quoted
quoted
-
- for (i = INT_GPIO_BASE; i < (INT_GPIO_BASE + TEGRA_NR_GPIOS); i++) {
- struct irq_desc *desc = irq_to_desc(i);
- if (!desc || (desc->status & IRQ_WAKEUP))
- continue;
- enable_irq(i);
- }
And this part is totally unacceptable and should have never been
merged. Further it is in the way of cleanups to the core code and as
there is no user I'm not willing to even think about what it does and
why it is there.
FYI, the core code deals with interrupt suspending/resuming
already. So if there is a problem with that which does not cover your
specific problem, then you better talk to me before hacking up such
private workarounds and expecting that I tolerate them in unused code.
Yes, the existing code wrong, and unnecessary. It was copied from
mach-tegra/irq.c, which I later fixed, but I missed this one. I'll
take this patch for 2.6.39-rc1, which will prevent merge conflicts
between your tree and the tegra tree in 2.6.40.
You can keep the functions if you need them anyway, but the irq
fiddling needs to go now as it blocks core code cleanups.
Thanks,
tglx