All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd: usb: run 'usb start' when USB is stopped
Date: Mon, 28 Nov 2016 09:11:24 +0100	[thread overview]
Message-ID: <384f905d-ea4c-1b43-04bf-dc40e6a6dcc8@redhat.com> (raw)
In-Reply-To: <fd1e1c2d-1cda-1912-2261-85a703a36946@samsung.com>

Hi,

On 28-11-16 07:54, Minkyu Kang wrote:
> Hi Jaehoon,
>
> On 28/11/16 14:08, Jaehoon Chung wrote:
>> Hi Marek,
>>
>> On 09/23/2016 01:15 PM, Simon Glass wrote:
>>> +Marek
>>>
>>> On 9 September 2016 at 04:20, Jaehoon Chung <jh80.chung@samsung.com> wrote:
>>>> If USB is stopped, just run 'usb start' instead of printing message.
>>>> Then user didn't consider whether usb is started or stopped.
>>
>> Do you have any other opinion for this? :)
>>
>> Best Regards,
>> Jaehoon Chung
>>
>>>>
>>>> Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
>>>> ---
>>>>  cmd/usb.c | 4 ++--
>>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/cmd/usb.c b/cmd/usb.c
>>>> index 455127c..4970851 100644
>>>> --- a/cmd/usb.c
>>>> +++ b/cmd/usb.c
>>>> @@ -651,8 +651,8 @@ static int do_usb(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[])
>>>>                 return 0;
>>>>         }
>>>>         if (!usb_started) {
>>>> -               printf("USB is stopped. Please issue 'usb start' first.\n");
>>>> -               return 1;
>>>> +               printf("USB is stopped. Running 'usb start' first.\n");
>>>> +               do_usb_start();
>>>>         }
>
> It seems to ambiguous whether initialization was succeed or not.

Right at a minimum it should detect that do_usb_start succeeds. E.g.
on an otg port without an otg -> usb-host cable plugged in it will not
succeed.

Regards,

Hans

  reply	other threads:[~2016-11-28  8:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09 10:20 [U-Boot] [PATCH] cmd: usb: run 'usb start' when USB is stopped Jaehoon Chung
2016-09-23  4:15 ` Simon Glass
2016-11-28  5:08   ` Jaehoon Chung
2016-11-28  6:54     ` Minkyu Kang
2016-11-28  8:11       ` Hans de Goede [this message]
2016-11-28  9:45         ` Jaehoon Chung

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=384f905d-ea4c-1b43-04bf-dc40e6a6dcc8@redhat.com \
    --to=hdegoede@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.