From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Stefan Roese" <sr@denx.de>, "Nuno Sá" <nuno.sa@analog.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH v3 1/2] mtd: cfi: respect reg address length
Date: Fri, 28 Apr 2023 13:25:16 +0200 [thread overview]
Message-ID: <0d4550ef73b225fe8c60c1949bbc630b2d4966f2.camel@gmail.com> (raw)
In-Reply-To: <bc143515-b004-9197-843e-be92756ea262@denx.de>
Hi Stefan,
On Fri, 2023-04-28 at 11:59 +0200, Stefan Roese wrote:
> Hi Nuno Sá,
>
> On 4/26/23 16:16, Nuno Sá wrote:
> > flash_get_size() will get the flash size from the device itself and go
> > through all erase regions to read protection status. However, the device
> > mappable region (eg: devicetree reg property) might be lower than the
> > device full size which means that the above cycle will result in a data
> > bus exception. This change fixes it by reading the 'addr_size' during
> > probe() and also use that as one possible upper limit.
> >
> > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> > ---
> >
> > v2:
> > * Fix compilation when CONFIG_CFI_FLASH is not set. Done by redefining
> > cfi_flash_bank_size() when CONFIG_CFI_FLASH is set (by returning dts
> > size).
> >
> > v3:
> > * Fix another compilation warning by explicitly casting to unsigned
> > long in cfi_flash_bank_size()
> >
> > Stefan, I did ran a world build [1] by opening a PR in github (to force CI
> > to run). However I had to bypass the pytest stage (it was giving me some
> > unrelated problems) and there are a couple of jobs failing but the
> > errors apparently are not related to this patchset. Hopefully things now
> > pass in your tests.
> >
> > [1]: https://github.com/u-boot/u-boot/pull/281
>
> Unfortunately this breaks my usual Azure CI build in the test_py phase.
> And this works without any issues without those 2 patches applied. So
> its related to these changes.
>
Sorry for this... It seemed unrelated and the logs don't say much about why is
it failing. I'll try to see what's the problem.
- Nuno Sá
prev parent reply other threads:[~2023-04-28 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 14:16 [PATCH v3 1/2] mtd: cfi: respect reg address length Nuno Sá
2023-04-26 14:16 ` [PATCH v3 2/2] mtd: cfi: change cfi_flash_bank_size() return type Nuno Sá
2023-04-28 9:59 ` [PATCH v3 1/2] mtd: cfi: respect reg address length Stefan Roese
2023-04-28 11:25 ` Nuno Sá [this message]
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=0d4550ef73b225fe8c60c1949bbc630b2d4966f2.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=nuno.sa@analog.com \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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