All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] kbuild: take into account DT_SCHEMA_FILES changes while checking dtbs
Date: Fri, 29 Jul 2022 16:03:43 +0900	[thread overview]
Message-ID: <CAK7LNAQU42fpqPqUipZYx+685B+Rc8JGdaKcP3TdfQWUept1nQ@mail.gmail.com> (raw)
In-Reply-To: <CAA8EJprM4WAgfVTJ15azFtSH6POL5uuseHO=zVxRd44RmqKZjw@mail.gmail.com>

On Fri, Jul 29, 2022 at 3:53 PM Dmitry Baryshkov
<dmitry.baryshkov@linaro.org> wrote:
>
> On Fri, 29 Jul 2022 at 08:55, Masahiro Yamada <masahiroy@kernel.org> wrote:
> >
> > On Thu, Jul 28, 2022 at 2:36 AM Rob Herring <robh+dt@kernel.org> wrote:
> > >
> > > On Wed, Jul 27, 2022 at 4:06 AM Dmitry Baryshkov
> > > <dmitry.baryshkov@linaro.org> wrote:
> > > >
> > > > It is useful to be able to recheck dtbs files against a limited set of
> > > > DT schema files. This can be accomplished by using differnt
> > > > DT_SCHEMA_FILES argument values while rerunning make dtbs_check. However
> > > > for some reason if_changed_rule doesn't pick up the rule_dtc changes
> > > > (and doesn't retrigger the build).
> > > >
> > > > Fix this by changing if_changed_rule to if_changed_dep and squashing DTC
> > > > and dt-validate into a single new command. Then if_changed_dep triggers
> > > > on DT_SCHEMA_FILES changes and reruns the build/check.
> > > >
> > > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > > > ---
> > > >  scripts/Makefile.lib | 14 ++++++--------
> > > >  1 file changed, 6 insertions(+), 8 deletions(-)
> > > >
> > > > diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
> > > > index c88b98b5dc44..3df470289382 100644
> > > > --- a/scripts/Makefile.lib
> > > > +++ b/scripts/Makefile.lib
> > > > @@ -383,17 +383,15 @@ DT_CHECKER_FLAGS ?= $(if $(DT_SCHEMA_FILES),-l $(DT_SCHEMA_FILES),-m)
> > > >  DT_BINDING_DIR := Documentation/devicetree/bindings
> > > >  DT_TMP_SCHEMA := $(objtree)/$(DT_BINDING_DIR)/processed-schema.json
> > > >
> > > > -quiet_cmd_dtb_check =  CHECK   $@
> > > > -      cmd_dtb_check =  $(DT_CHECKER) $(DT_CHECKER_FLAGS) -u $(srctree)/$(DT_BINDING_DIR) -p $(DT_TMP_SCHEMA) $@ || true
> > > > +quiet_cmd_dtb =        DTC/CHECK   $@
> > >
> > > This is supposed to be 7 chars or less. DTCCHK or DTC_CHK perhaps. Or
> > > always do just 'DTC'. I can fixup when applying.
> > >
> > > I'll give it a few days for other comments.
> >
> >
> >
> > When you change DT_SCHEMA_FILES, re-running dt-validate should be enough.
> > You do not need to re-run dtc.
> >
> > I guess the strangeness comes from the fact that you are trying to do the
> >  two different things in a single rule.
>
> The issue is that with the current rules the dt-validate isn't
> re-executed on DT_SCHEMA_FILES changes. Thus comes my proposal.

Correct.



What I said is like this.



# touch the timestamp file, %.dtb.checked
$(obj)/%.dtb.checked: $(obj)/%.dtb $(DT_TMP_SCHEMA) FORCE
        $(call if_changed_rule,dtb_check)

$(obj)/%.dtb: $(src)/%.dts $(DTC) $FORCE
        $(call if_changed_rule,dtc)

$(obj)/%.dtbo: $(src)/%.dts $(DTC) FORCE
        $(call if_changed_dep,dtc)


With the dtc/check split, we can avoid unneeded regeneration of
%.dtb when DT_TMP_SCHEMA or DT_SCHEMA_FILES is
changed.


One drawback is we track %.dtb.checked and and %.dtb separately,
so something like 53182e81f47d4ea0c727c49ad23cb782173ab849
may come back.






BTW, we do not check %.dtbo, why?

At least, 53182e81f47d4ea0c727c49ad23cb782173ab849
was trying to check %.dtbo




> --
> With best wishes
> Dmitry



-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2022-07-29  7:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 10:06 [PATCH] kbuild: take into account DT_SCHEMA_FILES changes while checking dtbs Dmitry Baryshkov
2022-07-27 17:36 ` Rob Herring
2022-07-29  5:54   ` Masahiro Yamada
2022-07-29  6:52     ` Dmitry Baryshkov
2022-07-29  7:03       ` Masahiro Yamada [this message]
2022-07-29  7:46         ` Dmitry Baryshkov
2022-08-04 15:27           ` Rob Herring
2022-09-10 17:35             ` Dmitry Baryshkov
2022-09-15  4:50               ` Masahiro Yamada
2022-09-15 11:40                 ` Dmitry Baryshkov
2022-09-16  1:09                   ` Masahiro Yamada
2022-09-16 14:21                     ` Dmitry Baryshkov
2022-09-16 14:54                       ` Rob Herring
2022-09-16 19:37                         ` Dmitry Baryshkov

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=CAK7LNAQU42fpqPqUipZYx+685B+Rc8JGdaKcP3TdfQWUept1nQ@mail.gmail.com \
    --to=masahiroy@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=ndesaulniers@google.com \
    --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 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.