From: Benjamin GAIGNARD <benjamin.gaignard@st.com> To: Hugues FRUCHET <hugues.fruchet@st.com>, "mchehab@kernel.org" <mchehab@kernel.org>, "mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>, Alexandre TORGUE <alexandre.torgue@st.com>, "robh+dt@kernel.org" <robh+dt@kernel.org> Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>, "linux-stm32@st-md-mailman.stormreply.com" <linux-stm32@st-md-mailman.stormreply.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "vincent.guittot@linaro.org" <vincent.guittot@linaro.org>, "valentin.schneider@arm.com" <valentin.schneider@arm.com>, "rjw@rjwysocki.net" <rjw@rjwysocki.net>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org> Subject: Re: [PATCH v6 0/3] DCMI set minimum cpufreq requirement Date: Wed, 1 Jul 2020 13:02:45 +0000 [thread overview] Message-ID: <52850ead-3e49-7f24-e96b-3f6f293d54fe@st.com> (raw) In-Reply-To: <20200701125918.30793-1-benjamin.gaignard@st.com> On 7/1/20 2:59 PM, Benjamin Gaignard wrote: > This series allow to STM32 camera interface (DCMI) to require a minimum > frequency to the CPUs before start streaming frames from the sensor. > The minimum frequency requirement is provided in the devide-tree node. > > Setting a minimum frequency for the CPUs is needed to ensure a quick handling > of the interrupts between two sensor frames and avoid dropping half of them. Please forget this version, the incoming version 7 should have fix your remarks. Sorry, Benjamin > version 6: > - come back to version 4 and follow Valentin's suggestions about notifier > > version 5: > - add a mutex to protect dcmi_irq_notifier_notify() > - register notifier a probe time > > version 4: > - simplify irq affinity handling by using only dcmi_irq_notifier_notify() > > version 3: > - add a cpumask field to track boosted CPUs > - add irq_affinity_notify callback > - protect cpumask field with a mutex > > Benjamin Gaignard (3): > dt-bindings: media: stm32-dcmi: Add DCMI min frequency property > media: stm32-dcmi: Set minimum cpufreq requirement > ARM: dts: stm32: Set DCMI frequency requirement for stm32mp15x > > .../devicetree/bindings/media/st,stm32-dcmi.yaml | 8 ++ > arch/arm/boot/dts/stm32mp151.dtsi | 1 + > drivers/media/platform/stm32/stm32-dcmi.c | 138 +++++++++++++++++++-- > 3 files changed, 139 insertions(+), 8 deletions(-) >
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin GAIGNARD <benjamin.gaignard@st.com> To: Hugues FRUCHET <hugues.fruchet@st.com>, "mchehab@kernel.org" <mchehab@kernel.org>, "mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>, Alexandre TORGUE <alexandre.torgue@st.com>, "robh+dt@kernel.org" <robh+dt@kernel.org> Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "vincent.guittot@linaro.org" <vincent.guittot@linaro.org>, "rjw@rjwysocki.net" <rjw@rjwysocki.net>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-stm32@st-md-mailman.stormreply.com" <linux-stm32@st-md-mailman.stormreply.com>, "valentin.schneider@arm.com" <valentin.schneider@arm.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-media@vger.kernel.org" <linux-media@vger.kernel.org> Subject: Re: [PATCH v6 0/3] DCMI set minimum cpufreq requirement Date: Wed, 1 Jul 2020 13:02:45 +0000 [thread overview] Message-ID: <52850ead-3e49-7f24-e96b-3f6f293d54fe@st.com> (raw) In-Reply-To: <20200701125918.30793-1-benjamin.gaignard@st.com> On 7/1/20 2:59 PM, Benjamin Gaignard wrote: > This series allow to STM32 camera interface (DCMI) to require a minimum > frequency to the CPUs before start streaming frames from the sensor. > The minimum frequency requirement is provided in the devide-tree node. > > Setting a minimum frequency for the CPUs is needed to ensure a quick handling > of the interrupts between two sensor frames and avoid dropping half of them. Please forget this version, the incoming version 7 should have fix your remarks. Sorry, Benjamin > version 6: > - come back to version 4 and follow Valentin's suggestions about notifier > > version 5: > - add a mutex to protect dcmi_irq_notifier_notify() > - register notifier a probe time > > version 4: > - simplify irq affinity handling by using only dcmi_irq_notifier_notify() > > version 3: > - add a cpumask field to track boosted CPUs > - add irq_affinity_notify callback > - protect cpumask field with a mutex > > Benjamin Gaignard (3): > dt-bindings: media: stm32-dcmi: Add DCMI min frequency property > media: stm32-dcmi: Set minimum cpufreq requirement > ARM: dts: stm32: Set DCMI frequency requirement for stm32mp15x > > .../devicetree/bindings/media/st,stm32-dcmi.yaml | 8 ++ > arch/arm/boot/dts/stm32mp151.dtsi | 1 + > drivers/media/platform/stm32/stm32-dcmi.c | 138 +++++++++++++++++++-- > 3 files changed, 139 insertions(+), 8 deletions(-) > _______________________________________________ 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:[~2020-07-01 13:03 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-01 12:59 [PATCH v6 0/3] DCMI set minimum cpufreq requirement Benjamin Gaignard 2020-07-01 12:59 ` Benjamin Gaignard 2020-07-01 12:59 ` [PATCH v6 1/3] dt-bindings: media: stm32-dcmi: Add DCMI min frequency property Benjamin Gaignard 2020-07-01 12:59 ` Benjamin Gaignard 2020-07-01 12:59 ` [PATCH v6 2/3] media: stm32-dcmi: Set minimum cpufreq requirement Benjamin Gaignard 2020-07-01 12:59 ` Benjamin Gaignard 2020-07-01 12:59 ` [PATCH v6 3/3] ARM: dts: stm32: Set DCMI frequency requirement for stm32mp15x Benjamin Gaignard 2020-07-01 12:59 ` Benjamin Gaignard 2020-07-01 13:02 ` Benjamin GAIGNARD [this message] 2020-07-01 13:02 ` [PATCH v6 0/3] DCMI set minimum cpufreq requirement Benjamin GAIGNARD -- strict thread matches above, loose matches on Subject: below -- 2020-06-10 12:24 Benjamin Gaignard 2020-06-10 12:24 ` Benjamin Gaignard
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=52850ead-3e49-7f24-e96b-3f6f293d54fe@st.com \ --to=benjamin.gaignard@st.com \ --cc=alexandre.torgue@st.com \ --cc=devicetree@vger.kernel.org \ --cc=hugues.fruchet@st.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=linux-stm32@st-md-mailman.stormreply.com \ --cc=mchehab@kernel.org \ --cc=mcoquelin.stm32@gmail.com \ --cc=rjw@rjwysocki.net \ --cc=robh+dt@kernel.org \ --cc=valentin.schneider@arm.com \ --cc=vincent.guittot@linaro.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.