From: Peter Chen <peter.chen@freescale.com>
To: Valentin Rothberg <valentinrothberg@gmail.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Andreas Ziegler" <ziegler@cs.fau.de>
Subject: Re: Documentation: update of USB_CHIPIDEA_DEBUG
Date: Tue, 3 Nov 2015 15:03:38 +0800 [thread overview]
Message-ID: <20151103070337.GB21081@shlinux2> (raw)
In-Reply-To: <20151102091508.GB100007@vm-valentin>
On Mon, Nov 02, 2015 at 05:15:08PM +0800, Valentin Rothberg wrote:
> Hi Peter,
>
> your commit 2fb2884ed856 ("usb: chipidea: delete static debug support")
> has shown up in today's Linux next tree (i.e., next-20151102) and
> removes the Kconfig option USB_CHIPIDEA_DEBUG in favor of dynamic debug
> support. However, there are some documentary references on this option
> still left in the code that may need to be updated:
>
> Documentation/usb/chipidea.txt-9-If you want to check some internal variables for otg fsm,
> Documentation/usb/chipidea.txt:10:select CONFIG_USB_CHIPIDEA_DEBUG, there are 2 files which
> ^^^^^^^^^^^^^^^^^^^^^^^^^
> Documentation/usb/chipidea.txt-11-can show otg fsm variables and some controller registers value:
> --
> drivers/usb/chipidea/core.c-25- * Compile Options
> drivers/usb/chipidea/core.c:26: * - CONFIG_USB_CHIPIDEA_DEBUG: enable debug facilities
> ^^^^^^^^^^^^^^^^^^^^^^^^^
> drivers/usb/chipidea/core.c-27- * - STALL_IN: non-empty bulk-in pipes cannot be halted
>
>
> I'm just pointing to those references, since I don't know if you want to
> keep them in the code or not. I found the issue and your commit with
> scipts/checkkconfigsymbols.py.
Thanks, Valentin. I will change them.
>
> Kind regards,
> Valentin
--
Best Regards,
Peter Chen
prev parent reply other threads:[~2015-11-03 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 9:15 Documentation: update of USB_CHIPIDEA_DEBUG Valentin Rothberg
2015-11-03 7:03 ` Peter Chen [this message]
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=20151103070337.GB21081@shlinux2 \
--to=peter.chen@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valentinrothberg@gmail.com \
--cc=ziegler@cs.fau.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