From: Eric Anholt <eric@anholt.net>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
stefan.wahren@i2se.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, 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,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] clk: bcm2835: register Raspberry Pi's firmware clk device
Date: Tue, 04 Jun 2019 17:00:51 -0700 [thread overview]
Message-ID: <87muiwzyrw.fsf@anholt.net> (raw)
In-Reply-To: <20190604173223.4229-4-nsaenzjulienne@suse.de>
[-- Attachment #1: Type: text/plain, Size: 410 bytes --]
Nicolas Saenz Julienne <nsaenzjulienne@suse.de> writes:
> Registers clk-raspberrypi as a platform device as part of the driver's
> probe sequence.
Similar to how we have VCHI register platform devices for the services
VCHI provides, shouldn't we have the firmware driver register the device
for clk_raspberrypi? Or put the clk provider in the fw driver instead
of a separate driver (no opinion on my part).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric Anholt <eric@anholt.net>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
stefan.wahren@i2se.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, 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,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
linux-rpi-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
mbrugger@suse.de, ssuloev@orpaltech.com
Subject: Re: [PATCH 3/4] clk: bcm2835: register Raspberry Pi's firmware clk device
Date: Tue, 04 Jun 2019 17:00:51 -0700 [thread overview]
Message-ID: <87muiwzyrw.fsf@anholt.net> (raw)
In-Reply-To: <20190604173223.4229-4-nsaenzjulienne@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 410 bytes --]
Nicolas Saenz Julienne <nsaenzjulienne@suse.de> writes:
> Registers clk-raspberrypi as a platform device as part of the driver's
> probe sequence.
Similar to how we have VCHI register platform devices for the services
VCHI provides, shouldn't we have the firmware driver register the device
for clk_raspberrypi? Or put the clk provider in the fw driver instead
of a separate driver (no opinion on my part).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-06-05 0:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 17:32 [PATCH 0/4] cpufreq support for the Raspberry Pi Nicolas Saenz Julienne
2019-06-04 17:32 ` Nicolas Saenz Julienne
2019-06-04 17:32 ` [PATCH 1/4] clk: bcm2835: remove pllb Nicolas Saenz Julienne
2019-06-04 17:32 ` Nicolas Saenz Julienne
2019-06-05 0:03 ` Eric Anholt
2019-06-05 0:03 ` Eric Anholt
2019-06-05 10:49 ` Stefan Wahren
2019-06-05 10:49 ` Stefan Wahren
2019-06-04 17:32 ` [PATCH 2/4] clk: bcm283x: add driver interfacing with Raspberry Pi's firmware Nicolas Saenz Julienne
2019-06-04 17:32 ` Nicolas Saenz Julienne
2019-06-05 10:44 ` Stefan Wahren
2019-06-05 10:44 ` Stefan Wahren
2019-06-05 12:23 ` Nicolas Saenz Julienne
2019-06-05 12:23 ` Nicolas Saenz Julienne
2019-06-04 17:32 ` [PATCH 3/4] clk: bcm2835: register Raspberry Pi's firmware clk device Nicolas Saenz Julienne
2019-06-04 17:32 ` Nicolas Saenz Julienne
2019-06-05 0:00 ` Eric Anholt [this message]
2019-06-05 0:00 ` Eric Anholt
2019-06-05 9:11 ` Nicolas Saenz Julienne
2019-06-05 9:11 ` Nicolas Saenz Julienne
2019-06-05 10:01 ` Stefan Wahren
2019-06-05 10:01 ` Stefan Wahren
2019-06-04 17:32 ` [PATCH 4/4] cpufreq: add driver for Raspbery Pi Nicolas Saenz Julienne
2019-06-04 17:32 ` Nicolas Saenz Julienne
2019-06-05 0:18 ` Eric Anholt
2019-06-05 0:18 ` Eric Anholt
2019-06-05 9:12 ` Nicolas Saenz Julienne
2019-06-05 9:12 ` Nicolas Saenz Julienne
2019-06-05 11:15 ` Stefan Wahren
2019-06-05 11:15 ` Stefan Wahren
2019-06-05 9:46 ` [PATCH 0/4] cpufreq support for the Raspberry Pi Stefan Wahren
2019-06-05 9:46 ` Stefan Wahren
2019-06-05 11:00 ` Nicolas Saenz Julienne
2019-06-05 11:00 ` Nicolas Saenz Julienne
2019-06-05 11:34 ` Stefan Wahren
2019-06-05 11:34 ` Stefan Wahren
2019-06-05 12:27 ` Nicolas Saenz Julienne
2019-06-05 12:27 ` Nicolas Saenz Julienne
2019-06-05 13:12 ` Stefan Wahren
2019-06-05 13:12 ` Stefan Wahren
2019-06-05 19:11 ` Nicolas Saenz Julienne
2019-06-05 19:11 ` Nicolas Saenz Julienne
2019-06-05 20:15 ` Stefan Wahren
2019-06-05 20:15 ` Stefan Wahren
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=87muiwzyrw.fsf@anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--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=mbrugger@suse.de \
--cc=mturquette@baylibre.com \
--cc=nsaenzjulienne@suse.de \
--cc=ptesarik@suse.com \
--cc=rjui@broadcom.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.com \
--cc=ssuloev@orpaltech.com \
--cc=stefan.wahren@i2se.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.