public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: "Tom Rini" <trini@konsulko.com>, "Pali Rohár" <pali@kernel.org>,
	"Lokesh Vutla" <lokeshvutla@ti.com>,
	"Simon Glass" <sjg@chromium.org>,
	"Merlijn Wajer" <merlijn@wizzup.org>,
	maemo-leste@lists.dyne.org, u-boot@lists.denx.de,
	"Pavel Machek" <pavel@ucw.cz>
Subject: Re: [PATCH 1/2] DM_USB: allow building without OF_CONTROL
Date: Sat, 19 Jun 2021 22:33:23 +0300	[thread overview]
Message-ID: <0a8a9dab-ee44-fab7-d712-d66cb121c170@gmail.com> (raw)
In-Reply-To: <bcbe3d09-7141-3e41-7344-8d2ab957cc34@denx.de>

Hi,

On 19.06.21 г. 21:17 ч., Marek Vasut wrote:
> On 6/19/21 8:14 AM, Ivaylo Dimitrov wrote:
>> Hi Marek,
> 
> Hi,
> 
> [...]
> 
>>>>> Currently DM_USB requires OF_CONTROL to be enabled, otherwise link 
>>>>> errors
>>>>> occur. On the other hand OF_CONTROL requires board code to be 
>>>>> migrated to
>>>>> DT, which is not always possible or required.
>>>>>
>>>>> Fix that by conditionally compiling OF_CONTROL specific sections in 
>>>>> USB
>>>>> related drivers code in the same way like it is done in the other 
>>>>> drivers.
>>>>> Also, auto select OF_LIBFDT if DM_USB is selected but OF_CONTROL is 
>>>>> not.
>>>>> Introduce a new Kconfig option OF_NODE used to compile of_node.c in 
>>>>> case
>>>>> OF_CONTROL is not enabled. Fix deprecation warning condition as well.
>>>
>>> So, what is the use case of this? Why not just enable DM_USB and 
>>> OF_CONTROL ?
>>
>> OF_CONTROL requires migration to device-tree.
> 
> That's where the supported platforms are heading anyway. Or is there 
> some issue with switching the platform you use over to DT ?

OK, let me elaborate: It is about enabling DM_USB on N900 (Nokia rx-51 
board). For various reasons I am not going to discuss (1), migration to 
DM was delayed to the point where we saw "[PATCH] arm: Remove nokia_rx51 
board" with a commit message "This board has not been converted to 
CONFIG_DM_USB by the deadline. Remove it." posted. The missing pieces 
were WDT (a patch is already merged in -next) and DM_USB. The board 
itself does not support host mode, but USB TTY is very useful for 
debugging purposes. The particular task I am after is USB DM migration 
and the $subject patch allows this to be achieved with relatively little 
effort (a couple of defconfig changes), incomparable with the effort 
needed for migration to DT. As we are already past the DM migration 
deadline I think it makes sense to fulfil its requirements before 
undertaking such a big task like migration to DT.

Regards,
Ivo

(1) https://www.mail-archive.com/u-boot@lists.denx.de/msg409064.html

  reply	other threads:[~2021-06-19 19:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 14:57 [PATCH 1/2] DM_USB: allow building without OF_CONTROL Pali Rohár
2021-06-18 14:57 ` [PATCH 2/2] Nokia RX-51: Enable CONFIG_DM_USB to remove deprecation warning Pali Rohár
2021-06-26 18:31   ` Simon Glass
2021-06-18 16:38 ` [PATCH 1/2] DM_USB: allow building without OF_CONTROL Tom Rini
2021-06-19  2:23   ` Marek Vasut
2021-06-19  6:14     ` Ivaylo Dimitrov
2021-06-19 18:17       ` Marek Vasut
2021-06-19 19:33         ` Ivaylo Dimitrov [this message]
2021-06-19 19:38           ` Marek Vasut
2021-06-19 20:15             ` Ivaylo Dimitrov
2021-06-19 20:51               ` Tom Rini
2021-06-20  3:52                 ` Marek Vasut
2021-06-20 15:54                   ` Tom Rini
2021-06-20 19:43                     ` Marek Vasut
2021-06-25 12:38                       ` Tom Rini
2021-06-25 13:07                         ` Pali Rohár
2021-06-25 16:04                           ` Simon Glass
2021-06-25 16:16                             ` Pali Rohár
2021-06-25 16:43                               ` Simon Glass
2021-06-25 16:58                                 ` Pali Rohár
2021-06-27 19:06                                   ` Simon Glass
2021-06-28 13:39                                     ` Tom Rini
2021-06-28 14:20                                       ` Simon Glass
2021-06-28 14:43                                         ` Tom Rini
2021-06-25 21:31                             ` Ivaylo Dimitrov
2021-06-25 21:37                               ` Tom Rini
2021-06-25 21:51                                 ` Pali Rohár
2021-06-25 21:59                                   ` Tom Rini
2021-06-26 10:59                                     ` Merlijn Wajer
2021-06-26 14:58                                       ` Tom Rini
2021-06-30  7:12                                         ` Ivaylo Dimitrov
2021-06-30  7:30                                         ` Ivaylo Dimitrov
2021-06-30 13:33                                           ` Tom Rini
2021-06-30 14:31                                             ` Ivaylo Dimitrov
2021-06-30 15:48                                               ` Tom Rini
2021-06-30 16:02                                                 ` Simon Glass

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=0a8a9dab-ee44-fab7-d712-d66cb121c170@gmail.com \
    --to=ivo.g.dimitrov.75@gmail.com \
    --cc=lokeshvutla@ti.com \
    --cc=maemo-leste@lists.dyne.org \
    --cc=marex@denx.de \
    --cc=merlijn@wizzup.org \
    --cc=pali@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sjg@chromium.org \
    --cc=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