From: "Wu, Hao A" <hao.a.wu@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>, "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH] SourceLevelDebugPkg DebugCommUsb3: Return error when debug cap is reset
Date: Tue, 20 Mar 2018 01:24:39 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A0931D68B1D@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1521463542-135668-1-git-send-email-star.zeng@intel.com>
Reviewed-by: Hao Wu <hao.a.wu@intel.com>
Best Regards,
Hao Wu
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Star
> Zeng
> Sent: Monday, March 19, 2018 8:46 PM
> To: edk2-devel@lists.01.org
> Cc: Ni, Ruiyu; Wu, Hao A; Zeng, Star
> Subject: [edk2] [PATCH] SourceLevelDebugPkg DebugCommUsb3: Return error
> when debug cap is reset
>
> When source level debug is enabled, but debug cable is not connected,
> XhcResetHC() in XhciReg.c will reset the host controller, the debug
> capability registers will be also reset. After the code in
> InitializeUsbDebugHardware() sets DCE bit and LSE bit to "1" in DCCTRL,
> there will be DMA on 0 (the value of some debug capability registers
> for data transfer is 0) address buffer, fault info like below will
> appear when IOMMU based on VTd is enabled.
>
> VER_REG - 0x00000010
> CAP_REG - 0x00D2008C40660462
> ECAP_REG - 0x0000000000F050DA
> GSTS_REG - 0xC0000000
> RTADDR_REG - 0x0000000086512000
> CCMD_REG - 0x2800000000000000
> FSTS_REG - 0x00000002
> FECTL_REG - 0xC0000000
> FEDATA_REG - 0x00000000
> FEADDR_REG - 0x00000000
> FEUADDR_REG - 0x00000000
> FRCD_REG[0] - 0xC0000006000000A0 0000000000000000
> Fault Info - 0x0000000000000000
> Source - B00 D14 F00
> Type - 1 (read)
> Reason - 6
> IVA_REG - 0x0000000000000000
> IOTLB_REG - 0x1200000000000000
>
> This patch is to return error for the case.
>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Hao Wu <hao.a.wu@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Star Zeng <star.zeng@intel.com>
> ---
> .../DebugCommunicationLibUsb3/DebugCommunicationLibUsb3Common.c |
> 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git
> a/SourceLevelDebugPkg/Library/DebugCommunicationLibUsb3/DebugCommun
> icationLibUsb3Common.c
> b/SourceLevelDebugPkg/Library/DebugCommunicationLibUsb3/DebugCommun
> icationLibUsb3Common.c
> index fb9ca84fc7bc..86ecc2f9dbc7 100644
> ---
> a/SourceLevelDebugPkg/Library/DebugCommunicationLibUsb3/DebugCommun
> icationLibUsb3Common.c
> +++
> b/SourceLevelDebugPkg/Library/DebugCommunicationLibUsb3/DebugCommun
> icationLibUsb3Common.c
> @@ -673,11 +673,19 @@ InitializeUsbDebugHardware (
> UINTN Index;
> UINT8 TotalUsb3Port;
> EFI_PHYSICAL_ADDRESS XhciOpRegister;
> + UINT32 Dcddi1;
>
> XhciOpRegister = Handle->XhciOpRegister;
> TotalUsb3Port = MmioRead32 (((UINTN) Handle->XhciMmioBase +
> XHC_HCSPARAMS1_OFFSET)) >> 24;
>
> if (Handle->Initialized == USB3DBG_NOT_ENABLED) {
> + Dcddi1 = XhcReadDebugReg (Handle,XHC_DC_DCDDI1);
> + if (Dcddi1 != (UINT32)((XHCI_DEBUG_DEVICE_VENDOR_ID << 16) |
> XHCI_DEBUG_DEVICE_PROTOCOL)) {
> + //
> + // The debug capability has been reset by other code, return device error.
> + //
> + return EFI_DEVICE_ERROR;
> + }
> //
> // If XHCI supports debug capability, hardware resource has been allocated,
> // but it has not been enabled, try to enable again.
> --
> 2.7.0.windows.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2018-03-20 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 12:45 [PATCH] SourceLevelDebugPkg DebugCommUsb3: Return error when debug cap is reset Star Zeng
2018-03-20 1:24 ` Wu, Hao A [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-list 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=B80AF82E9BFB8E4FBD8C89DA810C6A0931D68B1D@SHSMSX104.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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