From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>
Cc: Johan Jonker <jbx6244@gmail.com>,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
jay.xu@rock-chips.com, shawn.lin@rock-chips.com,
david.wu@rock-chips.com, zhangqing@rock-chips.com,
huangtao@rock-chips.com, cl@rock-chips.com,
linux-gpio@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: gpio: convert rk3328-grf-gpio.txt to YAML
Date: Fri, 07 May 2021 23:06:33 +0200 [thread overview]
Message-ID: <3540274.MHq7AAxBmi@phil> (raw)
In-Reply-To: <20210507210239.GA2875797@robh.at.kernel.org>
Am Freitag, 7. Mai 2021, 23:02:39 CEST schrieb Rob Herring:
> On Fri, May 07, 2021 at 10:59:09PM +0200, Heiko Stuebner wrote:
> > Hi Bartosz,
> >
> > Am Mittwoch, 5. Mai 2021, 15:40:25 CEST schrieb Johan Jonker:
> > > Current dts files with RK3328 GRF 'gpio' nodes are manually verified.
> > > In order to automate this process rk3328-grf-gpio.txt has to be
> > > converted to YAML.
> > >
> > > Rename 'grf-gpio' nodename to 'gpio'.
> > >
> > > Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> >
> > just to not step on any toes, do you plan to apply this patch1 later on?
> > Patches 2-4 are in my domain so I'll get them after -rc1, but in theory
> > the gpio binding should go through the gpio tree.
>
> Different trees will break the schema checks because the grf schema
> refers to the gpio schema.
Ah, thanks for the heads up.
I guess we need to agree on one then.
Bartosz, gpio tree or the rockchip tree for patches 1+2? ;-)
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>
Cc: Johan Jonker <jbx6244@gmail.com>,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
jay.xu@rock-chips.com, shawn.lin@rock-chips.com,
david.wu@rock-chips.com, zhangqing@rock-chips.com,
huangtao@rock-chips.com, cl@rock-chips.com,
linux-gpio@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: gpio: convert rk3328-grf-gpio.txt to YAML
Date: Fri, 07 May 2021 23:06:33 +0200 [thread overview]
Message-ID: <3540274.MHq7AAxBmi@phil> (raw)
In-Reply-To: <20210507210239.GA2875797@robh.at.kernel.org>
Am Freitag, 7. Mai 2021, 23:02:39 CEST schrieb Rob Herring:
> On Fri, May 07, 2021 at 10:59:09PM +0200, Heiko Stuebner wrote:
> > Hi Bartosz,
> >
> > Am Mittwoch, 5. Mai 2021, 15:40:25 CEST schrieb Johan Jonker:
> > > Current dts files with RK3328 GRF 'gpio' nodes are manually verified.
> > > In order to automate this process rk3328-grf-gpio.txt has to be
> > > converted to YAML.
> > >
> > > Rename 'grf-gpio' nodename to 'gpio'.
> > >
> > > Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> >
> > just to not step on any toes, do you plan to apply this patch1 later on?
> > Patches 2-4 are in my domain so I'll get them after -rc1, but in theory
> > the gpio binding should go through the gpio tree.
>
> Different trees will break the schema checks because the grf schema
> refers to the gpio schema.
Ah, thanks for the heads up.
I guess we need to agree on one then.
Bartosz, gpio tree or the rockchip tree for patches 1+2? ;-)
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh@kernel.org>
Cc: Johan Jonker <jbx6244@gmail.com>,
linus.walleij@linaro.org, bgolaszewski@baylibre.com,
jay.xu@rock-chips.com, shawn.lin@rock-chips.com,
david.wu@rock-chips.com, zhangqing@rock-chips.com,
huangtao@rock-chips.com, cl@rock-chips.com,
linux-gpio@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: gpio: convert rk3328-grf-gpio.txt to YAML
Date: Fri, 07 May 2021 23:06:33 +0200 [thread overview]
Message-ID: <3540274.MHq7AAxBmi@phil> (raw)
In-Reply-To: <20210507210239.GA2875797@robh.at.kernel.org>
Am Freitag, 7. Mai 2021, 23:02:39 CEST schrieb Rob Herring:
> On Fri, May 07, 2021 at 10:59:09PM +0200, Heiko Stuebner wrote:
> > Hi Bartosz,
> >
> > Am Mittwoch, 5. Mai 2021, 15:40:25 CEST schrieb Johan Jonker:
> > > Current dts files with RK3328 GRF 'gpio' nodes are manually verified.
> > > In order to automate this process rk3328-grf-gpio.txt has to be
> > > converted to YAML.
> > >
> > > Rename 'grf-gpio' nodename to 'gpio'.
> > >
> > > Signed-off-by: Johan Jonker <jbx6244@gmail.com>
> >
> > just to not step on any toes, do you plan to apply this patch1 later on?
> > Patches 2-4 are in my domain so I'll get them after -rc1, but in theory
> > the gpio binding should go through the gpio tree.
>
> Different trees will break the schema checks because the grf schema
> refers to the gpio schema.
Ah, thanks for the heads up.
I guess we need to agree on one then.
Bartosz, gpio tree or the rockchip tree for patches 1+2? ;-)
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-07 21:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 13:40 [PATCH v2 0/4] convert grf.txt to YAML Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-05 13:40 ` [PATCH v2 1/4] dt-bindings: gpio: convert rk3328-grf-gpio.txt " Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-07 20:48 ` Rob Herring
2021-05-07 20:48 ` Rob Herring
2021-05-07 20:48 ` Rob Herring
2021-05-07 20:59 ` Heiko Stuebner
2021-05-07 20:59 ` Heiko Stuebner
2021-05-07 20:59 ` Heiko Stuebner
2021-05-07 21:02 ` Rob Herring
2021-05-07 21:02 ` Rob Herring
2021-05-07 21:02 ` Rob Herring
2021-05-07 21:06 ` Heiko Stuebner [this message]
2021-05-07 21:06 ` Heiko Stuebner
2021-05-07 21:06 ` Heiko Stuebner
2021-05-07 21:26 ` Linus Walleij
2021-05-07 21:26 ` Linus Walleij
2021-05-07 21:26 ` Linus Walleij
2021-05-05 13:40 ` [PATCH v2 2/4] dt-bindings: soc: rockchip: convert grf.txt " Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-07 20:47 ` Rob Herring
2021-05-07 20:47 ` Rob Herring
2021-05-07 20:47 ` Rob Herring
2021-05-05 13:40 ` [PATCH v2 3/4] ARM: dts: rockchip: add grf register compatible for rk3066/rk3188 Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-05 13:40 ` [PATCH v2 4/4] arm64: dts: rename grf-gpio nodename in rk3328.dtsi Johan Jonker
2021-05-05 13:40 ` Johan Jonker
2021-05-05 13:40 ` Johan Jonker
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=3540274.MHq7AAxBmi@phil \
--to=heiko@sntech.de \
--cc=bgolaszewski@baylibre.com \
--cc=cl@rock-chips.com \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=jbx6244@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=zhangqing@rock-chips.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: 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.