From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/8] spi: Kconfig: Mark MXS_SPI has BROKEN
Date: Tue, 14 May 2019 19:33:17 +0200 [thread overview]
Message-ID: <5f332176-2cf2-e02a-e1ad-4d30fb0284f5@denx.de> (raw)
In-Reply-To: <20190514144559.GR22232@bill-the-cat>
On 5/14/19 4:45 PM, Tom Rini wrote:
> On Tue, May 14, 2019 at 07:46:06PM +0530, Jagan Teki wrote:
>> On Mon, Apr 29, 2019 at 4:54 PM Tom Rini <trini@konsulko.com> wrote:
>>>
>>> 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.
>>
>> Yes, the idea here is to build the broken one by selecting BROKEN
>> so-that the travis-CI is green and have warning on the build,
>> otherwise it is another rework of selecting BROKEN for those
>> non-converted drivers if they depends.
>>
>>>
>>> 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.
>>
>> ie what this series does. Driver (for example) will select BROKEN,
>> that means it is still working bu would like to remove in next
>> versions and so..
>
> What I'm after is
> https://github.com/trini/u-boot/commits/WIP-BROKEN-test which is close,
> but not quite there. We no longer build the drivers marked as BROKEN by
> default, and the fallout from that has been:
> - Some missing dependencies (I'm trying to fix that now) leading to
> build problems.
> - Needing to yank CONFIG_SPI for example from configs that had been
> using a now-not-built driver as the subsystem fails to link if there's
> no controller. I don't think that's a problem however.
> - Needing to migrate a few more symbols to Kconfig in order to be able
> to properly express "You need to depend on BROKEN to use this option
> now".
I still disagree with marking drivers that need DM conversion, but are
otherwise working perfectly fine, as broken. That's just misleading and
in fact incorrect. Invent some new, more descriptive Kconfig option please.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-05-14 17:33 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
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 [this message]
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=5f332176-2cf2-e02a-e1ad-4d30fb0284f5@denx.de \
--to=marex@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