diff for duplicates of <87fumzehso.fsf@free-electrons.com> diff --git a/a/1.txt b/N1/1.txt index ac96195..0dccf54 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,23 +1,23 @@ Hi Thomas, - On jeu., nov. 10 2016, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote: + On jeu., nov. 10 2016, Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> wrote: [...] >> > A good example of why I'm worried is the sa-sram case: >> > ->> > + crypto_sram0: sa-sram0 at 0 { +>> > + crypto_sram0: sa-sram0@0 { >> > compatible = "mmio-sram"; >> > reg = <MBUS_ID(0x09, 0x09) 0 0x800>; >> > ->> > + crypto_sram1: sa-sram1 at 0 { +>> > + crypto_sram1: sa-sram1@0 { >> > compatible = "mmio-sram"; >> > reg = <MBUS_ID(0x09, 0x05) 0 0x800>; >> > >> > The node names should be just "sram" without a number. Indeed for UARTs ->> > for example, you use uart at XYZ, uart at ABC and not uart0 at XYZ and ->> > uart1 at ABC. But then, if you do that, with your scheme, you end up with ->> > both nodes named sa-sram at 0. +>> > for example, you use uart@XYZ, uart@ABC and not uart0@XYZ and +>> > uart1@ABC. But then, if you do that, with your scheme, you end up with +>> > both nodes named sa-sram@0. >> > >> > Which clearly shows that the way you set this unit-address is not >> > correct: those two devices are mapped at completely different @@ -30,12 +30,12 @@ Hi Thomas, >> concern. What I propose then is to expose the memory windows ID by >> adding the target and the attributes like this: >> ->> crypto_sram0: sa-sram at 09_09_0 { +>> crypto_sram0: sa-sram@09_09_0 { >> compatible = "mmio-sram"; >> reg = <MBUS_ID(0x09, 0x09) 0 0x800>; >> >> ->> crypto_sram1: sa-sram at 09_05_0 { +>> crypto_sram1: sa-sram@09_05_0 { >> compatible = "mmio-sram"; >> reg = <MBUS_ID(0x09, 0x05) 0 0x800>; > @@ -83,3 +83,7 @@ Gregory Clement, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com +-- +To unsubscribe from this list: send the line "unsubscribe devicetree" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 15a2052..2fbc696 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,32 +3,39 @@ "ref\020161110092221.0219490b@free-electrons.com\0" "ref\087wpgbekwg.fsf@free-electrons.com\0" "ref\020161110111506.02842cbd@free-electrons.com\0" - "From\0gregory.clement@free-electrons.com (Gregory CLEMENT)\0" - "Subject\0[PATCH 04/14] ARM: dts: armada-375: Fixup bootrom DT warning\0" + "ref\020161110111506.02842cbd-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org\0" + "From\0Gregory CLEMENT <gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>\0" + "Subject\0Re: [PATCH 04/14] ARM: dts: armada-375: Fixup bootrom DT warning\0" "Date\0Thu, 10 Nov 2016 11:43:51 +0100\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>\0" + "Cc\0Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>" + Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org> + Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> + linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org + Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> + " devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\0" "\00:1\0" "b\0" "Hi Thomas,\n" " \n" - " On jeu., nov. 10 2016, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:\n" + " On jeu., nov. 10 2016, Thomas Petazzoni <thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org> wrote:\n" "\n" "[...]\n" "\n" ">> > A good example of why I'm worried is the sa-sram case:\n" ">> >\n" - ">> > +\t\tcrypto_sram0: sa-sram0 at 0 {\n" + ">> > +\t\tcrypto_sram0: sa-sram0@0 {\n" ">> > \t\t\tcompatible = \"mmio-sram\";\n" ">> > \t\t\treg = <MBUS_ID(0x09, 0x09) 0 0x800>;\n" ">> >\n" - ">> > +\t\tcrypto_sram1: sa-sram1 at 0 {\n" + ">> > +\t\tcrypto_sram1: sa-sram1@0 {\n" ">> > \t\t\tcompatible = \"mmio-sram\";\n" ">> > \t\t\treg = <MBUS_ID(0x09, 0x05) 0 0x800>;\n" ">> >\n" ">> > The node names should be just \"sram\" without a number. Indeed for UARTs\n" - ">> > for example, you use uart at XYZ, uart at ABC and not uart0 at XYZ and\n" - ">> > uart1 at ABC. But then, if you do that, with your scheme, you end up with\n" - ">> > both nodes named sa-sram at 0.\n" + ">> > for example, you use uart@XYZ, uart@ABC and not uart0@XYZ and\n" + ">> > uart1@ABC. But then, if you do that, with your scheme, you end up with\n" + ">> > both nodes named sa-sram@0.\n" ">> >\n" ">> > Which clearly shows that the way you set this unit-address is not\n" ">> > correct: those two devices are mapped at completely different\n" @@ -41,12 +48,12 @@ ">> concern. What I propose then is to expose the memory windows ID by\n" ">> adding the target and the attributes like this:\n" ">> \n" - ">> \t\tcrypto_sram0: sa-sram at 09_09_0 {\n" + ">> \t\tcrypto_sram0: sa-sram@09_09_0 {\n" ">> \t\t\tcompatible = \"mmio-sram\";\n" ">> \t\t\treg = <MBUS_ID(0x09, 0x09) 0 0x800>;\n" ">> \n" ">> \n" - ">> \t\tcrypto_sram1: sa-sram at 09_05_0 {\n" + ">> \t\tcrypto_sram1: sa-sram@09_05_0 {\n" ">> \t\t\tcompatible = \"mmio-sram\";\n" ">> \t\t\treg = <MBUS_ID(0x09, 0x05) 0 0x800>;\n" ">\n" @@ -93,6 +100,10 @@ "Gregory Clement, Free Electrons\n" "Kernel, drivers, real-time and embedded Linux\n" "development, consulting, training and support.\n" - http://free-electrons.com + "http://free-electrons.com\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -56ec11d7f398c4fa572af5ac05819d42099a41b05c5c0c95840149c84d30406d +87ef417a94f57b81a5a2181d5bfaf4fb92a5a775e086a485ed457384f6cda3b7
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.