diff for duplicates of <878tgq5beu.fsf@codeaurora.org> diff --git a/a/1.txt b/N1/1.txt index 3223097..67900f1 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,26 +1,24 @@ Icenowy Zheng <icenowy@aosc.io> writes: -> =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=8D=88= -6:11:45, Maxime Ripard -> <maxime.ripard@free-electrons.com> =E5=86=99=E5=88=B0: +> ? 2017?10?4? GMT+08:00 ??6:11:45, Maxime Ripard +> <maxime.ripard@free-electrons.com> ??: >>On Wed, Oct 04, 2017 at 10:02:48AM +0000, Arend van Spriel wrote: >>> On 10/4/2017 11:03 AM, Icenowy Zheng wrote: ->>> >=20 ->>> >=20 ->>> > =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5= -=8D=885:02:17, Kalle Valo <kvalo@codeaurora.org> ->>=E5=86=99=E5=88=B0: +>>> > +>>> > +>>> > ? 2017?10?4? GMT+08:00 ??5:02:17, Kalle Valo <kvalo@codeaurora.org> +>>??: >>> > > Icenowy Zheng <icenowy@aosc.io> writes: ->>> > >=20 +>>> > > >>> > > > Allwinner XR819 is a SDIO Wi-Fi chip, which has the >>functionality to >>> > > use >>> > > > an out-of-band interrupt pin instead of SDIO in-band interrupt. ->>> > > >=20 +>>> > > > >>> > > > Add the device tree binding of this chip, in order to make it >>> > > possible >>> > > > to add this interrupt pin to device trees. ->>> > > >=20 +>>> > > > >>> > > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io> >>> > > > Acked-by: Rob Herring <robh@kernel.org> >>> > > > --- @@ -30,29 +28,29 @@ Icenowy Zheng <icenowy@aosc.io> writes: >>> > > > Changes in v2: >>> > > > - Removed status property in example. >>> > > > - Added required property reg. ->>> > > >=20 +>>> > > > >>> > > > .../bindings/net/wireless/allwinner,xr819.txt | 38 >>> > > ++++++++++++++++++++++ >>> > > > 1 file changed, 38 insertions(+) >>> > > > create mode 100644 >>> > > >>Documentation/devicetree/bindings/net/wireless/allwinner,xr819.txt ->>> > >=20 +>>> > > >>> > > Like I asked already last time, AFAICS there is no upstream xr819 >>> > > wireless driver in drivers/net/wireless directory. Do we still >>accept >>> > > bindings like this for out-of-tree drivers? ->>> >=20 +>>> > >>> > See esp8089. ->>> >=20 +>>> > >>> > There's also no in-tree driver for it. ->>>=20 +>>> >>> The question is whether we should. The above might be a precedent, >>but it >>> may not necessarily be the way to go. The commit message for esp8089 >>seems >>> to hint that there is intent to have an in-tree driver: ->>>=20 +>>> >>> """ >>> Note that at this point there only is an out of tree driver for >>this @@ -63,12 +61,12 @@ Icenowy Zheng <icenowy@aosc.io> writes: >>> now, so that any future migration to an in tree driver will not >>cause >>> compatiblity issues. ->>>=20 +>>> >>> Cc: Icenowy Zheng <icenowy@aosc.xyz> >>> Signed-off-by: Hans de Goede <hdegoede@redhat.com> >>> Signed-off-by: Rob Herring <robh@kernel.org> >>> """ ->>>=20 +>>> >>> Regardless the bindings are in principle independent of the kernel >>and just >>> describing hardware. I think there have been discussions to move the @@ -80,11 +78,11 @@ Icenowy Zheng <icenowy@aosc.io> writes: > > The cw1200 driver seems to still have some legacy platform > data. Maybe they should also be convert to DT. -> (Or maybe compatible =3D "allwinner,xr819" is enough, as +> (Or maybe compatible = "allwinner,xr819" is enough, as > xr819 is a specified variant of cw1200 family) Ah, so the upstream cw1200 driver supports xr819? Has anyone tested that? Or does cw1200 more changes than just adding the DT support? ---=20 +-- Kalle Valo diff --git a/a/content_digest b/N1/content_digest index b1943e7..e31aa0b 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,45 +5,33 @@ "ref\059D4B1C8.8020105@broadcom.com\0" "ref\020171004101145.kgjufpcktodppuy3@flea\0" "ref\0C4895259-FCDE-4B21-BB15-8F150FC53BE3@aosc.io\0" - "From\0Kalle Valo <kvalo@codeaurora.org>\0" - "Subject\0Re: [PATCH v3 1/2] dt-bindings: add device tree binding for Allwinner XR819 SDIO Wi-Fi\0" + "From\0kvalo@codeaurora.org (Kalle Valo)\0" + "Subject\0[PATCH v3 1/2] dt-bindings: add device tree binding for Allwinner XR819 SDIO Wi-Fi\0" "Date\0Thu, 05 Oct 2017 09:58:01 +0300\0" - "To\0Icenowy Zheng <icenowy@aosc.io>\0" - "Cc\0linux-arm-kernel@lists.infradead.org" - Maxime Ripard <maxime.ripard@free-electrons.com> - Arend van Spriel <arend.vanspriel@broadcom.com> - devicetree@vger.kernel.org - netdev@vger.kernel.org - linux-sunxi@googlegroups.com - linux-wireless@vger.kernel.org - linux-kernel@vger.kernel.org - Chen-Yu Tsai <wens@csie.org> - " Rob Herring <robh+dt@kernel.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Icenowy Zheng <icenowy@aosc.io> writes:\n" "\n" - "> =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=8D=88=\n" - "6:11:45, Maxime Ripard\n" - "> <maxime.ripard@free-electrons.com> =E5=86=99=E5=88=B0:\n" + "> ? 2017?10?4? GMT+08:00 ??6:11:45, Maxime Ripard\n" + "> <maxime.ripard@free-electrons.com> ??:\n" ">>On Wed, Oct 04, 2017 at 10:02:48AM +0000, Arend van Spriel wrote:\n" ">>> On 10/4/2017 11:03 AM, Icenowy Zheng wrote:\n" - ">>> >=20\n" - ">>> >=20\n" - ">>> > =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=\n" - "=8D=885:02:17, Kalle Valo <kvalo@codeaurora.org>\n" - ">>=E5=86=99=E5=88=B0:\n" + ">>> > \n" + ">>> > \n" + ">>> > ? 2017?10?4? GMT+08:00 ??5:02:17, Kalle Valo <kvalo@codeaurora.org>\n" + ">>??:\n" ">>> > > Icenowy Zheng <icenowy@aosc.io> writes:\n" - ">>> > >=20\n" + ">>> > > \n" ">>> > > > Allwinner XR819 is a SDIO Wi-Fi chip, which has the\n" ">>functionality to\n" ">>> > > use\n" ">>> > > > an out-of-band interrupt pin instead of SDIO in-band interrupt.\n" - ">>> > > >=20\n" + ">>> > > > \n" ">>> > > > Add the device tree binding of this chip, in order to make it\n" ">>> > > possible\n" ">>> > > > to add this interrupt pin to device trees.\n" - ">>> > > >=20\n" + ">>> > > > \n" ">>> > > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io>\n" ">>> > > > Acked-by: Rob Herring <robh@kernel.org>\n" ">>> > > > ---\n" @@ -53,29 +41,29 @@ ">>> > > > Changes in v2:\n" ">>> > > > - Removed status property in example.\n" ">>> > > > - Added required property reg.\n" - ">>> > > >=20\n" + ">>> > > > \n" ">>> > > > .../bindings/net/wireless/allwinner,xr819.txt | 38\n" ">>> > > ++++++++++++++++++++++\n" ">>> > > > 1 file changed, 38 insertions(+)\n" ">>> > > > create mode 100644\n" ">>> > >\n" ">>Documentation/devicetree/bindings/net/wireless/allwinner,xr819.txt\n" - ">>> > >=20\n" + ">>> > > \n" ">>> > > Like I asked already last time, AFAICS there is no upstream xr819\n" ">>> > > wireless driver in drivers/net/wireless directory. Do we still\n" ">>accept\n" ">>> > > bindings like this for out-of-tree drivers?\n" - ">>> >=20\n" + ">>> > \n" ">>> > See esp8089.\n" - ">>> >=20\n" + ">>> > \n" ">>> > There's also no in-tree driver for it.\n" - ">>>=20\n" + ">>> \n" ">>> The question is whether we should. The above might be a precedent,\n" ">>but it\n" ">>> may not necessarily be the way to go. The commit message for esp8089\n" ">>seems\n" ">>> to hint that there is intent to have an in-tree driver:\n" - ">>>=20\n" + ">>> \n" ">>> \"\"\"\n" ">>> Note that at this point there only is an out of tree driver for\n" ">>this\n" @@ -86,12 +74,12 @@ ">>> now, so that any future migration to an in tree driver will not\n" ">>cause\n" ">>> compatiblity issues.\n" - ">>>=20\n" + ">>> \n" ">>> Cc: Icenowy Zheng <icenowy@aosc.xyz>\n" ">>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>\n" ">>> Signed-off-by: Rob Herring <robh@kernel.org>\n" ">>> \"\"\"\n" - ">>>=20\n" + ">>> \n" ">>> Regardless the bindings are in principle independent of the kernel\n" ">>and just\n" ">>> describing hardware. I think there have been discussions to move the\n" @@ -103,13 +91,13 @@ ">\n" "> The cw1200 driver seems to still have some legacy platform\n" "> data. Maybe they should also be convert to DT.\n" - "> (Or maybe compatible =3D \"allwinner,xr819\" is enough, as\n" + "> (Or maybe compatible = \"allwinner,xr819\" is enough, as\n" "> xr819 is a specified variant of cw1200 family)\n" "\n" "Ah, so the upstream cw1200 driver supports xr819? Has anyone tested\n" "that? Or does cw1200 more changes than just adding the DT support?\n" "\n" - "--=20\n" + "-- \n" Kalle Valo -67463112159b6685bb1da2fc7d056f684ea4a1e0bf5dd42d80918835764bbf47 +bf84c4faa6f47a4aea4bb08ce9a5a5f392abb074e7227d3a2271259444c5c2c7
diff --git a/a/1.txt b/N2/1.txt index 3223097..d48cba5 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,28 +1,26 @@ -Icenowy Zheng <icenowy@aosc.io> writes: +Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org> writes: -> =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=8D=88= -6:11:45, Maxime Ripard -> <maxime.ripard@free-electrons.com> =E5=86=99=E5=88=B0: +> 于 2017年10月4日 GMT+08:00 下午6:11:45, Maxime Ripard +> <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> 写到: >>On Wed, Oct 04, 2017 at 10:02:48AM +0000, Arend van Spriel wrote: >>> On 10/4/2017 11:03 AM, Icenowy Zheng wrote: ->>> >=20 ->>> >=20 ->>> > =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5= -=8D=885:02:17, Kalle Valo <kvalo@codeaurora.org> ->>=E5=86=99=E5=88=B0: ->>> > > Icenowy Zheng <icenowy@aosc.io> writes: ->>> > >=20 +>>> > +>>> > +>>> > 于 2017年10月4日 GMT+08:00 下午5:02:17, Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> +>>写到: +>>> > > Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org> writes: +>>> > > >>> > > > Allwinner XR819 is a SDIO Wi-Fi chip, which has the >>functionality to >>> > > use >>> > > > an out-of-band interrupt pin instead of SDIO in-band interrupt. ->>> > > >=20 +>>> > > > >>> > > > Add the device tree binding of this chip, in order to make it >>> > > possible >>> > > > to add this interrupt pin to device trees. ->>> > > >=20 ->>> > > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io> ->>> > > > Acked-by: Rob Herring <robh@kernel.org> +>>> > > > +>>> > > > Signed-off-by: Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org> +>>> > > > Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> >>> > > > --- >>> > > > Changes in v3: >>> > > > - Renames the node name. @@ -30,29 +28,29 @@ Icenowy Zheng <icenowy@aosc.io> writes: >>> > > > Changes in v2: >>> > > > - Removed status property in example. >>> > > > - Added required property reg. ->>> > > >=20 +>>> > > > >>> > > > .../bindings/net/wireless/allwinner,xr819.txt | 38 >>> > > ++++++++++++++++++++++ >>> > > > 1 file changed, 38 insertions(+) >>> > > > create mode 100644 >>> > > >>Documentation/devicetree/bindings/net/wireless/allwinner,xr819.txt ->>> > >=20 +>>> > > >>> > > Like I asked already last time, AFAICS there is no upstream xr819 >>> > > wireless driver in drivers/net/wireless directory. Do we still >>accept >>> > > bindings like this for out-of-tree drivers? ->>> >=20 +>>> > >>> > See esp8089. ->>> >=20 +>>> > >>> > There's also no in-tree driver for it. ->>>=20 +>>> >>> The question is whether we should. The above might be a precedent, >>but it >>> may not necessarily be the way to go. The commit message for esp8089 >>seems >>> to hint that there is intent to have an in-tree driver: ->>>=20 +>>> >>> """ >>> Note that at this point there only is an out of tree driver for >>this @@ -63,12 +61,12 @@ Icenowy Zheng <icenowy@aosc.io> writes: >>> now, so that any future migration to an in tree driver will not >>cause >>> compatiblity issues. ->>>=20 ->>> Cc: Icenowy Zheng <icenowy@aosc.xyz> ->>> Signed-off-by: Hans de Goede <hdegoede@redhat.com> ->>> Signed-off-by: Rob Herring <robh@kernel.org> +>>> +>>> Cc: Icenowy Zheng <icenowy-ymACFijhrKM@public.gmane.org> +>>> Signed-off-by: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> +>>> Signed-off-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> >>> """ ->>>=20 +>>> >>> Regardless the bindings are in principle independent of the kernel >>and just >>> describing hardware. I think there have been discussions to move the @@ -80,11 +78,16 @@ Icenowy Zheng <icenowy@aosc.io> writes: > > The cw1200 driver seems to still have some legacy platform > data. Maybe they should also be convert to DT. -> (Or maybe compatible =3D "allwinner,xr819" is enough, as +> (Or maybe compatible = "allwinner,xr819" is enough, as > xr819 is a specified variant of cw1200 family) Ah, so the upstream cw1200 driver supports xr819? Has anyone tested that? Or does cw1200 more changes than just adding the DT support? ---=20 +-- Kalle Valo + +-- +You received this message because you are subscribed to the Google Groups "linux-sunxi" group. +To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org +For more options, visit https://groups.google.com/d/optout. diff --git a/a/content_digest b/N2/content_digest index b1943e7..99d4af7 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -5,47 +5,46 @@ "ref\059D4B1C8.8020105@broadcom.com\0" "ref\020171004101145.kgjufpcktodppuy3@flea\0" "ref\0C4895259-FCDE-4B21-BB15-8F150FC53BE3@aosc.io\0" - "From\0Kalle Valo <kvalo@codeaurora.org>\0" + "ref\0C4895259-FCDE-4B21-BB15-8F150FC53BE3-h8G6r0blFSE@public.gmane.org\0" + "From\0Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>\0" "Subject\0Re: [PATCH v3 1/2] dt-bindings: add device tree binding for Allwinner XR819 SDIO Wi-Fi\0" "Date\0Thu, 05 Oct 2017 09:58:01 +0300\0" - "To\0Icenowy Zheng <icenowy@aosc.io>\0" - "Cc\0linux-arm-kernel@lists.infradead.org" - Maxime Ripard <maxime.ripard@free-electrons.com> - Arend van Spriel <arend.vanspriel@broadcom.com> - devicetree@vger.kernel.org - netdev@vger.kernel.org - linux-sunxi@googlegroups.com - linux-wireless@vger.kernel.org - linux-kernel@vger.kernel.org - Chen-Yu Tsai <wens@csie.org> - " Rob Herring <robh+dt@kernel.org>\0" + "To\0Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org>\0" + "Cc\0linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" + Maxime Ripard <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> + Arend van Spriel <arend.vanspriel-dY08KVG/lbpWk0Htik3J/w@public.gmane.org> + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-sunxi-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org + linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org + Chen-Yu Tsai <wens-jdAy2FN1RRM@public.gmane.org> + " Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\0" "\00:1\0" "b\0" - "Icenowy Zheng <icenowy@aosc.io> writes:\n" + "Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org> writes:\n" "\n" - "> =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=8D=88=\n" - "6:11:45, Maxime Ripard\n" - "> <maxime.ripard@free-electrons.com> =E5=86=99=E5=88=B0:\n" + "> \344\272\216 2017\345\271\26410\346\234\2104\346\227\245 GMT+08:00 \344\270\213\345\215\2106:11:45, Maxime Ripard\n" + "> <maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> \345\206\231\345\210\260:\n" ">>On Wed, Oct 04, 2017 at 10:02:48AM +0000, Arend van Spriel wrote:\n" ">>> On 10/4/2017 11:03 AM, Icenowy Zheng wrote:\n" - ">>> >=20\n" - ">>> >=20\n" - ">>> > =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=\n" - "=8D=885:02:17, Kalle Valo <kvalo@codeaurora.org>\n" - ">>=E5=86=99=E5=88=B0:\n" - ">>> > > Icenowy Zheng <icenowy@aosc.io> writes:\n" - ">>> > >=20\n" + ">>> > \n" + ">>> > \n" + ">>> > \344\272\216 2017\345\271\26410\346\234\2104\346\227\245 GMT+08:00 \344\270\213\345\215\2105:02:17, Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>\n" + ">>\345\206\231\345\210\260:\n" + ">>> > > Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org> writes:\n" + ">>> > > \n" ">>> > > > Allwinner XR819 is a SDIO Wi-Fi chip, which has the\n" ">>functionality to\n" ">>> > > use\n" ">>> > > > an out-of-band interrupt pin instead of SDIO in-band interrupt.\n" - ">>> > > >=20\n" + ">>> > > > \n" ">>> > > > Add the device tree binding of this chip, in order to make it\n" ">>> > > possible\n" ">>> > > > to add this interrupt pin to device trees.\n" - ">>> > > >=20\n" - ">>> > > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io>\n" - ">>> > > > Acked-by: Rob Herring <robh@kernel.org>\n" + ">>> > > > \n" + ">>> > > > Signed-off-by: Icenowy Zheng <icenowy-h8G6r0blFSE@public.gmane.org>\n" + ">>> > > > Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\n" ">>> > > > ---\n" ">>> > > > Changes in v3:\n" ">>> > > > - Renames the node name.\n" @@ -53,29 +52,29 @@ ">>> > > > Changes in v2:\n" ">>> > > > - Removed status property in example.\n" ">>> > > > - Added required property reg.\n" - ">>> > > >=20\n" + ">>> > > > \n" ">>> > > > .../bindings/net/wireless/allwinner,xr819.txt | 38\n" ">>> > > ++++++++++++++++++++++\n" ">>> > > > 1 file changed, 38 insertions(+)\n" ">>> > > > create mode 100644\n" ">>> > >\n" ">>Documentation/devicetree/bindings/net/wireless/allwinner,xr819.txt\n" - ">>> > >=20\n" + ">>> > > \n" ">>> > > Like I asked already last time, AFAICS there is no upstream xr819\n" ">>> > > wireless driver in drivers/net/wireless directory. Do we still\n" ">>accept\n" ">>> > > bindings like this for out-of-tree drivers?\n" - ">>> >=20\n" + ">>> > \n" ">>> > See esp8089.\n" - ">>> >=20\n" + ">>> > \n" ">>> > There's also no in-tree driver for it.\n" - ">>>=20\n" + ">>> \n" ">>> The question is whether we should. The above might be a precedent,\n" ">>but it\n" ">>> may not necessarily be the way to go. The commit message for esp8089\n" ">>seems\n" ">>> to hint that there is intent to have an in-tree driver:\n" - ">>>=20\n" + ">>> \n" ">>> \"\"\"\n" ">>> Note that at this point there only is an out of tree driver for\n" ">>this\n" @@ -86,12 +85,12 @@ ">>> now, so that any future migration to an in tree driver will not\n" ">>cause\n" ">>> compatiblity issues.\n" - ">>>=20\n" - ">>> Cc: Icenowy Zheng <icenowy@aosc.xyz>\n" - ">>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>\n" - ">>> Signed-off-by: Rob Herring <robh@kernel.org>\n" + ">>> \n" + ">>> Cc: Icenowy Zheng <icenowy-ymACFijhrKM@public.gmane.org>\n" + ">>> Signed-off-by: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>\n" + ">>> Signed-off-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\n" ">>> \"\"\"\n" - ">>>=20\n" + ">>> \n" ">>> Regardless the bindings are in principle independent of the kernel\n" ">>and just\n" ">>> describing hardware. I think there have been discussions to move the\n" @@ -103,13 +102,18 @@ ">\n" "> The cw1200 driver seems to still have some legacy platform\n" "> data. Maybe they should also be convert to DT.\n" - "> (Or maybe compatible =3D \"allwinner,xr819\" is enough, as\n" + "> (Or maybe compatible = \"allwinner,xr819\" is enough, as\n" "> xr819 is a specified variant of cw1200 family)\n" "\n" "Ah, so the upstream cw1200 driver supports xr819? Has anyone tested\n" "that? Or does cw1200 more changes than just adding the DT support?\n" "\n" - "--=20\n" - Kalle Valo + "-- \n" + "Kalle Valo\n" + "\n" + "-- \n" + "You received this message because you are subscribed to the Google Groups \"linux-sunxi\" group.\n" + "To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org\n" + For more options, visit https://groups.google.com/d/optout. -67463112159b6685bb1da2fc7d056f684ea4a1e0bf5dd42d80918835764bbf47 +3fc82c23ad59459754acfc5297d1c261e52964865845e6d75a4ecaa82b2ac5cb
diff --git a/a/1.txt b/N3/1.txt index 3223097..f970867 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -1,26 +1,24 @@ Icenowy Zheng <icenowy@aosc.io> writes: -> =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=8D=88= -6:11:45, Maxime Ripard -> <maxime.ripard@free-electrons.com> =E5=86=99=E5=88=B0: +> 于 2017年10月4日 GMT+08:00 下午6:11:45, Maxime Ripard +> <maxime.ripard@free-electrons.com> 写到: >>On Wed, Oct 04, 2017 at 10:02:48AM +0000, Arend van Spriel wrote: >>> On 10/4/2017 11:03 AM, Icenowy Zheng wrote: ->>> >=20 ->>> >=20 ->>> > =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5= -=8D=885:02:17, Kalle Valo <kvalo@codeaurora.org> ->>=E5=86=99=E5=88=B0: +>>> > +>>> > +>>> > 于 2017年10月4日 GMT+08:00 下午5:02:17, Kalle Valo <kvalo@codeaurora.org> +>>写到: >>> > > Icenowy Zheng <icenowy@aosc.io> writes: ->>> > >=20 +>>> > > >>> > > > Allwinner XR819 is a SDIO Wi-Fi chip, which has the >>functionality to >>> > > use >>> > > > an out-of-band interrupt pin instead of SDIO in-band interrupt. ->>> > > >=20 +>>> > > > >>> > > > Add the device tree binding of this chip, in order to make it >>> > > possible >>> > > > to add this interrupt pin to device trees. ->>> > > >=20 +>>> > > > >>> > > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io> >>> > > > Acked-by: Rob Herring <robh@kernel.org> >>> > > > --- @@ -30,29 +28,29 @@ Icenowy Zheng <icenowy@aosc.io> writes: >>> > > > Changes in v2: >>> > > > - Removed status property in example. >>> > > > - Added required property reg. ->>> > > >=20 +>>> > > > >>> > > > .../bindings/net/wireless/allwinner,xr819.txt | 38 >>> > > ++++++++++++++++++++++ >>> > > > 1 file changed, 38 insertions(+) >>> > > > create mode 100644 >>> > > >>Documentation/devicetree/bindings/net/wireless/allwinner,xr819.txt ->>> > >=20 +>>> > > >>> > > Like I asked already last time, AFAICS there is no upstream xr819 >>> > > wireless driver in drivers/net/wireless directory. Do we still >>accept >>> > > bindings like this for out-of-tree drivers? ->>> >=20 +>>> > >>> > See esp8089. ->>> >=20 +>>> > >>> > There's also no in-tree driver for it. ->>>=20 +>>> >>> The question is whether we should. The above might be a precedent, >>but it >>> may not necessarily be the way to go. The commit message for esp8089 >>seems >>> to hint that there is intent to have an in-tree driver: ->>>=20 +>>> >>> """ >>> Note that at this point there only is an out of tree driver for >>this @@ -63,12 +61,12 @@ Icenowy Zheng <icenowy@aosc.io> writes: >>> now, so that any future migration to an in tree driver will not >>cause >>> compatiblity issues. ->>>=20 +>>> >>> Cc: Icenowy Zheng <icenowy@aosc.xyz> >>> Signed-off-by: Hans de Goede <hdegoede@redhat.com> >>> Signed-off-by: Rob Herring <robh@kernel.org> >>> """ ->>>=20 +>>> >>> Regardless the bindings are in principle independent of the kernel >>and just >>> describing hardware. I think there have been discussions to move the @@ -80,11 +78,11 @@ Icenowy Zheng <icenowy@aosc.io> writes: > > The cw1200 driver seems to still have some legacy platform > data. Maybe they should also be convert to DT. -> (Or maybe compatible =3D "allwinner,xr819" is enough, as +> (Or maybe compatible = "allwinner,xr819" is enough, as > xr819 is a specified variant of cw1200 family) Ah, so the upstream cw1200 driver supports xr819? Has anyone tested that? Or does cw1200 more changes than just adding the DT support? ---=20 +-- Kalle Valo diff --git a/a/content_digest b/N3/content_digest index b1943e7..1929c54 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -23,27 +23,25 @@ "b\0" "Icenowy Zheng <icenowy@aosc.io> writes:\n" "\n" - "> =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=8D=88=\n" - "6:11:45, Maxime Ripard\n" - "> <maxime.ripard@free-electrons.com> =E5=86=99=E5=88=B0:\n" + "> \344\272\216 2017\345\271\26410\346\234\2104\346\227\245 GMT+08:00 \344\270\213\345\215\2106:11:45, Maxime Ripard\n" + "> <maxime.ripard@free-electrons.com> \345\206\231\345\210\260:\n" ">>On Wed, Oct 04, 2017 at 10:02:48AM +0000, Arend van Spriel wrote:\n" ">>> On 10/4/2017 11:03 AM, Icenowy Zheng wrote:\n" - ">>> >=20\n" - ">>> >=20\n" - ">>> > =E4=BA=8E 2017=E5=B9=B410=E6=9C=884=E6=97=A5 GMT+08:00 =E4=B8=8B=E5=\n" - "=8D=885:02:17, Kalle Valo <kvalo@codeaurora.org>\n" - ">>=E5=86=99=E5=88=B0:\n" + ">>> > \n" + ">>> > \n" + ">>> > \344\272\216 2017\345\271\26410\346\234\2104\346\227\245 GMT+08:00 \344\270\213\345\215\2105:02:17, Kalle Valo <kvalo@codeaurora.org>\n" + ">>\345\206\231\345\210\260:\n" ">>> > > Icenowy Zheng <icenowy@aosc.io> writes:\n" - ">>> > >=20\n" + ">>> > > \n" ">>> > > > Allwinner XR819 is a SDIO Wi-Fi chip, which has the\n" ">>functionality to\n" ">>> > > use\n" ">>> > > > an out-of-band interrupt pin instead of SDIO in-band interrupt.\n" - ">>> > > >=20\n" + ">>> > > > \n" ">>> > > > Add the device tree binding of this chip, in order to make it\n" ">>> > > possible\n" ">>> > > > to add this interrupt pin to device trees.\n" - ">>> > > >=20\n" + ">>> > > > \n" ">>> > > > Signed-off-by: Icenowy Zheng <icenowy@aosc.io>\n" ">>> > > > Acked-by: Rob Herring <robh@kernel.org>\n" ">>> > > > ---\n" @@ -53,29 +51,29 @@ ">>> > > > Changes in v2:\n" ">>> > > > - Removed status property in example.\n" ">>> > > > - Added required property reg.\n" - ">>> > > >=20\n" + ">>> > > > \n" ">>> > > > .../bindings/net/wireless/allwinner,xr819.txt | 38\n" ">>> > > ++++++++++++++++++++++\n" ">>> > > > 1 file changed, 38 insertions(+)\n" ">>> > > > create mode 100644\n" ">>> > >\n" ">>Documentation/devicetree/bindings/net/wireless/allwinner,xr819.txt\n" - ">>> > >=20\n" + ">>> > > \n" ">>> > > Like I asked already last time, AFAICS there is no upstream xr819\n" ">>> > > wireless driver in drivers/net/wireless directory. Do we still\n" ">>accept\n" ">>> > > bindings like this for out-of-tree drivers?\n" - ">>> >=20\n" + ">>> > \n" ">>> > See esp8089.\n" - ">>> >=20\n" + ">>> > \n" ">>> > There's also no in-tree driver for it.\n" - ">>>=20\n" + ">>> \n" ">>> The question is whether we should. The above might be a precedent,\n" ">>but it\n" ">>> may not necessarily be the way to go. The commit message for esp8089\n" ">>seems\n" ">>> to hint that there is intent to have an in-tree driver:\n" - ">>>=20\n" + ">>> \n" ">>> \"\"\"\n" ">>> Note that at this point there only is an out of tree driver for\n" ">>this\n" @@ -86,12 +84,12 @@ ">>> now, so that any future migration to an in tree driver will not\n" ">>cause\n" ">>> compatiblity issues.\n" - ">>>=20\n" + ">>> \n" ">>> Cc: Icenowy Zheng <icenowy@aosc.xyz>\n" ">>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>\n" ">>> Signed-off-by: Rob Herring <robh@kernel.org>\n" ">>> \"\"\"\n" - ">>>=20\n" + ">>> \n" ">>> Regardless the bindings are in principle independent of the kernel\n" ">>and just\n" ">>> describing hardware. I think there have been discussions to move the\n" @@ -103,13 +101,13 @@ ">\n" "> The cw1200 driver seems to still have some legacy platform\n" "> data. Maybe they should also be convert to DT.\n" - "> (Or maybe compatible =3D \"allwinner,xr819\" is enough, as\n" + "> (Or maybe compatible = \"allwinner,xr819\" is enough, as\n" "> xr819 is a specified variant of cw1200 family)\n" "\n" "Ah, so the upstream cw1200 driver supports xr819? Has anyone tested\n" "that? Or does cw1200 more changes than just adding the DT support?\n" "\n" - "--=20\n" + "-- \n" Kalle Valo -67463112159b6685bb1da2fc7d056f684ea4a1e0bf5dd42d80918835764bbf47 +99a51d2c1888f4b5f74c8127ccc93b6b918e0bfe2fc4de6da7ff49bbe8daec98
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.