All of lore.kernel.org
 help / color / mirror / Atom feed

diff for duplicates of <VE1PR04MB6638DE9AB1E51213DACCCA0F89BF0@VE1PR04MB6638.eurprd04.prod.outlook.com>

diff --git a/a/1.txt b/N1/1.txt
index e4e1688..8c65ada 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -50,4 +50,9 @@ On 2020/05/13 Sascha Hauer <s.hauer@pengutronix.de> wrote:d
 > So with tx_glitch_fixed we end up with tx.dst_maxburst being the same as two
 > patches before which is rather confusing. Better introduce tx_glitch_fixed in
 > this patch, or maybe even merge this patch and the next one.
-Sorry confused you, I should repleace 'tx_wml=0' in the above comments with ' TX_THRESHOLD=0', which means tx transfer dma have to wait all the tx data in tx fifo transferred with ERR009165 rather than generically 'tx_wml' (for example --half fifo size used as TX_THRESHOLD). Obviously TX_THRESHOLD=0 would down performance, so enlarge dst_maxburst to fifo size as PIO with ERR009165. After ERR009165 fixed at HW level. TX_THRESHOLD could be used as common 'spi_imx->wml' so change it back. Will add more detail information in v8.
\ No newline at end of file
+Sorry confused you, I should repleace 'tx_wml=0' in the above comments with ' TX_THRESHOLD=0', which means tx transfer dma have to wait all the tx data in tx fifo transferred with ERR009165 rather than generically 'tx_wml' (for example --half fifo size used as TX_THRESHOLD). Obviously TX_THRESHOLD=0 would down performance, so enlarge dst_maxburst to fifo size as PIO with ERR009165. After ERR009165 fixed at HW level. TX_THRESHOLD could be used as common 'spi_imx->wml' so change it back. Will add more detail information in v8.
+
+_______________________________________________
+linux-arm-kernel mailing list
+linux-arm-kernel@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index 1ccca84..af7dd7c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -20,24 +20,24 @@
   "To\0Sascha Hauer <s.hauer\@pengutronix.de>\0"
 ]
 [
-  "Cc\0vkoul\@kernel.org <vkoul\@kernel.org>",
-  " shawnguo\@kernel.org <shawnguo\@kernel.org>",
-  " u.kleine-koenig\@pengutronix.de <u.kleine-koenig\@pengutronix.de>",
-  " robh+dt\@kernel.org <robh+dt\@kernel.org>",
-  " festevam\@gmail.com <festevam\@gmail.com>",
-  " dan.j.williams\@intel.com <dan.j.williams\@intel.com>",
-  " mark.rutland\@arm.com <mark.rutland\@arm.com>",
+  "Cc\0mark.rutland\@arm.com <mark.rutland\@arm.com>",
+  " devicetree\@vger.kernel.org <devicetree\@vger.kernel.org>",
   " catalin.marinas\@arm.com <catalin.marinas\@arm.com>",
-  " will.deacon\@arm.com <will.deacon\@arm.com>",
-  " l.stach\@pengutronix.de <l.stach\@pengutronix.de>",
-  " martin.fuzzey\@flowbird.group <martin.fuzzey\@flowbird.group>",
   " kernel\@pengutronix.de <kernel\@pengutronix.de>",
-  " linux-spi\@vger.kernel.org <linux-spi\@vger.kernel.org>",
-  " linux-arm-kernel\@lists.infradead.org <linux-arm-kernel\@lists.infradead.org>",
+  " shawnguo\@kernel.org <shawnguo\@kernel.org>",
+  " will.deacon\@arm.com <will.deacon\@arm.com>",
   " linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
+  " linux-spi\@vger.kernel.org <linux-spi\@vger.kernel.org>",
+  " vkoul\@kernel.org <vkoul\@kernel.org>",
+  " robh+dt\@kernel.org <robh+dt\@kernel.org>",
   " dl-linux-imx <linux-imx\@nxp.com>",
+  " martin.fuzzey\@flowbird.group <martin.fuzzey\@flowbird.group>",
+  " u.kleine-koenig\@pengutronix.de <u.kleine-koenig\@pengutronix.de>",
   " dmaengine\@vger.kernel.org <dmaengine\@vger.kernel.org>",
-  " devicetree\@vger.kernel.org <devicetree\@vger.kernel.org>\0"
+  " dan.j.williams\@intel.com <dan.j.williams\@intel.com>",
+  " festevam\@gmail.com <festevam\@gmail.com>",
+  " linux-arm-kernel\@lists.infradead.org <linux-arm-kernel\@lists.infradead.org>",
+  " l.stach\@pengutronix.de <l.stach\@pengutronix.de>\0"
 ]
 [
   "\0000:1\0"
@@ -98,7 +98,12 @@
   "> So with tx_glitch_fixed we end up with tx.dst_maxburst being the same as two\n",
   "> patches before which is rather confusing. Better introduce tx_glitch_fixed in\n",
   "> this patch, or maybe even merge this patch and the next one.\n",
-  "Sorry confused you, I should repleace 'tx_wml=0' in the above comments with ' TX_THRESHOLD=0', which means tx transfer dma have to wait all the tx data in tx fifo transferred with ERR009165 rather than generically 'tx_wml' (for example --half fifo size used as TX_THRESHOLD). Obviously TX_THRESHOLD=0 would down performance, so enlarge dst_maxburst to fifo size as PIO with ERR009165. After ERR009165 fixed at HW level. TX_THRESHOLD could be used as common 'spi_imx->wml' so change it back. Will add more detail information in v8."
+  "Sorry confused you, I should repleace 'tx_wml=0' in the above comments with ' TX_THRESHOLD=0', which means tx transfer dma have to wait all the tx data in tx fifo transferred with ERR009165 rather than generically 'tx_wml' (for example --half fifo size used as TX_THRESHOLD). Obviously TX_THRESHOLD=0 would down performance, so enlarge dst_maxburst to fifo size as PIO with ERR009165. After ERR009165 fixed at HW level. TX_THRESHOLD could be used as common 'spi_imx->wml' so change it back. Will add more detail information in v8.\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"
 ]
 
-05075d8fd2cf285879a6274f7917c24ad2cc6a2f09353bda3ddb429bdd77b5c7
+3c79bb4af9ffc4535e31d04aae982f237ed3341ac1b634f3d4951e6e0f599fe5
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.