U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH V2] spi: Update speed/mode on change
Date: Wed, 31 Mar 2021 15:26:27 -0400	[thread overview]
Message-ID: <20210331192627.GC1310@bill-the-cat> (raw)
In-Reply-To: <afd6fdba-8cd6-3389-7850-f01370755716@denx.de>

On Wed, Mar 31, 2021 at 09:18:28PM +0200, Marek Vasut wrote:
> On 3/29/21 4:40 AM, Marek Vasut wrote:
> > On 3/29/21 4:09 AM, Marek Vasut wrote:
> > > On 3/29/21 3:59 AM, Tom Rini wrote:
> > > > On Mon, Mar 29, 2021 at 03:32:51AM +0200, Marek Vasut wrote:
> > > > > On 3/28/21 11:30 PM, Tom Rini wrote:
> > > > > > On Fri, Feb 26, 2021 at 03:21:24PM +0100, Marek Vasut wrote:
> > > > > > 
> > > > > > > The spi_get_bus_and_cs() may be called on the same bus and chipselect
> > > > > > > with different frequency or mode. This is valid usecase, but the code
> > > > > > > fails to notify the controller of such a configuration change. Call
> > > > > > > spi_set_speed_mode() in case bus frequency or bus mode changed to let
> > > > > > > the controller update the configuration.
> > > > > > > 
> > > > > > > The problem can easily be triggered using the sspi command:
> > > > > > > => sspi 0:0 at 1000
> > > > > > > => sspi 0:0 at 2000
> > > > > > > Without this patch, both transfers happen at 1000
> > > > > > > Hz. With this patch,
> > > > > > > the later transfer happens correctly at 2000 Hz.
> > > > > > > 
> > > > > > > Signed-off-by: Marek Vasut <marex@denx.de>
> > > > > > > Cc: Jagan Teki <jagan@amarulasolutions.com>
> > > > > > > Cc: Patrick Delaunay <patrick.delaunay@st.com>
> > > > > > 
> > > > > > So, very reliably I can make:
> > > > > > https://source.denx.de/u-boot/u-boot/-/jobs/245517
> > > > > > happen locally as well building with clang.? It's not
> > > > > > obvious to me why
> > > > > > the test now fails however.
> > > > > 
> > > > > Can you please be more specific / clear ? I have no idea what those 300
> > > > > lines of cryptic output mean, nor what are you trying to say
> > > > > by the above,
> > > > > sorry.
> > > > 
> > > > If you build with clang, for sandbox, and run the tests, U-Boot crashes
> > > > in the unit tests that you start with "ut dm".
> > > 
> > > And that is related to this patch somehow ? How ?
> > 
> > ... after further discussion off-list to get a better test case
> > description ...
> > 
> > It seems the problem is in sound_beep() and it is unrelated to this
> > patch, as the same problem happens with / without this patch being
> > applied, on:
> > 
> > a7d3ac61482 ("Merge branch '2021-03-28-assorted-bugfixes'")
> > 
> > $ clang --version
> > Debian clang version 11.0.1-2
> > ...
> > $ make CC=clang HOSTCC=clang sandbox_defconfig
> > $ make CC=clang HOSTCC=clang
> > $ gdb --args ./u-boot -d arch/sandbox/dts/test.dtb
> > => ut dm
> > ...
> > Program received signal SIGSEGV, Segmentation fault.
> > dlfree (mem=<optimized out>, mem at entry=0x15c19c50) at
> > common/dlmalloc.c:1623
> > 1623????? if (!(inuse_bit_at_offset(next, nextsz)))?? /* consolidate
> > forward */
> > (gdb) bt
> > #0? dlfree (mem=<optimized out>, mem at entry=0x15c19c50) at
> > common/dlmalloc.c:1623
> > #1? 0x00000000004759e3 in sound_beep (dev=0x15c05580, msecs=<optimized
> > out>, frequency_hz=100)
> >  ?? at drivers/sound/sound-uclass.c:118
> 
> Tom, any further comments ? It seems your claim that this bugfix is causing
> problems with clang is not correct, so I think it should still be applied to
> v2021.04 , unless you can provide more details about the clang problem ?

There's at least a few funny things going on.  Yes, apparently outside
of CI building sandbox with clang and running the tests manually crashes
in sound, before it gets to the SPI tests.  Except when it crashes on
the SPI tests instead, which I did get to happen once.  So there's some
sort of use-after-free or similar bug around here somewhere, similar to
how we can't use the -fstack-protector patch as it exposes other real
problems that need to be fixed first.

So, I'll see if with a new tag and a few other changes having been made
we once again get to the point where your patch doesn't trigger this
issue.  But since it's also not a regression fix, if no one can figure
out what to do about fixing what clang shows us, then it can wait for
v2021.07.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210331/8ed34325/attachment.sig>

  reply	other threads:[~2021-03-31 19:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 14:21 [PATCH V2] spi: Update speed/mode on change Marek Vasut
2021-03-25 17:41 ` Marek Vasut
2021-03-28 21:30 ` Tom Rini
2021-03-29  1:32   ` Marek Vasut
2021-03-29  1:59     ` Tom Rini
2021-03-29  2:09       ` Marek Vasut
2021-03-29  2:40         ` Marek Vasut
2021-03-31 19:18           ` Marek Vasut
2021-03-31 19:26             ` Tom Rini [this message]
2021-03-31 19:40               ` Tom Rini
2021-03-31 20:05                 ` Marek Vasut
2021-03-31 21:45                   ` Tom Rini
2021-03-31 22:19                     ` Simon Glass
2021-04-01 14:18                       ` Tom Rini
2021-03-31 22:39                     ` Marek Vasut
2021-03-31 22:50                       ` Simon Glass
2021-03-31 23:19                         ` Marek Vasut
2021-03-31 23:41                           ` Simon Glass
2021-03-31 23:47                             ` Marek Vasut
2021-03-31 23:54                               ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2021-06-10 12:00 Marek Vasut
2021-06-30 16:49 ` Tom Rini
2021-07-02 17:24   ` Da Xue
2021-07-02 17:44     ` Marek Vasut
     [not found]       ` <CACdvmAh4MZ-rACRAY1nv1d0myCMyNnXjR5htkHTpe3A-wm=B1g@mail.gmail.com>
2021-07-02 18:10         ` Marek Vasut
2021-07-02 18:28           ` Da Xue
2021-07-02 19:06             ` Marek Vasut
2021-07-02 19:35               ` Da Xue
2021-07-02 19:40                 ` Marek Vasut
2021-07-02 20:10                   ` Da Xue
2021-07-02 20:20                     ` Marek Vasut

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=20210331192627.GC1310@bill-the-cat \
    --to=trini@konsulko.com \
    --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