From: Conor Dooley <conor@kernel.org> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Cc: Conor Dooley <conor.dooley@microchip.com>, Hal Feng <hal.feng@starfivetech.com>, linux-riscv@lists.infradead.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, Palmer Dabbelt <palmer@dabbelt.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Stephen Boyd <sboyd@kernel.org>, Michael Turquette <mturquette@baylibre.com>, Philipp Zabel <p.zabel@pengutronix.de>, Emil Renner Berthing <emil.renner.berthing@canonical.com>, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 07/11] dt-bindings: clock: Add StarFive JH7110 system clock and reset generator Date: Sat, 18 Feb 2023 15:08:28 +0000 [thread overview] Message-ID: <Y/Dp7OSNIAL39DSV@spud> (raw) In-Reply-To: <a3217699-7b23-35e6-84b2-fe9e52158481@linaro.org> [-- Attachment #1: Type: text/plain, Size: 3333 bytes --] On Sat, Feb 18, 2023 at 03:55:25PM +0100, Krzysztof Kozlowski wrote: > On 18/02/2023 12:17, Conor Dooley wrote: > > On Sat, Feb 18, 2023 at 11:20:30AM +0100, Krzysztof Kozlowski wrote: > >>>> That's a long thread, please summarize what you ask. Otherwise I have no > >>>> clue what is the question. > >>> > >>> Sorry. I tried to preserve the context of the conversation the last time > >>> I cropped it so that things would be contained on one email. > >>> > >>> For me at least, I am wondering how you convey that out of a list of > >>> clock inputs (for example a, b, c, d) that two of the clocks are inputs > >>> to a mux and it is only required to provide one of the two (say b & c). > > > > You skipped this part which was what I was trying to ask you about. > > Yeah, I skipped a lot because there was one big thread with a question: > what do you think? Sorry, I will not dig 8 emails thread to figure out > which question is to me and which is not... This was in the cut-down message & a fake scenario to avoid you needing to understand the full thread. I kept the context originally so that you would not have to dig out the thread & provided the fake scenario this time for this very reason. > > Do you know how to convey this situation, or is it even possible to > > express those rules? > > oneOf: > - clock-names: > minItems: 3 > items: > - a > - b > - c > - d > - clock-names: > items: > - a > - b > - d > > or maybe: > - clock-names: > minItems: 3 > items: > - a > - b > - enum: [c, d] > - d Thanks for the suggestions. Without actually going and playing with it, the first of those two looks like it may be the right fit for this situation, depending on what Hal says the hardware can do. > >>>> Does the mux works correctly if clock input is not connected? I mean, > >>>> are you now talking about real hardware or some simplification from SW > >>>> point of view? > >>> > >>> I'm coming at this from an angle of "is a StarFive customer going to show > >>> up with a devicetree containing dummy fixed-clocks to satisfy dtbs_check > >>> because they opted to only populate one input to the mux". > >>> I don't really care about implications for the driver, just about > >>> whether the hardware allows for inputs to the mux to be left > >>> un-populated. > >> > >> Whether hardware allows - not a question to me. > > > >> BTW, this is rather question coming from me... > > > > I don't understand what you mean by this, sorry. > > You said to a letter addressed to me "whether the hardware allows for > ...". Why would you ask me about hardware I know nothing about? That was > my question - I am asking - whether hardware allows it or not. Then > write bindings depending on that. There was no question here, instead it was an answer to this question of yours: > I mean, > are you now talking about real hardware or some simplification from SW > point of view? In which I was saying I cared about the "real hardware". For obvious reasons, I wouldn't ask you to explain whether the hardware is capable of it or not! Perhaps your original question here was misunderstood. Thanks for the suggestions, Conor. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org> To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Cc: Conor Dooley <conor.dooley@microchip.com>, Hal Feng <hal.feng@starfivetech.com>, linux-riscv@lists.infradead.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, Palmer Dabbelt <palmer@dabbelt.com>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Stephen Boyd <sboyd@kernel.org>, Michael Turquette <mturquette@baylibre.com>, Philipp Zabel <p.zabel@pengutronix.de>, Emil Renner Berthing <emil.renner.berthing@canonical.com>, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 07/11] dt-bindings: clock: Add StarFive JH7110 system clock and reset generator Date: Sat, 18 Feb 2023 15:08:28 +0000 [thread overview] Message-ID: <Y/Dp7OSNIAL39DSV@spud> (raw) In-Reply-To: <a3217699-7b23-35e6-84b2-fe9e52158481@linaro.org> [-- Attachment #1.1: Type: text/plain, Size: 3333 bytes --] On Sat, Feb 18, 2023 at 03:55:25PM +0100, Krzysztof Kozlowski wrote: > On 18/02/2023 12:17, Conor Dooley wrote: > > On Sat, Feb 18, 2023 at 11:20:30AM +0100, Krzysztof Kozlowski wrote: > >>>> That's a long thread, please summarize what you ask. Otherwise I have no > >>>> clue what is the question. > >>> > >>> Sorry. I tried to preserve the context of the conversation the last time > >>> I cropped it so that things would be contained on one email. > >>> > >>> For me at least, I am wondering how you convey that out of a list of > >>> clock inputs (for example a, b, c, d) that two of the clocks are inputs > >>> to a mux and it is only required to provide one of the two (say b & c). > > > > You skipped this part which was what I was trying to ask you about. > > Yeah, I skipped a lot because there was one big thread with a question: > what do you think? Sorry, I will not dig 8 emails thread to figure out > which question is to me and which is not... This was in the cut-down message & a fake scenario to avoid you needing to understand the full thread. I kept the context originally so that you would not have to dig out the thread & provided the fake scenario this time for this very reason. > > Do you know how to convey this situation, or is it even possible to > > express those rules? > > oneOf: > - clock-names: > minItems: 3 > items: > - a > - b > - c > - d > - clock-names: > items: > - a > - b > - d > > or maybe: > - clock-names: > minItems: 3 > items: > - a > - b > - enum: [c, d] > - d Thanks for the suggestions. Without actually going and playing with it, the first of those two looks like it may be the right fit for this situation, depending on what Hal says the hardware can do. > >>>> Does the mux works correctly if clock input is not connected? I mean, > >>>> are you now talking about real hardware or some simplification from SW > >>>> point of view? > >>> > >>> I'm coming at this from an angle of "is a StarFive customer going to show > >>> up with a devicetree containing dummy fixed-clocks to satisfy dtbs_check > >>> because they opted to only populate one input to the mux". > >>> I don't really care about implications for the driver, just about > >>> whether the hardware allows for inputs to the mux to be left > >>> un-populated. > >> > >> Whether hardware allows - not a question to me. > > > >> BTW, this is rather question coming from me... > > > > I don't understand what you mean by this, sorry. > > You said to a letter addressed to me "whether the hardware allows for > ...". Why would you ask me about hardware I know nothing about? That was > my question - I am asking - whether hardware allows it or not. Then > write bindings depending on that. There was no question here, instead it was an answer to this question of yours: > I mean, > are you now talking about real hardware or some simplification from SW > point of view? In which I was saying I cared about the "real hardware". For obvious reasons, I wouldn't ask you to explain whether the hardware is capable of it or not! Perhaps your original question here was misunderstood. Thanks for the suggestions, Conor. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 228 bytes --] [-- Attachment #2: Type: text/plain, Size: 161 bytes --] _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-02-18 15:08 UTC|newest] Thread overview: 120+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-20 0:50 [PATCH v3 00/11] Basic clock and reset support for StarFive JH7110 RISC-V SoC Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 0:50 ` [PATCH v3 01/11] clk: starfive: Factor out common JH7100 and JH7110 code Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 21:54 ` Conor Dooley 2022-12-20 21:54 ` Conor Dooley 2022-12-20 0:50 ` [PATCH v3 02/11] clk: starfive: Rename "jh7100" to "jh71x0" for the common code Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 22:08 ` Conor Dooley 2022-12-20 22:08 ` Conor Dooley 2022-12-23 6:23 ` Hal Feng 2022-12-23 6:23 ` Hal Feng 2022-12-20 0:50 ` [PATCH v3 03/11] reset: Create subdirectory for StarFive drivers Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 22:15 ` Conor Dooley 2022-12-20 22:15 ` Conor Dooley 2022-12-23 7:02 ` Hal Feng 2022-12-23 7:02 ` Hal Feng 2022-12-20 0:50 ` [PATCH v3 04/11] reset: starfive: Factor out common JH71X0 reset code Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 22:28 ` Conor Dooley 2022-12-20 22:28 ` Conor Dooley 2022-12-23 7:49 ` Hal Feng 2022-12-23 7:49 ` Hal Feng 2022-12-20 0:50 ` [PATCH v3 05/11] reset: starfive: Rename "jh7100" to "jh71x0" for the common code Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 2:40 ` kernel test robot 2022-12-20 2:40 ` kernel test robot 2022-12-20 22:31 ` Conor Dooley 2022-12-20 22:31 ` Conor Dooley 2022-12-24 3:48 ` kernel test robot 2022-12-24 3:48 ` kernel test robot 2022-12-20 0:50 ` [PATCH v3 06/11] reset: starfive: jh71x0: Use 32bit I/O on 32bit registers Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 22:49 ` Conor Dooley 2022-12-20 22:49 ` Conor Dooley 2022-12-20 0:50 ` [PATCH v3 07/11] dt-bindings: clock: Add StarFive JH7110 system clock and reset generator Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 20:12 ` Rob Herring 2022-12-20 20:12 ` Rob Herring 2022-12-20 23:14 ` Conor Dooley 2022-12-20 23:14 ` Conor Dooley 2022-12-20 23:16 ` Conor Dooley 2022-12-20 23:16 ` Conor Dooley 2022-12-25 16:26 ` Hal Feng 2022-12-25 16:26 ` Hal Feng 2022-12-27 20:15 ` Conor Dooley 2022-12-27 20:15 ` Conor Dooley 2023-02-16 14:42 ` Hal Feng 2023-02-16 14:42 ` Hal Feng 2023-02-16 18:20 ` Conor Dooley 2023-02-16 18:20 ` Conor Dooley 2023-02-17 2:27 ` Hal Feng 2023-02-17 2:27 ` Hal Feng 2023-02-17 7:51 ` Conor Dooley 2023-02-17 7:51 ` Conor Dooley 2023-02-17 12:20 ` Hal Feng 2023-02-17 12:20 ` Hal Feng 2023-02-17 13:32 ` Conor Dooley 2023-02-17 13:32 ` Conor Dooley 2023-02-17 15:47 ` Krzysztof Kozlowski 2023-02-17 15:47 ` Krzysztof Kozlowski 2023-02-17 16:27 ` Conor Dooley 2023-02-17 16:27 ` Conor Dooley 2023-02-18 10:20 ` Krzysztof Kozlowski 2023-02-18 10:20 ` Krzysztof Kozlowski 2023-02-18 11:17 ` Conor Dooley 2023-02-18 11:17 ` Conor Dooley 2023-02-18 14:55 ` Krzysztof Kozlowski 2023-02-18 14:55 ` Krzysztof Kozlowski 2023-02-18 15:08 ` Conor Dooley [this message] 2023-02-18 15:08 ` Conor Dooley 2023-02-21 22:17 ` Stephen Boyd 2023-02-21 22:17 ` Stephen Boyd 2023-02-21 23:39 ` Conor Dooley 2023-02-21 23:39 ` Conor Dooley 2023-02-22 13:27 ` Hal Feng 2023-02-22 13:27 ` Hal Feng 2023-02-22 16:26 ` Conor Dooley 2023-02-22 16:26 ` Conor Dooley 2023-02-23 3:03 ` Hal Feng 2023-02-23 3:03 ` Hal Feng 2023-02-23 6:18 ` Conor Dooley 2023-02-23 6:18 ` Conor Dooley 2023-02-23 9:52 ` Hal Feng 2023-02-23 9:52 ` Hal Feng 2022-12-20 0:50 ` [PATCH v3 08/11] dt-bindings: clock: Add StarFive JH7110 always-on " Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 20:14 ` Rob Herring 2022-12-20 20:14 ` Rob Herring 2022-12-20 23:19 ` Conor Dooley 2022-12-20 23:19 ` Conor Dooley 2023-02-16 17:19 ` Hal Feng 2023-02-16 17:19 ` Hal Feng 2022-12-20 0:50 ` [PATCH v3 09/11] clk: starfive: Add StarFive JH7110 system clock driver Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-23 9:57 ` kernel test robot 2022-12-23 9:57 ` kernel test robot 2023-01-05 11:32 ` kernel test robot 2023-01-05 11:32 ` kernel test robot 2023-02-19 21:23 ` Emil Renner Berthing 2023-02-19 21:23 ` Emil Renner Berthing 2023-02-21 6:44 ` Hal Feng 2023-02-21 6:44 ` Hal Feng 2022-12-20 0:50 ` [PATCH v3 10/11] clk: starfive: Add StarFive JH7110 always-on " Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-23 11:28 ` kernel test robot 2022-12-23 11:28 ` kernel test robot 2023-01-05 13:44 ` kernel test robot 2023-01-05 13:44 ` kernel test robot 2022-12-20 0:50 ` [PATCH v3 11/11] reset: starfive: Add StarFive JH7110 reset driver Hal Feng 2022-12-20 0:50 ` Hal Feng 2022-12-20 7:14 ` kernel test robot 2022-12-20 7:14 ` kernel test robot 2022-12-23 12:39 ` kernel test robot 2022-12-23 12:39 ` kernel test robot 2022-12-27 19:20 ` kernel test robot 2022-12-27 19:20 ` kernel test robot 2023-01-05 15:35 ` kernel test robot 2023-01-05 15:35 ` kernel test robot
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=Y/Dp7OSNIAL39DSV@spud \ --to=conor@kernel.org \ --cc=conor.dooley@microchip.com \ --cc=devicetree@vger.kernel.org \ --cc=emil.renner.berthing@canonical.com \ --cc=hal.feng@starfivetech.com \ --cc=krzysztof.kozlowski+dt@linaro.org \ --cc=krzysztof.kozlowski@linaro.org \ --cc=linux-clk@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=mturquette@baylibre.com \ --cc=p.zabel@pengutronix.de \ --cc=palmer@dabbelt.com \ --cc=robh+dt@kernel.org \ --cc=sboyd@kernel.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.