devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Marek Behún" <kabel@kernel.org>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: leds: register-bit-led: Add active-low property
Date: Fri, 19 Aug 2022 10:42:22 +0200	[thread overview]
Message-ID: <20220819084222.ru4olyfntunlm3f3@pali> (raw)
In-Reply-To: <ae1c301a-60e4-5112-6681-8896a7479207@linaro.org>

On Friday 19 August 2022 11:38:29 Krzysztof Kozlowski wrote:
> On 19/08/2022 11:08, Pavel Machek wrote:
> > Hi!
> > 
> >>> Although the question is - where is the user of it?
> >>
> >> I was planning to send updated powerpc DTS files with these
> >> register-bit-led definitions after accepting dt bindings.
> > 
> > We need device tree people to ack them, first. But a note saying "this
> > is for Turris Omnia router" would be welcome.
> 
> In general the process is one of:
> 1. Send DT bindings with driver and DTS changes,
> 2. Send DT bindings with driver in one patchset, DTS in second but you
> mention the dependency.
> 
> You should not wait with DTS till bindings got accepted. Why? Because
> for example we do not want bindings for stuff which never is going to be
> upstreamed (with several exceptions, e.g. for other systems). Also
> because we want to be able to compare bindings with your DTS
> implementing them, so we are sure you described everything (especially
> that you said running one command to install dtchema and second command
> to make the check is not possible in your system).
> 
> Without DTS here how can anyone be sure your DTS actually follows the
> bindings?
> 
> Best regards,
> Krzysztof

Well, last time I was told that first needs to be accepted bindings
documentation and then device tree files. So I did it like this. And now
it is again feasible and different steps and ordering is needed...
Sorry I cannot known all requirements which are moreover changing every
day.

  reply	other threads:[~2022-08-19  8:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 17:25 [PATCH 1/2] dt-bindings: leds: register-bit-led: Add active-low property Pali Rohár
2022-08-18 17:25 ` [PATCH 2/2] leds: syscon: Implement support for " Pali Rohár
2022-08-26  8:05   ` Linus Walleij
2022-08-31 11:49     ` Pali Rohár
2022-10-09 11:40       ` Pali Rohár
2022-11-01 22:32         ` Pali Rohár
2022-11-08 12:42           ` Linus Walleij
2022-08-19  6:46 ` [PATCH 1/2] dt-bindings: leds: register-bit-led: Add " Krzysztof Kozlowski
2022-08-19  6:56   ` Pali Rohár
2022-08-19  8:08     ` Pavel Machek
2022-08-19  8:38       ` Krzysztof Kozlowski
2022-08-19  8:42         ` Pali Rohár [this message]
2022-08-19  9:08           ` Krzysztof Kozlowski
2022-08-19  9:11           ` Pali Rohár
2022-08-19  8:35 ` Linus Walleij

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=20220819084222.ru4olyfntunlm3f3@pali \
    --to=pali@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kabel@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@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: 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).