mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexei Budankov <abudankov@huawei.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
	"liuqi (BA)" <liuqi115@huawei.com>,
	Linuxarm <linuxarm@huawei.com>, <gregkh@linuxfoundation.org>,
	<mathieu.poirier@linaro.org>, <mike.leach@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Alexey Budankov <alexey.budankov@huawei.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	<abudankov@huawei.com>
Subject: Re: [PATCH v2] coresight: etm4x: Add Support for HiSilicon ETM device
Date: Thu, 26 May 2022 14:43:32 +0300	[thread overview]
Message-ID: <378cead0-7d2e-2fcd-6113-2059b9446bbc@huawei.com> (raw)
In-Reply-To: <f43d759d-dc07-e2cd-6865-32a91d8c4096@arm.com>

Hi Suzuki,

On 26.05.2022 12:59, Suzuki K Poulose wrote:
> Hi
> 
> 
> 
> On 26/05/2022 09:00, Alexei Budankov wrote:
>> Hi,
>>
>> On 26.05.2022 10:47, liuqi (BA) wrote:
>>>
>>>
>>> On 2022/5/26 15:23, Alexei Budankov wrote:
>>>> Hi Qi,
>>>>
>> <SNIP>
>>>>
>>>> Look like our server firmware should be upgraded, right?
>>>
>>> Yes, seems firmware should be upgraded first, and then you could test ETM device :)
>>
>> I would appreciate if you could share some links to upgrade bits and docs, if possible,
>> so we could use it to perform the upgrade.
> 
> Does your system use ACPI based firmware ? If that is

Not sure about it yet.

> the case, we do not have the support for ETM with system instructions
> at the moment. Anshuman is currently working on addressing
> this.

Thanks for clarification. Good to know.

Thanks,
Alexei

> 
> Cheers
> Suzuki
> 
>>
>> Thanks, > Alexei
>>
> 
> .

      reply	other threads:[~2022-05-26 11:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 12:59 Qi Liu
2020-08-13 13:44 ` Suzuki K Poulose
2020-08-13 21:00 ` Mathieu Poirier
2022-05-25 15:10 ` Alexei Budankov
2022-05-26  2:56   ` liuqi (BA)
2022-05-26  7:23     ` Alexei Budankov
2022-05-26  7:47       ` liuqi (BA)
2022-05-26  8:00         ` Alexei Budankov
2022-05-26  9:59           ` Suzuki K Poulose
2022-05-26 11:43             ` Alexei Budankov [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=378cead0-7d2e-2fcd-6113-2059b9446bbc@huawei.com \
    --to=abudankov@huawei.com \
    --cc=alexey.budankov@huawei.com \
    --cc=anshuman.khandual@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuqi115@huawei.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®