linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Slark Xiao" <slark_xiao@163.com>
To: "Sergei Shtylyov" <sergei.shtylyov@gmail.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH] [v2,1/1] This aims to support Foxconn SDX55
Date: Thu, 12 Aug 2021 09:46:48 +0800 (CST)	[thread overview]
Message-ID: <3068a773.9a1.17b380a5d58.Coremail.slark_xiao@163.com> (raw)
In-Reply-To: <c62d60aa-2e2d-8465-b0d9-e2409ef4de5a@gmail.com>

















At 2021-08-11 18:58:09, "Sergei Shtylyov" <sergei.shtylyov@gmail.com> wrote:
>Hello!
>
>On 11.08.2021 11:56, Slark Xiao wrote:
>
>> Foxconn SDX55 T77W175 device is working in PCIe mode normally.
>> You can find it in drivers/bus/mhi/pci_geneirc.c file.
>
>    pci_generic? :-)
>
>> But in some scenario, we need to capture the memory dump once it crashed.
>> So a diag port driver is needed.
>> 
>> Signed-off-by: Slark Xiao <slark_xiao@163.com>
>[...]
>
>MBR, Sergei

Hi Sergei,
   Yes, I didn't mix them up. Our product supports 3 modes: PCIE only, USB only, and PCIE+USB.
   Normally, it would be PCIE mode. When we want to reproduce some crash issue, we will switch it from PCIE mode to PCIE+USB mode.
  In this scenario, the USB port is used for capturing memory dump as our tool is designed based on Qualcomm USB Sahara protocol.

Thanks.

  reply	other threads:[~2021-08-12  1:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  8:56 [PATCH] [v2,1/1] This aims to support Foxconn SDX55 Slark Xiao
2021-08-11 10:58 ` Sergei Shtylyov
2021-08-12  1:46   ` Slark Xiao [this message]
     [not found]   ` <4e38db09.53c.17b37e7bc99.Coremail.slark_xiao@163.com>
2021-08-12 10:00     ` Sergei Shtylyov
2021-08-11 11:42 ` Greg KH
2021-08-12  1:52   ` Slark Xiao
2021-08-12  6:46     ` Greg KH
2021-08-12 10:51       ` Slark Xiao
2021-08-11 12:01 ` Bjørn Mork
2021-08-12  2:07   ` Slark Xiao

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=3068a773.9a1.17b380a5d58.Coremail.slark_xiao@163.com \
    --to=slark_xiao@163.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sergei.shtylyov@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).