diff for duplicates of <87aa1621yv.fsf@ti.com> diff --git a/a/1.txt b/N1/1.txt index bce3156..29f510a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -18,18 +18,18 @@ >>> is fixed in SAR ROM. SAR is split into 4 banks with different >>> privilege accesses based on device type >>> ->>> --------------------------------------------------------------- ->>> Access mode Bank Address Range ->>> --------------------------------------------------------------- ->>> HS/GP : Public 1 0x4A32_6000 - 0x4A32_6FFF (4kB) ->>> HS/GP : Public 2 0x4A32_7000 - 0x4A32_73FF (1kB) +>>> ?--------------------------------------------------------------- +>>> ?Access mode ? ? ? ? ?Bank ? ?Address Range +>>> ?--------------------------------------------------------------- +>>> ?HS/GP : Public ? ? ? ? ? ? ? 1 ? ? ? 0x4A32_6000 - 0x4A32_6FFF (4kB) +>>> ?HS/GP : Public ? ? ? ? ? ? ? 2 ? ? ? 0x4A32_7000 - 0x4A32_73FF (1kB) >>> ->>> HS/EMU : Secured ->>> GP : Public 3 0x4A32_8000 - 0x4A32_87FF (2kB) +>>> ?HS/EMU : Secured +>>> ?GP : Public ? ? ? ? ?3 ? ? ? 0x4A32_8000 - 0x4A32_87FF (2kB) >>> ->>> HS/GP :Secure ->>> write once. 4 0x4A32_9000 - 0x4A32_93FF (1kB) ->>> --------------------------------------------------------------- +>>> ?HS/GP :Secure +>>> ?write once. ? ? ? ? ?4 ? ? ? 0x4A32_9000 - 0x4A32_93FF (1kB) +>>> ?--------------------------------------------------------------- >>> >>> The save process is done entirely by software and restore is done by >>> hardware using the auto-restore feature. The restore feature is enabled @@ -47,7 +47,7 @@ Yeah, I see now. I like your idea of a device-off notifier chain modeled on the CPU PM notifier chain. >> - This patch adds lots of data that is immediately removed by the next ->> patch. Probably the two just need to be combined. +>> ?patch. ?Probably the two just need to be combined. >> > iormap() hunk from this patch can be completely dropped since > it is getting fixed in next patch. Other infrastructure is maintained. @@ -57,16 +57,11 @@ in this patch, and think about how a reviewer is supposed to follow that easily. >> - BUG_ON() should not be used unless there is absolutely no recovery ->> path, since it casues a full kernel panic. Instead, some error ->> recovery should be added. +>> ?path, since it casues a full kernel panic. ? Instead, some error +>> ?recovery should be added. >> > WARN_ON should suffice. Not really. Error recovery should be added. Kevin - -_______________________________________________ -linux-arm-kernel mailing list -linux-arm-kernel@lists.infradead.org -http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N1/content_digest index 3af4fac..8a6b839 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,15 +2,10 @@ "ref\01336990730-26892-7-git-send-email-t-kristo@ti.com\0" "ref\087aa177my3.fsf@ti.com\0" "ref\0CAMQu2gznJ0q-Eqevh9dWn+vw69to91kfFG6hYDvTbGj3zwT0FQ@mail.gmail.com\0" - "From\0Kevin Hilman <khilman@ti.com>\0" - "Subject\0Re: [PATCHv2 06/19] ARM: OMAP4: PM: Add SAR backup support towards device OFF\0" + "From\0khilman@ti.com (Kevin Hilman)\0" + "Subject\0[PATCHv2 06/19] ARM: OMAP4: PM: Add SAR backup support towards device OFF\0" "Date\0Thu, 17 May 2012 09:42:48 -0700\0" - "To\0Shilimkar" - " Santosh <santosh.shilimkar@ti.com>\0" - "Cc\0Tero Kristo <t-kristo@ti.com>" - paul@pwsan.com - linux-omap@vger.kernel.org - " linux-arm-kernel@lists.infradead.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "\"Shilimkar, Santosh\" <santosh.shilimkar@ti.com> writes:\n" @@ -33,18 +28,18 @@ ">>> is fixed in SAR ROM. SAR is split into 4 banks with different\n" ">>> privilege accesses based on device type\n" ">>>\n" - ">>> \302\240---------------------------------------------------------------\n" - ">>> \302\240Access mode \302\240 \302\240 \302\240 \302\240 \302\240Bank \302\240 \302\240Address Range\n" - ">>> \302\240---------------------------------------------------------------\n" - ">>> \302\240HS/GP : Public \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 1 \302\240 \302\240 \302\240 0x4A32_6000 - 0x4A32_6FFF (4kB)\n" - ">>> \302\240HS/GP : Public \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 2 \302\240 \302\240 \302\240 0x4A32_7000 - 0x4A32_73FF (1kB)\n" + ">>> ?---------------------------------------------------------------\n" + ">>> ?Access mode ? ? ? ? ?Bank ? ?Address Range\n" + ">>> ?---------------------------------------------------------------\n" + ">>> ?HS/GP : Public ? ? ? ? ? ? ? 1 ? ? ? 0x4A32_6000 - 0x4A32_6FFF (4kB)\n" + ">>> ?HS/GP : Public ? ? ? ? ? ? ? 2 ? ? ? 0x4A32_7000 - 0x4A32_73FF (1kB)\n" ">>>\n" - ">>> \302\240HS/EMU : Secured\n" - ">>> \302\240GP : Public \302\240 \302\240 \302\240 \302\240 \302\2403 \302\240 \302\240 \302\240 0x4A32_8000 - 0x4A32_87FF (2kB)\n" + ">>> ?HS/EMU : Secured\n" + ">>> ?GP : Public ? ? ? ? ?3 ? ? ? 0x4A32_8000 - 0x4A32_87FF (2kB)\n" ">>>\n" - ">>> \302\240HS/GP :Secure\n" - ">>> \302\240write once. \302\240 \302\240 \302\240 \302\240 \302\2404 \302\240 \302\240 \302\240 0x4A32_9000 - 0x4A32_93FF (1kB)\n" - ">>> \302\240---------------------------------------------------------------\n" + ">>> ?HS/GP :Secure\n" + ">>> ?write once. ? ? ? ? ?4 ? ? ? 0x4A32_9000 - 0x4A32_93FF (1kB)\n" + ">>> ?---------------------------------------------------------------\n" ">>>\n" ">>> The save process is done entirely by software and restore is done by\n" ">>> hardware using the auto-restore feature. The restore feature is enabled\n" @@ -62,7 +57,7 @@ "modeled on the CPU PM notifier chain.\n" "\n" ">> - This patch adds lots of data that is immediately removed by the next\n" - ">> \302\240patch. \302\240Probably the two just need to be combined.\n" + ">> ?patch. ?Probably the two just need to be combined.\n" ">>\n" "> iormap() hunk from this patch can be completely dropped since\n" "> it is getting fixed in next patch. Other infrastructure is maintained.\n" @@ -72,18 +67,13 @@ "easily.\n" "\n" ">> - BUG_ON() should not be used unless there is absolutely no recovery\n" - ">> \302\240path, since it casues a full kernel panic. \302\240 Instead, some error\n" - ">> \302\240recovery should be added.\n" + ">> ?path, since it casues a full kernel panic. ? Instead, some error\n" + ">> ?recovery should be added.\n" ">>\n" "> WARN_ON should suffice.\n" "\n" "Not really. Error recovery should be added.\n" "\n" - "Kevin\n" - "\n" - "_______________________________________________\n" - "linux-arm-kernel mailing list\n" - "linux-arm-kernel@lists.infradead.org\n" - http://lists.infradead.org/mailman/listinfo/linux-arm-kernel + Kevin -5bdfd4731821db5cfc446866e355c8139fe0537cce7fedf14b2d3a4526aabe6f +dbc23f2dcc237c901f9b291d0431eae40bd009950ef3c0a183ae47548d0c4779
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.