From: Vanessa Page <Vebpe@outlook.com>
To: kernel test robot <lkp@intel.com>
Cc: " 周琰杰 (Zhou Yanjie) " <zhouyanjie@wanyeetech.com>,
"Tudor.Ambarus@microchip.com" <Tudor.Ambarus@microchip.com>,
"p.yadav@ti.com" <p.yadav@ti.com>,
"michael@walle.cc" <michael@walle.cc>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"aidanmacdonald.0x0@gmail.com" <aidanmacdonald.0x0@gmail.com>,
"tmn505@gmail.com" <tmn505@gmail.com>,
"paul@crapouillou.net" <paul@crapouillou.net>,
"dongsheng.qiu@ingenic.com" <dongsheng.qiu@ingenic.com>,
"aric.pzqi@ingenic.com" <aric.pzqi@ingenic.com>,
"rick.tyliu@ingenic.com" <rick.tyliu@ingenic.com>,
"jinghui.liu@ingenic.com" <jinghui.liu@ingenic.com>,
"sernia.zhou@foxmail.com" <sernia.zhou@foxmail.com>,
"reimu@sudomaker.com" <reimu@sudomaker.com>
Subject: Re: [PATCH 3/3] SPI: Ingenic: Add SFC support for Ingenic SoCs.
Date: Sun, 24 Jul 2022 01:28:29 +0000 [thread overview]
Message-ID: <MN2PR17MB337549EACCAA9E83CB484F9FB8929@MN2PR17MB3375.namprd17.prod.outlook.com> (raw)
In-Reply-To: <202207240839.YeZ8uQ0T-lkp@intel.com>
288 op->dummy.nbytes * 8 / op->dummy.buswidth);
289
290 if (op->data.nbytes > 0)
291 val |= TRAN_CONF_DATA_EN;
292
293 writel(val, sfc->base + SFC_REG_TRAN_CONF(0));
294 writel(op->data.nbytes, sfc->base + SFC_REG_TRAN_LEN);
295
296
Sent from my iPhone
> On Jul 23, 2022, at 8:47 PM, kernel test robot <lkp@intel.com> wrote:
>
> 288 op->dummy.nbytes * 8 / op->dummy.buswidth);
> 289
> 290 if (op->data.nbytes > 0)
> 291 val |= TRAN_CONF_DATA_EN;
> 292
> 293 writel(val, sfc->base + SFC_REG_TRAN_CONF(0));
> 294 writel(op->data.nbytes, sfc->base + SFC_REG_TRAN_LEN);
> 295
> 296
WARNING: multiple messages have this Message-ID (diff)
From: Vanessa Page <Vebpe@outlook.com>
To: kernel test robot <lkp@intel.com>
Cc: " 周琰杰 (Zhou Yanjie) " <zhouyanjie@wanyeetech.com>,
"Tudor.Ambarus@microchip.com" <Tudor.Ambarus@microchip.com>,
"p.yadav@ti.com" <p.yadav@ti.com>,
"michael@walle.cc" <michael@walle.cc>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"aidanmacdonald.0x0@gmail.com" <aidanmacdonald.0x0@gmail.com>,
"tmn505@gmail.com" <tmn505@gmail.com>,
"paul@crapouillou.net" <paul@crapouillou.net>,
"dongsheng.qiu@ingenic.com" <dongsheng.qiu@ingenic.com>,
"aric.pzqi@ingenic.com" <aric.pzqi@ingenic.com>,
"rick.tyliu@ingenic.com" <rick.tyliu@ingenic.com>,
"jinghui.liu@ingenic.com" <jinghui.liu@ingenic.com>,
"sernia.zhou@foxmail.com" <sernia.zhou@foxmail.com>,
"reimu@sudomaker.com" <reimu@sudomaker.com>
Subject: Re: [PATCH 3/3] SPI: Ingenic: Add SFC support for Ingenic SoCs.
Date: Sun, 24 Jul 2022 01:28:29 +0000 [thread overview]
Message-ID: <MN2PR17MB337549EACCAA9E83CB484F9FB8929@MN2PR17MB3375.namprd17.prod.outlook.com> (raw)
In-Reply-To: <202207240839.YeZ8uQ0T-lkp@intel.com>
288 op->dummy.nbytes * 8 / op->dummy.buswidth);
289
290 if (op->data.nbytes > 0)
291 val |= TRAN_CONF_DATA_EN;
292
293 writel(val, sfc->base + SFC_REG_TRAN_CONF(0));
294 writel(op->data.nbytes, sfc->base + SFC_REG_TRAN_LEN);
295
296
Sent from my iPhone
> On Jul 23, 2022, at 8:47 PM, kernel test robot <lkp@intel.com> wrote:
>
> 288 op->dummy.nbytes * 8 / op->dummy.buswidth);
> 289
> 290 if (op->data.nbytes > 0)
> 291 val |= TRAN_CONF_DATA_EN;
> 292
> 293 writel(val, sfc->base + SFC_REG_TRAN_CONF(0));
> 294 writel(op->data.nbytes, sfc->base + SFC_REG_TRAN_LEN);
> 295
> 296
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-07-24 1:28 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 16:48 [PATCH 0/3] Add SFC support for Ingenic SoCs 周琰杰 (Zhou Yanjie)
2022-07-22 16:48 ` 周琰杰 (Zhou Yanjie)
2022-07-22 16:48 ` [PATCH 1/3] mtd: spi-nor: Use the spi-mem poll status APIs 周琰杰 (Zhou Yanjie)
2022-07-22 16:48 ` 周琰杰 (Zhou Yanjie)
2022-07-23 8:30 ` Sergey Shtylyov
2022-07-23 8:30 ` Sergey Shtylyov
2022-07-22 16:48 ` [PATCH 2/3] dt-bindings: SPI: Add Ingenic SFC bindings 周琰杰 (Zhou Yanjie)
2022-07-22 16:48 ` 周琰杰 (Zhou Yanjie)
2022-07-22 17:46 ` Krzysztof Kozlowski
2022-07-22 17:46 ` Krzysztof Kozlowski
2022-07-23 16:50 ` Zhou Yanjie
2022-07-23 16:50 ` Zhou Yanjie
2022-07-23 17:43 ` Krzysztof Kozlowski
2022-07-23 17:43 ` Krzysztof Kozlowski
2022-07-23 18:47 ` Mike Yang
2022-07-23 18:47 ` Mike Yang
2022-07-23 19:27 ` Mark Brown
2022-07-23 19:27 ` Mark Brown
2022-07-23 20:07 ` Krzysztof Kozlowski
2022-07-23 20:07 ` Krzysztof Kozlowski
2022-07-23 20:49 ` Mike Yang
2022-07-23 20:49 ` Mike Yang
2022-07-24 15:33 ` Zhou Yanjie
2022-07-24 15:33 ` Zhou Yanjie
2022-07-25 18:30 ` Rob Herring
2022-07-25 18:30 ` Rob Herring
2022-07-23 20:05 ` Krzysztof Kozlowski
2022-07-23 20:05 ` Krzysztof Kozlowski
2022-07-24 14:52 ` Zhou Yanjie
2022-07-24 14:52 ` Zhou Yanjie
2022-07-22 22:44 ` Rob Herring
2022-07-22 22:44 ` Rob Herring
2022-07-22 16:48 ` [PATCH 3/3] SPI: Ingenic: Add SFC support for Ingenic SoCs 周琰杰 (Zhou Yanjie)
2022-07-22 16:48 ` 周琰杰 (Zhou Yanjie)
2022-07-22 18:07 ` Krzysztof Kozlowski
2022-07-22 18:07 ` Krzysztof Kozlowski
2022-07-23 16:53 ` Zhou Yanjie
2022-07-23 16:53 ` Zhou Yanjie
2022-07-22 18:38 ` Mark Brown
2022-07-22 18:38 ` Mark Brown
2022-07-23 17:06 ` Zhou Yanjie
2022-07-23 17:06 ` Zhou Yanjie
2022-07-23 19:32 ` Mark Brown
2022-07-23 19:32 ` Mark Brown
2022-07-24 1:24 ` Zhou Yanjie
2022-07-24 1:24 ` Zhou Yanjie
2022-07-22 20:03 ` Paul Cercueil
2022-07-22 20:03 ` Paul Cercueil
2022-07-23 17:26 ` Zhou Yanjie
2022-07-23 17:26 ` Zhou Yanjie
2022-07-23 20:24 ` Paul Cercueil
2022-07-23 20:24 ` Paul Cercueil
2022-07-24 15:29 ` Zhou Yanjie
2022-07-24 15:29 ` Zhou Yanjie
2022-07-23 15:15 ` Christophe JAILLET
2022-07-23 15:15 ` Christophe JAILLET
2022-07-23 15:15 ` Christophe JAILLET
2022-07-24 1:22 ` Zhou Yanjie
2022-07-24 1:22 ` Zhou Yanjie
2022-07-24 0:43 ` kernel test robot
2022-07-24 0:43 ` kernel test robot
2022-07-24 1:28 ` Vanessa Page [this message]
2022-07-24 1:28 ` Vanessa Page
2022-07-25 16:58 ` Vanessa Page
2022-07-23 14:47 ` [PATCH 0/3] " Tomasz Maciej Nowak
2022-07-23 14:47 ` Tomasz Maciej Nowak
2022-07-24 1:25 ` Zhou Yanjie
2022-07-24 1:25 ` Zhou Yanjie
2022-07-24 1:28 ` Vanessa Page
2022-07-24 1:28 ` Vanessa Page
2022-07-24 1:28 ` Vanessa Page
2022-07-24 1:28 ` Vanessa Page
2022-07-24 1:30 ` Vanessa Page
2022-07-24 1:30 ` Vanessa Page
2022-07-24 1:32 ` Vee Page
2022-07-24 1:32 ` Vee Page
2022-07-26 6:13 ` Vee Page
2022-07-26 6:13 ` Vee Page
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=MN2PR17MB337549EACCAA9E83CB484F9FB8929@MN2PR17MB3375.namprd17.prod.outlook.com \
--to=vebpe@outlook.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=aidanmacdonald.0x0@gmail.com \
--cc=aric.pzqi@ingenic.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dongsheng.qiu@ingenic.com \
--cc=jinghui.liu@ingenic.com \
--cc=kbuild-all@lists.01.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=paul@crapouillou.net \
--cc=reimu@sudomaker.com \
--cc=richard@nod.at \
--cc=rick.tyliu@ingenic.com \
--cc=robh+dt@kernel.org \
--cc=sernia.zhou@foxmail.com \
--cc=tmn505@gmail.com \
--cc=vigneshr@ti.com \
--cc=zhouyanjie@wanyeetech.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.