From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl> To: Dmitry Osipenko <digetx@gmail.com> Cc: Russell King <linux@armlinux.org.uk>, Thierry Reding <thierry.reding@gmail.com>, Jonathan Hunter <jonathanh@nvidia.com>, Robert Yang <decatf@gmail.com>, linux-arm-kernel@lists.infradead.org, linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v9 1/7] ARM: trusted_foundations: Support L2 cache maintenance Date: Mon, 4 Mar 2019 16:47:29 +0100 [thread overview] Message-ID: <20190304154729.GA13794@qmqm.qmqm.pl> (raw) In-Reply-To: <20190303171214.24821-2-digetx@gmail.com> On Sun, Mar 03, 2019 at 08:12:08PM +0300, Dmitry Osipenko wrote: > Implement L2 cache initialization firmware callback that should be > invoked early during boot in order to set up the required outer cache > driver's callbacks and add the callback required for L2X0 maintenance. [...] > @@ -43,6 +46,11 @@ void register_trusted_foundations(struct trusted_foundations_platform_data *pd); > void of_register_trusted_foundations(void); > > #else /* CONFIG_TRUSTED_FOUNDATIONS */ > +static inline void tf_dummy_write_sec(unsigned long val, unsigned int reg) > +{ > + if (reg == L2X0_CTRL && val == L2X0_CTRL_EN) > + pr_err("Trusted Foundations unavailable, ignoring request to enable L2C\n"); > +} > > static inline void register_trusted_foundations( > struct trusted_foundations_platform_data *pd) > @@ -53,6 +61,10 @@ static inline void register_trusted_foundations( > */ > pr_err("No support for Trusted Foundations, continuing in degraded mode.\n"); > pr_err("Secondary processors as well as CPU PM will be disabled.\n"); > +#if IS_ENABLED(CONFIG_CACHE_L2X0) > + pr_err("L2X0 cache will be disabled.\n"); [...] I guess this is redundant since tf_dummy_write_sec() will say the same thing when trying to enable the cache. Best Regards, Michał Mirosław
WARNING: multiple messages have this Message-ID (diff)
From: "Michał Mirosław" <mirq-linux@rere.qmqm.pl> To: Dmitry Osipenko <digetx@gmail.com> Cc: linux-kernel@vger.kernel.org, Russell King <linux@armlinux.org.uk>, Jonathan Hunter <jonathanh@nvidia.com>, Thierry Reding <thierry.reding@gmail.com>, Robert Yang <decatf@gmail.com>, linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v9 1/7] ARM: trusted_foundations: Support L2 cache maintenance Date: Mon, 4 Mar 2019 16:47:29 +0100 [thread overview] Message-ID: <20190304154729.GA13794@qmqm.qmqm.pl> (raw) In-Reply-To: <20190303171214.24821-2-digetx@gmail.com> On Sun, Mar 03, 2019 at 08:12:08PM +0300, Dmitry Osipenko wrote: > Implement L2 cache initialization firmware callback that should be > invoked early during boot in order to set up the required outer cache > driver's callbacks and add the callback required for L2X0 maintenance. [...] > @@ -43,6 +46,11 @@ void register_trusted_foundations(struct trusted_foundations_platform_data *pd); > void of_register_trusted_foundations(void); > > #else /* CONFIG_TRUSTED_FOUNDATIONS */ > +static inline void tf_dummy_write_sec(unsigned long val, unsigned int reg) > +{ > + if (reg == L2X0_CTRL && val == L2X0_CTRL_EN) > + pr_err("Trusted Foundations unavailable, ignoring request to enable L2C\n"); > +} > > static inline void register_trusted_foundations( > struct trusted_foundations_platform_data *pd) > @@ -53,6 +61,10 @@ static inline void register_trusted_foundations( > */ > pr_err("No support for Trusted Foundations, continuing in degraded mode.\n"); > pr_err("Secondary processors as well as CPU PM will be disabled.\n"); > +#if IS_ENABLED(CONFIG_CACHE_L2X0) > + pr_err("L2X0 cache will be disabled.\n"); [...] I guess this is redundant since tf_dummy_write_sec() will say the same thing when trying to enable the cache. Best Regards, Michał Mirosław _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-04 15:47 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-03 17:12 [PATCH v9 0/7] Support Trusted Foundations firmware on Tegra30 Dmitry Osipenko 2019-03-03 17:12 ` Dmitry Osipenko 2019-03-03 17:12 ` [PATCH v9 1/7] ARM: trusted_foundations: Support L2 cache maintenance Dmitry Osipenko 2019-03-03 17:12 ` Dmitry Osipenko 2019-03-04 15:47 ` Michał Mirosław [this message] 2019-03-04 15:47 ` Michał Mirosław 2019-03-04 16:40 ` Dmitry Osipenko 2019-03-04 16:40 ` Dmitry Osipenko 2019-03-03 17:12 ` [PATCH v9 2/7] ARM: trusted_foundations: Make prepare_idle call to take mode argument Dmitry Osipenko 2019-03-03 17:12 ` Dmitry Osipenko 2019-03-03 17:12 ` [PATCH v9 3/7] ARM: trusted_foundations: Provide information about whether firmware is registered Dmitry Osipenko 2019-03-03 17:12 ` Dmitry Osipenko 2019-03-03 17:12 ` [PATCH v9 4/7] ARM: tegra: Set up L2 cache using Trusted Foundations firmware Dmitry Osipenko 2019-03-03 17:12 ` Dmitry Osipenko 2019-03-03 17:12 ` [PATCH v9 5/7] ARM: tegra: Don't apply CPU erratas in insecure mode Dmitry Osipenko 2019-03-03 17:12 ` Dmitry Osipenko 2019-03-03 17:12 ` [PATCH v9 6/7] ARM: tegra: Always boot CPU in ARM-mode Dmitry Osipenko 2019-03-03 17:12 ` Dmitry Osipenko 2019-03-03 17:12 ` [PATCH v9 7/7] ARM: tegra: Add firmware calls required for suspend-resume on Tegra30 Dmitry Osipenko 2019-03-03 17:12 ` Dmitry Osipenko
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=20190304154729.GA13794@qmqm.qmqm.pl \ --to=mirq-linux@rere.qmqm.pl \ --cc=decatf@gmail.com \ --cc=digetx@gmail.com \ --cc=jonathanh@nvidia.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=thierry.reding@gmail.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: 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.