From: Valentin Korenblit <vkorenblit@sequans.com>
To: Arnd Bergmann <arnd@arndb.de>, Miquel Raynal <miquel.raynal@bootlin.com>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
linux-kernel@vger.kernel.org
Subject: Re: [mtd:nand/next 11/31] drivers/mtd/nand/raw/cadence-nand-controller.c:1893:4: error: implicit declaration of function 'ioread64_rep' is invalid in C99
Date: Wed, 28 Sep 2022 12:04:38 +0200 [thread overview]
Message-ID: <a20dc3ff-58e3-2fe2-f531-a2f55db35d4d@sequans.com> (raw)
In-Reply-To: <16c470b0-0a69-4182-9676-2367a7fd831d@www.fastmail.com>
On 9/28/22 10:56, Arnd Bergmann wrote:
> On Wed, Sep 28, 2022, at 10:41 AM, Valentin Korenblit wrote:
>> On 9/27/22 22:02, Arnd Bergmann wrote:
>>> On Tue, Sep 27, 2022, at 4:56 PM, Valentin Korenblit wrote:
>>>>>> But in the mean time I am only half satisfied, because we plan to do
>>>>>> twice more accesses than needed _just_ because of a the COMPILE_TEST
>>>>>> constraint.
>>> It's also possible you have to read from the second word first,
>>> like
>>>
>>> u32 *buf;
>>> do {
>>> buf[1] = __raw_readl(reg + 4);
>>> buf[0] = __raw_readl(reg);
>>> buf += 2;
>>> } while (buf < end);
>> Same result with pairs of readl at OFF0 and when reading at OFF1 first too,
>> I still see sdma_err. I've just opened a case to Cadence to see if there
>> is any workaround for this or if it is just not possible.
> I think this just means that the access has to be done with the exact
> width that is configured, and you cannot implement the access on
> 32-bit architectures. The only possibility is that you can reconfigure
> the nand controller to 32-bit mode at runtime, which is what Cadence
> should be able to tell you.
>
> Arnd
I've just confirmed that we cannot change sdma width in runtime and
that sdma expects to be addressed in burst width, which is the bus
width (64-bit).
Valentin
-- IMPORTANT NOTICE:
The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.
Thank you.
next prev parent reply other threads:[~2022-09-28 10:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 22:31 [mtd:nand/next 11/31] drivers/mtd/nand/raw/cadence-nand-controller.c:1893:4: error: implicit declaration of function 'ioread64_rep' is invalid in C99 kernel test robot
2022-09-21 8:40 ` Miquel Raynal
2022-09-21 8:45 ` Valentin Korenblit
[not found] ` <7074197c-aa8d-f763-cb0f-03ea5335b923@sequans.com>
2022-09-21 14:47 ` Miquel Raynal
2022-09-21 15:49 ` Arnd Bergmann
2022-09-21 16:38 ` Miquel Raynal
2022-09-21 20:01 ` Arnd Bergmann
[not found] ` <6b5a2b19-39c6-5116-60c2-d292ae2e7bae@sequans.com>
2022-09-22 9:36 ` Miquel Raynal
2022-09-22 10:52 ` Arnd Bergmann
2022-09-22 11:00 ` Miquel Raynal
[not found] ` <da19f271-6ad6-7158-2ebe-e54fa5c91f6b@sequans.com>
2022-09-27 20:02 ` Arnd Bergmann
2022-09-28 8:41 ` Valentin Korenblit
2022-09-28 8:56 ` Arnd Bergmann
2022-09-28 10:04 ` Valentin Korenblit [this message]
2022-09-22 9:38 ` Miquel Raynal
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=a20dc3ff-58e3-2fe2-f531-a2f55db35d4d@sequans.com \
--to=vkorenblit@sequans.com \
--cc=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=miquel.raynal@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).