* [PATCH v2 0/2] bus: brcmstb_gisb: misc fixes @ 2014-09-19 19:50 Florian Fainelli 2014-09-19 19:50 ` [PATCH v2 1/2] bus: brcmstb_gisb: register the fault code hook Florian Fainelli 2014-09-19 19:50 ` [PATCH v2 2/2] bus: brcmstb_gisb: save and restore GISB timeout Florian Fainelli 0 siblings, 2 replies; 5+ messages in thread From: Florian Fainelli @ 2014-09-19 19:50 UTC (permalink / raw) To: linux-arm-kernel Hello Arnd, Hi Arnd, This patch set contains two small fixes for the Broadcom GISB bus arbiter code. First patch makes sure we do register a fault code for ARM platforms, second patch is a fix when the code is used on a PM capable system. Changes in v2: - move the hunk that adds 'saved_timeout' where it belongs, in patch 2 Florian Fainelli (2): bus: brcmstb_gisb: register the fault code hook bus: brcmstb_gisb: save and restore GISB timeout drivers/bus/brcmstb_gisb.c | 40 +++++++++++++++++++++++++++++++++++++++- 1 file changed, 39 insertions(+), 1 deletion(-) -- 1.9.1 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH v2 1/2] bus: brcmstb_gisb: register the fault code hook 2014-09-19 19:50 [PATCH v2 0/2] bus: brcmstb_gisb: misc fixes Florian Fainelli @ 2014-09-19 19:50 ` Florian Fainelli 2014-09-19 20:17 ` Brian Norris 2014-09-19 19:50 ` [PATCH v2 2/2] bus: brcmstb_gisb: save and restore GISB timeout Florian Fainelli 1 sibling, 1 reply; 5+ messages in thread From: Florian Fainelli @ 2014-09-19 19:50 UTC (permalink / raw) To: linux-arm-kernel Commit 44127b771d9c31 ("bus: add Broadcom GISB bus arbiter timeout/error handler") added everything that is required to register an ARM fault handler for imprecise external aborts, except that there is nothing calling this currently. We do not need to export that specific function and have to update arch/arm/mach-bcm/brcmstb.c to call it, simply, register the fault handler with an arch_initcall. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> --- Changes in v2: - removed the accidental hunk that added saved_timeout since it does not belong in this patch drivers/bus/brcmstb_gisb.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/bus/brcmstb_gisb.c b/drivers/bus/brcmstb_gisb.c index f2cd6a2d40b4..5b608955957a 100644 --- a/drivers/bus/brcmstb_gisb.c +++ b/drivers/bus/brcmstb_gisb.c @@ -160,11 +160,13 @@ static int brcmstb_bus_error_handler(unsigned long addr, unsigned int fsr, return ret; } -void __init brcmstb_hook_fault_code(void) +static int __init brcmstb_hook_fault_code(void) { hook_fault_code(22, brcmstb_bus_error_handler, SIGBUS, 0, "imprecise external abort"); + return 0; } +arch_initcall(brcmstb_hook_fault_code) static irqreturn_t brcmstb_gisb_timeout_handler(int irq, void *dev_id) { -- 1.9.1 ^ permalink raw reply related [flat|nested] 5+ messages in thread
* [PATCH v2 1/2] bus: brcmstb_gisb: register the fault code hook 2014-09-19 19:50 ` [PATCH v2 1/2] bus: brcmstb_gisb: register the fault code hook Florian Fainelli @ 2014-09-19 20:17 ` Brian Norris 2014-09-19 21:11 ` Florian Fainelli 0 siblings, 1 reply; 5+ messages in thread From: Brian Norris @ 2014-09-19 20:17 UTC (permalink / raw) To: linux-arm-kernel On Fri, Sep 19, 2014 at 12:50:29PM -0700, Florian Fainelli wrote: > Commit 44127b771d9c31 ("bus: add Broadcom GISB bus arbiter timeout/error > handler") added everything that is required to register an ARM fault > handler for imprecise external aborts, except that there is nothing > calling this currently. > > We do not need to export that specific function and have to update > arch/arm/mach-bcm/brcmstb.c to call it, simply, register the fault > handler with an arch_initcall. Am I missing something, or does that mean that this error handler will be registered for *all* kernels which include this driver? e.g., anyone using multi_v7_defconfig? So it seems we need to gate this behind some kind of machine check; either called from mach-bcm/*, or better, from something that is probed via device tree. Is it a problem to register this in the probe() function, like drivers/pci/host/pci-imx6.c? > Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> > --- > Changes in v2: > - removed the accidental hunk that added saved_timeout since it does > not belong in this patch > > drivers/bus/brcmstb_gisb.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/drivers/bus/brcmstb_gisb.c b/drivers/bus/brcmstb_gisb.c > index f2cd6a2d40b4..5b608955957a 100644 > --- a/drivers/bus/brcmstb_gisb.c > +++ b/drivers/bus/brcmstb_gisb.c > @@ -160,11 +160,13 @@ static int brcmstb_bus_error_handler(unsigned long addr, unsigned int fsr, > return ret; > } > > -void __init brcmstb_hook_fault_code(void) > +static int __init brcmstb_hook_fault_code(void) > { > hook_fault_code(22, brcmstb_bus_error_handler, SIGBUS, 0, > "imprecise external abort"); > + return 0; > } > +arch_initcall(brcmstb_hook_fault_code) > > static irqreturn_t brcmstb_gisb_timeout_handler(int irq, void *dev_id) > { Brian ^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH v2 1/2] bus: brcmstb_gisb: register the fault code hook 2014-09-19 20:17 ` Brian Norris @ 2014-09-19 21:11 ` Florian Fainelli 0 siblings, 0 replies; 5+ messages in thread From: Florian Fainelli @ 2014-09-19 21:11 UTC (permalink / raw) To: linux-arm-kernel On 09/19/2014 01:17 PM, Brian Norris wrote: > On Fri, Sep 19, 2014 at 12:50:29PM -0700, Florian Fainelli wrote: >> Commit 44127b771d9c31 ("bus: add Broadcom GISB bus arbiter timeout/error >> handler") added everything that is required to register an ARM fault >> handler for imprecise external aborts, except that there is nothing >> calling this currently. >> >> We do not need to export that specific function and have to update >> arch/arm/mach-bcm/brcmstb.c to call it, simply, register the fault >> handler with an arch_initcall. > > Am I missing something, or does that mean that this error handler will > be registered for *all* kernels which include this driver? e.g., anyone > using multi_v7_defconfig? That's a very good point, at first I was relying on the fact that even though we register our fault code, this is not much of a problem because the list is empty until we get to probe the gisb-arb node, it would be empty for non-brcmstb platforms, but that's not a good thing. > > So it seems we need to gate this behind some kind of machine check; > either called from mach-bcm/*, or better, from something that is probed > via device tree. Is it a problem to register this in the probe() > function, like drivers/pci/host/pci-imx6.c? No, I do not think this is a problem, there might be a small window during which we enable external aborts exceptions and we have no handler for it yet, but I will check that more thoroughly. > >> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> >> --- >> Changes in v2: >> - removed the accidental hunk that added saved_timeout since it does >> not belong in this patch >> >> drivers/bus/brcmstb_gisb.c | 4 +++- >> 1 file changed, 3 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/bus/brcmstb_gisb.c b/drivers/bus/brcmstb_gisb.c >> index f2cd6a2d40b4..5b608955957a 100644 >> --- a/drivers/bus/brcmstb_gisb.c >> +++ b/drivers/bus/brcmstb_gisb.c >> @@ -160,11 +160,13 @@ static int brcmstb_bus_error_handler(unsigned long addr, unsigned int fsr, >> return ret; >> } >> >> -void __init brcmstb_hook_fault_code(void) >> +static int __init brcmstb_hook_fault_code(void) >> { >> hook_fault_code(22, brcmstb_bus_error_handler, SIGBUS, 0, >> "imprecise external abort"); >> + return 0; >> } >> +arch_initcall(brcmstb_hook_fault_code) >> >> static irqreturn_t brcmstb_gisb_timeout_handler(int irq, void *dev_id) >> { > > Brian > ^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH v2 2/2] bus: brcmstb_gisb: save and restore GISB timeout 2014-09-19 19:50 [PATCH v2 0/2] bus: brcmstb_gisb: misc fixes Florian Fainelli 2014-09-19 19:50 ` [PATCH v2 1/2] bus: brcmstb_gisb: register the fault code hook Florian Fainelli @ 2014-09-19 19:50 ` Florian Fainelli 1 sibling, 0 replies; 5+ messages in thread From: Florian Fainelli @ 2014-09-19 19:50 UTC (permalink / raw) To: linux-arm-kernel When the system enters S3, we will lose the GISB timeout value we have configured, make sure that we do save this timeout value, and restore this timeout value prior to re-enabling interrupts such that the GISB timeout interrupt will fire with the expected timeout. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> --- Changes in v2: - took the hunk that adds saved_timeout here drivers/bus/brcmstb_gisb.c | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/drivers/bus/brcmstb_gisb.c b/drivers/bus/brcmstb_gisb.c index 5b608955957a..c202c97493de 100644 --- a/drivers/bus/brcmstb_gisb.c +++ b/drivers/bus/brcmstb_gisb.c @@ -23,6 +23,7 @@ #include <linux/list.h> #include <linux/of.h> #include <linux/bitops.h> +#include <linux/pm.h> #include <asm/bug.h> #include <asm/signal.h> @@ -48,6 +49,7 @@ struct brcmstb_gisb_arb_device { struct list_head next; u32 valid_mask; const char *master_names[sizeof(u32) * BITS_PER_BYTE]; + u32 saved_timeout; }; static LIST_HEAD(brcmstb_gisb_arb_device_list); @@ -269,6 +271,39 @@ static int brcmstb_gisb_arb_probe(struct platform_device *pdev) return 0; } +#ifdef CONFIG_PM_SLEEP +static int brcmstb_gisb_arb_suspend(struct device *dev) +{ + struct platform_device *pdev = to_platform_device(dev); + struct brcmstb_gisb_arb_device *gdev = platform_get_drvdata(pdev); + + gdev->saved_timeout = ioread32(gdev->base + ARB_TIMER); + + return 0; +} + +/* Make sure we provide the same timeout value that was configured before, and + * do this before the GISB timeout interrupt handler has any chance to run. + */ +static int brcmstb_gisb_arb_resume_noirq(struct device *dev) +{ + struct platform_device *pdev = to_platform_device(dev); + struct brcmstb_gisb_arb_device *gdev = platform_get_drvdata(pdev); + + iowrite32(gdev->saved_timeout, gdev->base + ARB_TIMER); + + return 0; +} +#else +#define brcmstb_gisb_arb_suspend NULL +#define brcmstb_gisb_arb_resume_noirq NULL +#endif + +static const struct dev_pm_ops brcmstb_gisb_arb_pm_ops = { + .suspend = brcmstb_gisb_arb_suspend, + .resume_noirq = brcmstb_gisb_arb_resume_noirq, +}; + static const struct of_device_id brcmstb_gisb_arb_of_match[] = { { .compatible = "brcm,gisb-arb" }, { }, @@ -280,6 +315,7 @@ static struct platform_driver brcmstb_gisb_arb_driver = { .name = "brcm-gisb-arb", .owner = THIS_MODULE, .of_match_table = brcmstb_gisb_arb_of_match, + .pm = &brcmstb_gisb_arb_pm_ops, }, }; -- 1.9.1 ^ permalink raw reply related [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-09-19 21:11 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-09-19 19:50 [PATCH v2 0/2] bus: brcmstb_gisb: misc fixes Florian Fainelli 2014-09-19 19:50 ` [PATCH v2 1/2] bus: brcmstb_gisb: register the fault code hook Florian Fainelli 2014-09-19 20:17 ` Brian Norris 2014-09-19 21:11 ` Florian Fainelli 2014-09-19 19:50 ` [PATCH v2 2/2] bus: brcmstb_gisb: save and restore GISB timeout Florian Fainelli
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).