LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Atish Patra <atishp@atishpatra.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Bin Meng <bmeng.cn@gmail.com>,
	Drew Fustini <drew@beagleboard.org>,
	Rob Herring <robh+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	michael.zhu@starfivetech.com, Wei Fu <tekkamanninja@gmail.com>,
	jack.zhu@starfivetech.com, leyfoon.tan@starfivetech.com,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Emil Renner Berhing <kernel@esmil.dk>,
	devicetree <devicetree@vger.kernel.org>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	"linux-kernel@vger.kernel.org List"
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] dt-bindings: riscv: add starfive jh7100 bindings
Date: Wed, 4 Aug 2021 13:54:16 -0700	[thread overview]
Message-ID: <CAOnJCUL9uU5G1LOgfYPz9Ny77yFYaP5sgtdxG3_w=Zcsi+f96Q@mail.gmail.com> (raw)
In-Reply-To: <mhng-a2fd6094-0ae8-4f7b-9dee-fd71b85b29f1@palmerdabbelt-glaptop>

On Wed, Aug 4, 2021 at 1:33 PM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> On Thu, 15 Jul 2021 19:17:23 PDT (-0700), bmeng.cn@gmail.com wrote:
> > On Tue, Jul 13, 2021 at 2:34 PM Drew Fustini <drew@beagleboard.org> wrote:
> >>
> >> Add DT binding documentation for the StarFive JH7100 Soc [1] and the
> >> BeagleV Starlight JH7100 board [2].
> >>
> >> [1] https://github.com/starfive-tech/beaglev_doc
> >> [2] https://github.com/beagleboard/beaglev-starlight
> >>
> >> Signed-off-by: Drew Fustini <drew@beagleboard.org>
> >> ---
> >> v4 changes:
> >> - removed JH7100 SoC revision number after discussion with Geert
> >>
> >> v3 changes:
> >> - added revision number for the board and soc after question from Palmer
> >>
> >> v2 changes:
> >> - removed "items:" entry that only had "const: starfive,jh7100"
> >> - correct typo in Description:
> >>
> >> Results of running checks:
> >>   $ make -j8 ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- dt_binding_check \
> >>     DT_SCHEMA_FILES=Documentation/devicetree/bindings/riscv/starfive.yaml
> >>     CHKDT   Documentation/devicetree/bindings/processed-schema-examples.json
> >>     DTEX    Documentation/devicetree/bindings/riscv/starfive.example.dts
> >>     SCHEMA  Documentation/devicetree/bindings/processed-schema-examples.json
> >>     DTC     Documentation/devicetree/bindings/riscv/starfive.example.dt.yaml
> >>     CHECK   Documentation/devicetree/bindings/riscv/starfive.example.dt.yaml
> >>   $ make -j8 ARCH=riscv CROSS_COMPILE=riscv64-linux-gnu- dtbs_check \
> >>     DT_SCHEMA_FILES=Documentation/devicetree/bindings/riscv/starfive.yaml
> >>     SYNC    include/config/auto.conf.cmd
> >>     UPD     include/config/kernel.release
> >>     SCHEMA  Documentation/devicetree/bindings/processed-schema.json
> >>     DTC     arch/riscv/boot/dts/starfive/jh7100-beaglev-starlight.dtb
> >>     DTC     arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dt.yaml
> >>     DTC     arch/riscv/boot/dts/starfive/jh7100-beaglev-starlight.dt.yaml
> >>     DTC     arch/riscv/boot/dts/sifive/hifive-unmatched-a00.dt.yaml
> >>     CHECK   arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dt.yaml
> >>     CHECK   arch/riscv/boot/dts/sifive/hifive-unmatched-a00.dt.yaml
> >>     CHECK   arch/riscv/boot/dts/starfive/jh7100-beaglev-starlight.dt.yaml
> >>
> >> The dts file is from vendor repo and is being cleaned up right now in
> >> preperation for submitting to the mailing list:
> >> https://github.com/starfive-tech/linux/tree/beaglev/arch/riscv/boot/dts/starfive
> >>
> >>  .../devicetree/bindings/riscv/starfive.yaml   | 27 +++++++++++++++++++
> >>  1 file changed, 27 insertions(+)
> >>  create mode 100644 Documentation/devicetree/bindings/riscv/starfive.yaml
> >>
> >
> > Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
>
> Thanks.  This is on for-next, as Rob suggested taking it via the RISC-V
> tree.
>
Given that beagleV starlight mass production is cancelled [1], are we
still upstreaming the support for this ?

[1] https://www.cnx-software.com/2021/07/31/beaglev-starlight-sbc-wont-be-mass-manufactured-redesigned-beaglev-risc-v-sbc-expected-in-q1-2022/
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv



-- 
Regards,
Atish

  reply	other threads:[~2021-08-04 20:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13  6:30 Drew Fustini
2021-07-15 17:12 ` Rob Herring
2021-07-16  2:17 ` Bin Meng
2021-08-04 20:33   ` Palmer Dabbelt
2021-08-04 20:54     ` Atish Patra [this message]
2021-08-04 21:13       ` Palmer Dabbelt
2021-08-05  2:30         ` Drew Fustini
2021-08-05  8:13           ` Andreas Schwab
2021-08-05  8:13           ` Emil Renner Berthing
2021-08-05 18:09             ` Atish Patra
2021-08-05 18:28               ` Drew Fustini
2021-08-09 10:59               ` Geert Uytterhoeven

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='CAOnJCUL9uU5G1LOgfYPz9Ny77yFYaP5sgtdxG3_w=Zcsi+f96Q@mail.gmail.com' \
    --to=atishp@atishpatra.org \
    --cc=bmeng.cn@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drew@beagleboard.org \
    --cc=geert@linux-m68k.org \
    --cc=jack.zhu@starfivetech.com \
    --cc=kernel@esmil.dk \
    --cc=leyfoon.tan@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michael.zhu@starfivetech.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=tekkamanninja@gmail.com \
    --subject='Re: [PATCH v4] dt-bindings: riscv: add starfive jh7100 bindings' \
    /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

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).