From: Kalle Valo <kvalo@codeaurora.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: brcm80211-dev-list.pdl@broadcom.com,
Franky Lin <franky.lin@broadcom.com>,
linux-wireless@vger.kernel.org,
Chi-Hsien Lin <chi-hsien.lin@cypress.com>,
Wright Feng <wright.feng@cypress.com>,
brcm80211-dev-list@cypress.com,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Simon Shields <simon@lineageos.org>,
Hante Meuleman <hante.meuleman@broadcom.com>
Subject: Re: [PATCH] brcmfmac: add support for external 32khz clock
Date: Wed, 08 Nov 2017 02:30:37 +0200 [thread overview]
Message-ID: <87r2t9ipci.fsf@codeaurora.org> (raw)
In-Reply-To: <964084973.5481.1510037571344@email.1und1.de> (Stefan Wahren's message of "Tue, 7 Nov 2017 07:52:51 +0100 (CET)")
Stefan Wahren <stefan.wahren@i2se.com> writes:
> Hi,
>
>> Kalle Valo <kvalo@codeaurora.org> hat am 7. November 2017 um 03:18 geschrieben:
>>
>>
>> Stefan Wahren <stefan.wahren@i2se.com> writes:
>>
>> >> Simon Shields <simon@lineageos.org> hat am 4. November 2017 um 14:24 geschrieben:
>> >>
>> >>
>> >> Some boards use an external 32khz clock for low-power
>> >> mode timing. Make sure the clock is powered on while the chipset
>> >> is active.
>> >>
>> >> Signed-off-by: Simon Shields <simon@lineageos.org>
>> >> ---
>> >> .../devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt | 2 ++
>> >> drivers/net/wireless/broadcom/brcm80211/brcmfmac/common.h | 2 ++
>> >> drivers/net/wireless/broadcom/brcm80211/brcmfmac/of.c | 5 +++++
>> >> drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c | 10 ++++++++++
>> >> 4 files changed, 19 insertions(+)
>> >>
>> >> diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
>> >> index b2bd4704f859..37add5e29272 100644
>> >> --- a/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
>> >> +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm43xx-fmac.txt
>> >> @@ -17,6 +17,8 @@ Optional properties:
>> >> When not specified the device will use in-band SDIO interrupts.
>> >> - interrupt-names : name of the out-of-band interrupt, which must be set
>> >> to "host-wake".
>> >> + - clocks : external 32khz clock
>> >> + - clock-names : name of the external 32khz clock, must be "32khz"
>> >
>> > sorry for the nitpicking, but according to the datasheet [1] it's
>> > 32768 Hz. Apart from that i suggest to use a functional name for the
>> > clock like "low_power" or something else, which is more flexible and
>> > future-proof.
>> >
>> > Btw this binding needs to be a separate patch, which should go to the
>> > devicetree guys.
>>
>> Previously I have applied binding documentation changes which the DT
>> maintainers have acked, that's why I specifically asked to Cc device
>> tree list. Has something changed?
>
> as long as the changes has been acked this should be okay. I was
> referring to point 1 in this guideline [1].
>
> [1] -
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/submitting-patches.txt?h=v4.14-rc8
Ah, that's a good point. Splitting the patch does make sense.
--
Kalle Valo
next prev parent reply other threads:[~2017-11-08 0:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 13:24 [PATCH] brcmfmac: add support for external 32khz clock Simon Shields
2017-11-06 9:42 ` Kalle Valo
2017-11-06 10:59 ` Arend van Spriel
2017-11-06 11:27 ` Simon Shields
2017-11-07 11:09 ` Arend van Spriel
2017-11-07 13:31 ` Simon Shields
2017-11-08 10:38 ` Arend van Spriel
2017-11-08 11:43 ` Simon Shields
2017-11-08 13:31 ` Simon Shields
2017-11-06 18:34 ` Stefan Wahren
2017-11-07 2:18 ` Kalle Valo
2017-11-07 6:52 ` Stefan Wahren
2017-11-07 9:01 ` Arend van Spriel
2017-11-08 0:30 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-06 10:29 Simon Shields
2017-11-06 10:43 ` Kalle Valo
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=87r2t9ipci.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=simon@lineageos.org \
--cc=stefan.wahren@i2se.com \
--cc=wright.feng@cypress.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).