From: "Christian Daudt" <csd@broadcom.com> To: Arnd Bergmann <arnd@arndb.de> Cc: Russell King <linux@arm.linux.org.uk>, Stephen Warren <swarren@wwwdotorg.org>, devicetree-discuss@lists.ozlabs.org, csd_b@daudt.org, "arm@kernel.org" <arm@kernel.org>, abhimanyu.kapur@outlook.com, Olof Johansson <olof@lixom.net>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] ARM: bcm281xx: Add L2 cache enable code Date: Tue, 5 Mar 2013 14:54:51 -0800 [thread overview] Message-ID: <513677BB.9010309@broadcom.com> (raw) In-Reply-To: <201303050901.12317.arnd@arndb.de> On 13-03-05 01:01 AM, Arnd Bergmann wrote: > On Tuesday 05 March 2013, Christian Daudt wrote: > >> diff --git a/Documentation/devicetree/bindings/misc/smc.txt b/Documentation/devicetree/bindings/misc/smc.txt >> new file mode 100644 >> index 0000000..cd8c729 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/misc/smc.txt >> @@ -0,0 +1,14 @@ >> +Broadcom Secure Monitor Bounce buffer >> +----------------------------------------------------- >> +This binding defines the location of the bounce buffer >> +used for non-secure to secure communications. >> + >> +Required properties: >> +- compatible : "bcm,kona-smc" >> +- reg : Location and size of bounce buffer >> + >> +Example: >> + smc@0x3404c000 { >> + compatible = "bcm,kona-smc"; >> + reg = <0x3404c000 0x400>; //1 KiB in SRAM >> + }; > For other firmware interfaces like this, we tend to list the specific commands > that the firmware understands. If you think there might be different versions > to consider, you might want to model this like > > Documentation/devicetree/bindings/arm/psci.txt This interface is stable and in shipping products at this time, and so the api will remain constant. >> diff --git a/arch/arm/mach-bcm/bcm_kona_smc_asm.S b/arch/arm/mach-bcm/bcm_kona_smc_asm.S >> new file mode 100644 >> index 0000000..a160848 >> --- /dev/null >> +++ b/arch/arm/mach-bcm/bcm_kona_smc_asm.S >> +/* >> + * int bcm_kona_smc_asm(u32 service_id, u32 buffer_addr) >> + */ >> + >> +ENTRY(bcm_kona_smc_asm) >> + stmfd sp!, {r4-r12, lr} >> + mov r4, r0 @ service_id >> + mov r5, #3 @ Keep IRQ and FIQ off in SM > Why not just use an inline assembly? We ran into problems with some gcc versions messing up the "arch_extension sec" when passing it to the assembler, so we broke it out to its own .S file following the example of omap and highbank. I suspect that they did it for the same reason. > >> +#ifdef CONFIG_CACHE_L2X0 >> +static int __init kona_l2_cache_init(void) >> +{ >> + /* >> + * Currently there is no SSAPI for setting the L2 cache aux register, >> + * so the default value (0x1e050000) applies. >> + */ >> + bcm_kona_smc(SSAPI_ENABLE_L2_CACHE, 0, 0, 0, 0); > This can be written in a nicer way as > > static int __init kona_l2_cache_init(void) > { > if (!IS_ENABLED(CONFIG_CACHE_L2X0)) > return 0; > ... > } > > To remove the need for the #ifdef. ok. done. >> +static void __init init_irq(void) >> +{ >> + irqchip_init(); >> + bcm_kona_smc_init(); >> + >> +#ifdef CONFIG_CACHE_L2X0 >> + kona_l2_cache_init(); >> +#endif /* CONFIG_CACHE_L2X0 */ >> +} > Why are you calling bcm_kona_smc_init() and kona_l2_cache_init() from init_irq()? > > It seems completely unrelated to interrupt handling. > It was originally in init_machine section but I was told that that was too late and init_irq would be better, and I saw that highbank also has it in init_irq. I agree that it is unrelated to irq - is there a better place to put this in ? thanks, csd
WARNING: multiple messages have this Message-ID (diff)
From: csd@broadcom.com (Christian Daudt) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] ARM: bcm281xx: Add L2 cache enable code Date: Tue, 5 Mar 2013 14:54:51 -0800 [thread overview] Message-ID: <513677BB.9010309@broadcom.com> (raw) In-Reply-To: <201303050901.12317.arnd@arndb.de> On 13-03-05 01:01 AM, Arnd Bergmann wrote: > On Tuesday 05 March 2013, Christian Daudt wrote: > >> diff --git a/Documentation/devicetree/bindings/misc/smc.txt b/Documentation/devicetree/bindings/misc/smc.txt >> new file mode 100644 >> index 0000000..cd8c729 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/misc/smc.txt >> @@ -0,0 +1,14 @@ >> +Broadcom Secure Monitor Bounce buffer >> +----------------------------------------------------- >> +This binding defines the location of the bounce buffer >> +used for non-secure to secure communications. >> + >> +Required properties: >> +- compatible : "bcm,kona-smc" >> +- reg : Location and size of bounce buffer >> + >> +Example: >> + smc at 0x3404c000 { >> + compatible = "bcm,kona-smc"; >> + reg = <0x3404c000 0x400>; //1 KiB in SRAM >> + }; > For other firmware interfaces like this, we tend to list the specific commands > that the firmware understands. If you think there might be different versions > to consider, you might want to model this like > > Documentation/devicetree/bindings/arm/psci.txt This interface is stable and in shipping products at this time, and so the api will remain constant. >> diff --git a/arch/arm/mach-bcm/bcm_kona_smc_asm.S b/arch/arm/mach-bcm/bcm_kona_smc_asm.S >> new file mode 100644 >> index 0000000..a160848 >> --- /dev/null >> +++ b/arch/arm/mach-bcm/bcm_kona_smc_asm.S >> +/* >> + * int bcm_kona_smc_asm(u32 service_id, u32 buffer_addr) >> + */ >> + >> +ENTRY(bcm_kona_smc_asm) >> + stmfd sp!, {r4-r12, lr} >> + mov r4, r0 @ service_id >> + mov r5, #3 @ Keep IRQ and FIQ off in SM > Why not just use an inline assembly? We ran into problems with some gcc versions messing up the "arch_extension sec" when passing it to the assembler, so we broke it out to its own .S file following the example of omap and highbank. I suspect that they did it for the same reason. > >> +#ifdef CONFIG_CACHE_L2X0 >> +static int __init kona_l2_cache_init(void) >> +{ >> + /* >> + * Currently there is no SSAPI for setting the L2 cache aux register, >> + * so the default value (0x1e050000) applies. >> + */ >> + bcm_kona_smc(SSAPI_ENABLE_L2_CACHE, 0, 0, 0, 0); > This can be written in a nicer way as > > static int __init kona_l2_cache_init(void) > { > if (!IS_ENABLED(CONFIG_CACHE_L2X0)) > return 0; > ... > } > > To remove the need for the #ifdef. ok. done. >> +static void __init init_irq(void) >> +{ >> + irqchip_init(); >> + bcm_kona_smc_init(); >> + >> +#ifdef CONFIG_CACHE_L2X0 >> + kona_l2_cache_init(); >> +#endif /* CONFIG_CACHE_L2X0 */ >> +} > Why are you calling bcm_kona_smc_init() and kona_l2_cache_init() from init_irq()? > > It seems completely unrelated to interrupt handling. > It was originally in init_machine section but I was told that that was too late and init_irq would be better, and I saw that highbank also has it in init_irq. I agree that it is unrelated to irq - is there a better place to put this in ? thanks, csd
next prev parent reply other threads:[~2013-03-05 22:54 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-05 2:47 [PATCH] ARM: bcm281xx: Add L2 cache enable code Christian Daudt 2013-03-05 2:47 ` Christian Daudt [not found] ` <1362451632-18806-1-git-send-email-csd-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> 2013-03-05 9:01 ` Arnd Bergmann 2013-03-05 9:01 ` Arnd Bergmann 2013-03-05 22:54 ` Christian Daudt [this message] 2013-03-05 22:54 ` Christian Daudt [not found] ` <513677BB.9010309-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> 2013-03-06 6:31 ` Arnd Bergmann 2013-03-06 6:31 ` Arnd Bergmann [not found] ` <5136F816.2070909@broadcom.com> [not found] ` <5136F816.2070909-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> 2013-03-06 11:28 ` Arnd Bergmann 2013-03-06 11:28 ` Arnd Bergmann 2013-03-06 15:05 ` Christian Daudt 2013-03-06 15:05 ` Christian Daudt 2013-04-10 17:33 ` [GIT PULL] ARM: bcm281xx firmware tags Christian Daudt 2013-04-10 17:33 ` Christian Daudt [not found] ` <5165A271.6060407-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> 2013-04-11 6:52 ` Olof Johansson 2013-04-11 6:52 ` Olof Johansson [not found] ` <20130411065227.GA31465-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org> 2013-04-11 8:52 ` Olof Johansson 2013-04-11 8:52 ` Olof Johansson 2013-03-05 18:20 ` [PATCH] ARM: bcm281xx: Add L2 cache enable code Stephen Warren 2013-03-05 18:20 ` Stephen Warren 2013-03-05 22:56 ` Christian Daudt 2013-03-05 22:56 ` Christian Daudt
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=513677BB.9010309@broadcom.com \ --to=csd@broadcom.com \ --cc=abhimanyu.kapur@outlook.com \ --cc=arm@kernel.org \ --cc=arnd@arndb.de \ --cc=csd_b@daudt.org \ --cc=devicetree-discuss@lists.ozlabs.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux@arm.linux.org.uk \ --cc=olof@lixom.net \ --cc=swarren@wwwdotorg.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: linkBe 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.