From: Sjoerd Simons <sjoerd.simons@collabora.co.uk> To: Geert Uytterhoeven <geert@linux-m68k.org> Cc: Geert Uytterhoeven <geert+renesas@glider.be>, Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>, Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>, Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Wolfram Sang <wsa@sang-engineering.com>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>, Linux-Renesas <linux-renesas-soc@vger.kernel.org>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Daniel Stone <daniels@collabora.com>, Kevin Hilman <khilman@baylibre.com> Subject: Re: [PATCH/RFC v2 0/2] arm64: dts: r8a7795: Add support for R-Car H3 ES2.0 Date: Thu, 30 Mar 2017 13:50:25 +0200 [thread overview] Message-ID: <1490874625.3471.6.camel@collabora.co.uk> (raw) In-Reply-To: <CAMuHMdV+=pNpFO7H3J0=JM1BnXtm4t=Q+1bx=R+f9=JxvJZT_Q@mail.gmail.com> On Thu, 2017-03-30 at 13:13 +0200, Geert Uytterhoeven wrote: > Hi Sjoerd, > > On Thu, Mar 30, 2017 at 12:48 PM, Sjoerd Simons > <sjoerd.simons@collabora.co.uk> wrote: > > On Fri, 2017-03-24 at 14:37 +0100, Geert Uytterhoeven wrote: > > > This patch series adds preliminary support for Renesas Salvator-X > > > development boards equipped with revision ES2.0 of the R-Car H3 > > > Soc. > > > > > > - Patch 1 adds support for the R-Car H3 ES2.0 Soc, > > > While this patch is safe as-is, as it doesn't affect any > > > existing > > > setups, it's probably a bit premature to apply it. > > > - Patch 2 adds support for Salvator-X boards with R-Car H3 > > > ES2.0. > > > This patch does affect existing development setups, as it > > > changes > > > the > > > name of the DTB for Salvator-X boards equipped with ES1.x > > > SoCs. > > > Given most developers have access to ES1.x only, this patch > > > must > > > not be > > > applied yet. > > > > Would it make more sense to add a new r8a7795-es2.dtsi and keep the > > current dtsi for es1? Having to load different device-trees based > > on > > which kernel is used would be rather nasty. > > We definitely considered that option. > However, we concluded that in the end, we want to mainly support > production > SoCs. Hence the default files should represent the production > version. > Using a preproduction SoC can be considered a special case, and thus > needs > a file with a special esX ID in its name. The problem is that even though they are pre-production, these are out there and in active use, e.g. kernelci is at least doing automated testing on one of those in Kevins lab and should be an additional soonish in the Collabora lab. And for developers it'll be extra fun if halfway through a bisect the dts name changes.. Having a es2 in your dtb name might be a bit quirky, but it's really just a name without other meaning :). > We do realize this can cause some inconveniences during the > transition period, > when most developers don't have access to ES2.0 SoCs yet, or have > mixed > environments of ES1.x and ES2.0. Heh yeah, i'd expect we'd have a mixed environment for quite a while given these boards are a bit too expensive to just throw in the trash.. > Of course you can keep on using the current DTB (binary) on your H3 > ES1.x > boards, as long as you don't need to use devices not yet described in > that DTB. > > Thanks! > > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linu > x-m68k.org > > In personal conversations with technical people, I call myself a > hacker. But > when I'm talking to journalists I just say "programmer" or something > like that. > -- Linus Torvalds -- Sjoerd Simons Collabora Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: sjoerd.simons@collabora.co.uk (Sjoerd Simons) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH/RFC v2 0/2] arm64: dts: r8a7795: Add support for R-Car H3 ES2.0 Date: Thu, 30 Mar 2017 13:50:25 +0200 [thread overview] Message-ID: <1490874625.3471.6.camel@collabora.co.uk> (raw) In-Reply-To: <CAMuHMdV+=pNpFO7H3J0=JM1BnXtm4t=Q+1bx=R+f9=JxvJZT_Q@mail.gmail.com> On Thu, 2017-03-30 at 13:13 +0200, Geert Uytterhoeven wrote: > Hi Sjoerd, > > On Thu, Mar 30, 2017 at 12:48 PM, Sjoerd Simons > <sjoerd.simons@collabora.co.uk> wrote: > > On Fri, 2017-03-24 at 14:37 +0100, Geert Uytterhoeven wrote: > > > This patch series adds preliminary support for Renesas Salvator-X > > > development boards equipped with revision ES2.0 of the R-Car H3 > > > Soc. > > > > > > ? - Patch 1 adds support for the R-Car H3 ES2.0 Soc, > > > ????While this patch is safe as-is, as it doesn't affect any > > > existing > > > ????setups, it's probably a bit premature to apply it. > > > ? - Patch 2 adds support for Salvator-X boards with R-Car H3 > > > ES2.0. > > > ????This patch does affect existing development setups, as it > > > changes > > > the > > > ????name of the DTB for Salvator-X boards equipped with ES1.x > > > SoCs. > > > ????Given most developers have access to ES1.x only, this patch > > > must > > > not be > > > ????applied yet. > > > > Would it make more sense to add a new r8a7795-es2.dtsi and keep the > > current dtsi for es1? Having to load different device-trees based > > on > > which kernel is used would be rather nasty. > > We definitely considered that option. > However, we concluded that in the end, we want to mainly support > production > SoCs.??Hence the default files should represent the production > version. > Using a preproduction SoC can be considered a special case, and thus > needs > a file with a special esX ID in its name. The problem is that even though they are pre-production, these are out there and in active use, e.g. kernelci is at least doing automated testing on one of those in Kevins lab and should be an additional soonish in the Collabora lab.? And for developers it'll be extra fun if halfway through a bisect the dts name changes.. Having a es2 in your dtb name might be a bit quirky, but it's really just a name without other meaning :). > We do realize this can cause some inconveniences during the > transition period, > when most developers don't have access to ES2.0 SoCs yet, or have > mixed > environments of ES1.x and ES2.0. Heh yeah, i'd expect we'd have a mixed environment for quite a while given these boards are a bit too expensive to just throw in the trash.. > Of course you can keep on using the current DTB (binary) on your H3 > ES1.x > boards, as long as you don't need to use devices not yet described in > that DTB. > > Thanks! > > Gr{oetje,eeting}s, > > ????????????????????????Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linu > x-m68k.org > > In personal conversations with technical people, I call myself a > hacker. But > when I'm talking to journalists I just say "programmer" or something > like that. > ????????????????????????????????-- Linus Torvalds -- Sjoerd Simons Collabora Ltd.
next prev parent reply other threads:[~2017-03-30 11:50 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-24 13:37 [PATCH/RFC v2 0/2] arm64: dts: r8a7795: Add support for R-Car H3 ES2.0 Geert Uytterhoeven 2017-03-24 13:37 ` Geert Uytterhoeven [not found] ` <1490362665-4422-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org> 2017-03-24 13:37 ` [PATCH/RFC v2 1/2] " Geert Uytterhoeven 2017-03-24 13:37 ` Geert Uytterhoeven 2017-03-27 8:48 ` Laurent Pinchart 2017-03-27 8:48 ` Laurent Pinchart 2017-03-29 8:13 ` Simon Horman 2017-03-29 8:13 ` Simon Horman 2017-03-29 8:31 ` Geert Uytterhoeven 2017-03-29 8:31 ` Geert Uytterhoeven 2017-03-29 8:45 ` Simon Horman 2017-03-29 8:45 ` Simon Horman 2017-04-20 9:36 ` Geert Uytterhoeven 2017-04-20 9:36 ` Geert Uytterhoeven 2017-04-20 10:42 ` Laurent Pinchart 2017-04-20 10:42 ` Laurent Pinchart 2017-04-20 10:55 ` Geert Uytterhoeven 2017-04-20 10:55 ` Geert Uytterhoeven 2017-04-20 10:55 ` Geert Uytterhoeven [not found] ` <CAMuHMdWmvhZjxKfEdGJ3d_w0d2s2kK+8iW1tsEM584qZc+dVEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2017-04-20 11:24 ` Laurent Pinchart 2017-04-20 11:24 ` Laurent Pinchart 2017-04-20 11:24 ` Laurent Pinchart 2017-04-20 11:36 ` Geert Uytterhoeven 2017-04-20 11:36 ` Geert Uytterhoeven 2017-03-24 13:37 ` [PATCH/RFC v2 2/2] arm64: dts: r8a7795: salvator-x: " Geert Uytterhoeven 2017-03-24 13:37 ` Geert Uytterhoeven 2017-03-24 13:37 ` Geert Uytterhoeven 2017-03-30 10:48 ` [PATCH/RFC v2 0/2] arm64: dts: r8a7795: " Sjoerd Simons 2017-03-30 10:48 ` Sjoerd Simons 2017-03-30 10:48 ` Sjoerd Simons [not found] ` <1490870898.3471.3.camel-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org> 2017-03-30 11:13 ` Geert Uytterhoeven 2017-03-30 11:13 ` Geert Uytterhoeven 2017-03-30 11:13 ` Geert Uytterhoeven 2017-03-30 11:50 ` Sjoerd Simons [this message] 2017-03-30 11:50 ` Sjoerd Simons 2017-03-30 12:08 ` Geert Uytterhoeven 2017-03-30 12:08 ` 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=1490874625.3471.6.camel@collabora.co.uk \ --to=sjoerd.simons@collabora.co.uk \ --cc=daniels@collabora.com \ --cc=devicetree@vger.kernel.org \ --cc=geert+renesas@glider.be \ --cc=geert@linux-m68k.org \ --cc=horms@verge.net.au \ --cc=khilman@baylibre.com \ --cc=kuninori.morimoto.gx@renesas.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=magnus.damm@gmail.com \ --cc=mark.rutland@arm.com \ --cc=robh+dt@kernel.org \ --cc=wsa@sang-engineering.com \ --cc=yoshihiro.shimoda.uh@renesas.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: 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.