From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/8] spi: Kconfig: Mark MXS_SPI has BROKEN
Date: Mon, 29 Apr 2019 07:24:52 -0400 [thread overview]
Message-ID: <20190429112452.GJ31207@bill-the-cat> (raw)
In-Reply-To: <f04e02a9-0827-0af8-fb01-fb643ea73dc2@denx.de>
On Mon, Apr 29, 2019 at 01:06:57PM +0200, Marek Vasut wrote:
> On 4/29/19 1:02 PM, Jagan Teki wrote:
> > On Mon, Apr 29, 2019 at 4:28 PM Marek Vasut <marex@denx.de> wrote:
> >>
> >> On 4/29/19 12:40 PM, Jagan Teki wrote:
> >>> On Mon, Apr 29, 2019 at 3:24 PM Marek Vasut <marex@denx.de> wrote:
> >>>>
> >>>> On 4/28/19 10:47 PM, Jagan Teki wrote:
> >>>>> Mark MXS_SPI has BROKEN, this so the resulting build shows
> >>>>> warning for broken configuration enabled and associated code
> >>>>> will remove in v2019.07 release.
> >>>>
> >>>> But the code is not broken, it works fine, right ?
> >>>
> >>> Yes the code work fine, but dm conversion not done yet. Now the
> >>> CONFIG_BROKEN can mark the driver configs which doesn't convert dm
> >>
> >> That makes no sense, if the code works, it works and thus it is NOT
> >> broken. Find some other way to flag it as non-DM-converted, not this hack.
> >
> > np, It depends on whether we consider non-dm code(for legacy SPI
> > drivers) is broken or not, let Tom comment on this.
>
> Again, the code works, it's not broken. That's very clear.
> DM conversion is a separate matter, so let's not overload CONFIG_BROKEN
> for such things. The Makefile warning seems sufficient to me.
The code is broken because it doesn't work with DM and is going to be
removed due to lack of maintenance soon. My problem with this series,
but I need to check that we can do what I want to do and still keep
travis green, is have this (and the other non-converted and thus
non-maintained drivers) depend on, not select BROKEN.
The Makefile warnings tell people the code is going to be removed and
I'm trying to have the window be:
1) LOUD warning about needing work
2) 1 release past those loud deadlines of the code there, but not built
unless you enable BROKEN (as yes, I see code that's not updated to use
DM as being broken)
3) Code removed.
All that said, I continue to be open to delaying conversion / removal if
we're having:
- A discussion and proposed patches to do the conversion, but people
need more time. The work is in progress, but people need time as it's
not as easy to convert as hoped for various reasons.
- A problem converting the driver to DM as it's highlighting some other
problem within DM or hitting a size constraint or other problem.
- Someone who is willing to do the DM work is just now seeing this.
Yes, this is possible especially since our LOUD Makefile warnings are
also easy enough to miss if you're just automating the build and not
doing it manually.
But I am not fine with:
- Code that isn't converted AND
- Code that no one seems to be converting AND
- Code that no one says they are going to convert AND
- The conversion deadline has past.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190429/ccd42d22/attachment.sig>
next prev parent reply other threads:[~2019-04-29 11:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 20:47 [U-Boot] [PATCH 0/8] spi: Mark non-dm spi drivers as BROKEN Jagan Teki
2019-04-28 20:47 ` [U-Boot] [PATCH 1/8] Kconfig: Update CONFIG_BROKEN help text Jagan Teki
2019-04-29 5:56 ` Heinrich Schuchardt
2019-04-28 20:47 ` [U-Boot] [PATCH 2/8] Makefile: Trigger a Warning if BROKEN defined Jagan Teki
2019-04-29 6:00 ` Heinrich Schuchardt
2019-04-28 20:47 ` [U-Boot] [PATCH 3/8] Makefile: Trigger a warning for legcay spi drivers Jagan Teki
2019-04-28 20:47 ` [U-Boot] [PATCH 4/8] spi: Kconfig: Mark MXS_SPI has BROKEN Jagan Teki
2019-04-29 7:58 ` Marek Vasut
2019-04-29 10:40 ` Jagan Teki
2019-04-29 10:58 ` Marek Vasut
2019-04-29 11:02 ` Jagan Teki
2019-04-29 11:06 ` Marek Vasut
2019-04-29 11:24 ` Tom Rini [this message]
2019-04-29 11:27 ` Marek Vasut
2019-04-29 12:34 ` Michael Nazzareno Trimarchi
2019-04-29 12:47 ` Tom Rini
2019-04-29 12:53 ` Marek Vasut
2019-04-29 14:02 ` Jagan Teki
2019-05-14 14:16 ` Jagan Teki
2019-05-14 14:45 ` Tom Rini
2019-05-14 17:33 ` Marek Vasut
2019-05-14 17:37 ` Tom Rini
2019-05-14 17:41 ` Marek Vasut
2019-05-14 18:00 ` Tom Rini
2019-04-28 20:47 ` [U-Boot] [PATCH 5/8] spi: Kconfig: Mark SH_SPI " Jagan Teki
2019-04-28 20:47 ` [U-Boot] [PATCH 6/8] spi: Kconfig: Mark SOFT_SPI " Jagan Teki
2019-04-28 20:48 ` [U-Boot] [PATCH 7/8] spi: Kconfig: Mark FSL_ESPI " Jagan Teki
2019-04-28 20:48 ` [U-Boot] [PATCH 8/8] spi: Kconfig: Mark LPC32XX_SSP " Jagan Teki
2019-04-30 20:48 ` Vladimir Zapolskiy
2019-05-09 14:11 ` Sylvain Lemieux
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=20190429112452.GJ31207@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