From: Stefan Wahren <stefan.wahren@i2se.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com
Cc: mbrugger@suse.de, viresh.kumar@linaro.org, rjw@rjwysocki.net,
sboyd@kernel.org, eric@anholt.net, ptesarik@suse.com,
linux-rpi-kernel@lists.infradead.org, ssuloev@orpaltech.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
mturquette@baylibre.com, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v2 4/5] dts: bcm2837: add per-cpu clock devices
Date: Mon, 20 May 2019 14:19:04 +0200 [thread overview]
Message-ID: <af50c1e9-5f52-e06b-8d0b-c9f72fba1324@i2se.com> (raw)
In-Reply-To: <20190520104708.11980-5-nsaenzjulienne@suse.de>
Hi Nicolas,
On 20.05.19 12:47, Nicolas Saenz Julienne wrote:
> The four CPUs share a same clock source called pllb_arm. The clock can
> be scaled through the raspberrypi firmware interface.
do you see a problem with applying this also to bcm2835.dtsi and
bcm2836.dtsi?
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
ptesarik@suse.com, sboyd@kernel.org, viresh.kumar@linaro.org,
mturquette@baylibre.com, linux-pm@vger.kernel.org,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org, eric@anholt.net,
linux-rpi-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
mbrugger@suse.de, ssuloev@orpaltech.com
Subject: Re: [RFC v2 4/5] dts: bcm2837: add per-cpu clock devices
Date: Mon, 20 May 2019 14:19:04 +0200 [thread overview]
Message-ID: <af50c1e9-5f52-e06b-8d0b-c9f72fba1324@i2se.com> (raw)
In-Reply-To: <20190520104708.11980-5-nsaenzjulienne@suse.de>
Hi Nicolas,
On 20.05.19 12:47, Nicolas Saenz Julienne wrote:
> The four CPUs share a same clock source called pllb_arm. The clock can
> be scaled through the raspberrypi firmware interface.
do you see a problem with applying this also to bcm2835.dtsi and
bcm2836.dtsi?
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
ptesarik@suse.com, sboyd@kernel.org, viresh.kumar@linaro.org,
mturquette@baylibre.com, linux-pm@vger.kernel.org,
rjw@rjwysocki.net, linux-kernel@vger.kernel.org, eric@anholt.net,
linux-rpi-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
mbrugger@suse.de, ssuloev@orpaltech.com
Subject: Re: [RFC v2 4/5] dts: bcm2837: add per-cpu clock devices
Date: Mon, 20 May 2019 14:19:04 +0200 [thread overview]
Message-ID: <af50c1e9-5f52-e06b-8d0b-c9f72fba1324@i2se.com> (raw)
In-Reply-To: <20190520104708.11980-5-nsaenzjulienne@suse.de>
Hi Nicolas,
On 20.05.19 12:47, Nicolas Saenz Julienne wrote:
> The four CPUs share a same clock source called pllb_arm. The clock can
> be scaled through the raspberrypi firmware interface.
do you see a problem with applying this also to bcm2835.dtsi and
bcm2836.dtsi?
_______________________________________________
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-05-20 12:19 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 10:47 [RFC v2 0/5] cpufreq support for the Raspberry Pi Nicolas Saenz Julienne
2019-05-20 10:47 ` Nicolas Saenz Julienne
2019-05-20 10:47 ` [RFC v2 1/5] clk: bcm2835: set CLK_GET_RATE_NOCACHE on CPU clocks Nicolas Saenz Julienne
2019-05-20 10:47 ` Nicolas Saenz Julienne
2019-05-20 11:42 ` Stefan Wahren
2019-05-20 11:42 ` Stefan Wahren
2019-05-20 10:47 ` [RFC v2 2/5] clk: bcm2835: set pllb_arm divisor as readonly Nicolas Saenz Julienne
2019-05-20 10:47 ` Nicolas Saenz Julienne
2019-05-20 11:43 ` Stefan Wahren
2019-05-20 11:43 ` Stefan Wahren
2019-05-20 10:47 ` [RFC v2 3/5] clk: bcm2835: use firmware interface to update pllb Nicolas Saenz Julienne
2019-05-20 10:47 ` Nicolas Saenz Julienne
2019-05-20 12:11 ` Stefan Wahren
2019-05-20 12:11 ` Stefan Wahren
2019-05-20 12:14 ` Stefan Wahren
2019-05-20 12:14 ` Stefan Wahren
2019-05-21 12:40 ` Stefan Wahren
2019-05-21 12:40 ` Stefan Wahren
2019-05-21 15:47 ` Nicolas Saenz Julienne
2019-05-21 15:47 ` Nicolas Saenz Julienne
2019-05-21 21:43 ` Stefan Wahren
2019-05-21 21:43 ` Stefan Wahren
2019-05-23 8:51 ` Nicolas Saenz Julienne
2019-05-23 8:51 ` Nicolas Saenz Julienne
2019-05-20 12:43 ` Oliver Neukum
2019-05-20 12:43 ` Oliver Neukum
2019-05-21 11:39 ` Nicolas Saenz Julienne
2019-05-21 11:39 ` Nicolas Saenz Julienne
2019-05-21 12:14 ` Petr Tesarik
2019-05-21 12:14 ` Petr Tesarik
2019-05-21 12:18 ` Nicolas Saenz Julienne
2019-05-21 12:18 ` Nicolas Saenz Julienne
2019-05-20 10:47 ` [RFC v2 4/5] dts: bcm2837: add per-cpu clock devices Nicolas Saenz Julienne
2019-05-20 10:47 ` Nicolas Saenz Julienne
2019-05-20 12:19 ` Stefan Wahren [this message]
2019-05-20 12:19 ` Stefan Wahren
2019-05-20 12:19 ` Stefan Wahren
2019-05-21 11:40 ` Nicolas Saenz Julienne
2019-05-21 11:40 ` Nicolas Saenz Julienne
2019-05-20 10:47 ` [RFC v2 5/5] cpufreq: add driver for Raspbery Pi Nicolas Saenz Julienne
2019-05-20 10:47 ` Nicolas Saenz Julienne
2019-05-20 10:51 ` Viresh Kumar
2019-05-20 10:51 ` Viresh Kumar
2019-05-20 12:30 ` Stefan Wahren
2019-05-20 12:30 ` Stefan Wahren
2019-05-20 10:51 ` [RFC v2 0/5] cpufreq support for the Raspberry Pi Viresh Kumar
2019-05-20 10:51 ` Viresh Kumar
2019-05-21 12:02 ` Nicolas Saenz Julienne
2019-05-21 12:02 ` Nicolas Saenz Julienne
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=af50c1e9-5f52-e06b-8d0b-c9f72fba1324@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mbrugger@suse.de \
--cc=mturquette@baylibre.com \
--cc=nsaenzjulienne@suse.de \
--cc=ptesarik@suse.com \
--cc=rjui@broadcom.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.com \
--cc=ssuloev@orpaltech.com \
--cc=viresh.kumar@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: link
Be 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.