From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sai Prakash Ranjan Subject: Re: [PATCHv4 1/4] arm64: dts: qcom: sdm845: Add Coresight support Date: Tue, 29 Jan 2019 00:47:50 +0530 Message-ID: References: <1bd39862-0725-70ce-6535-fdb59569f683@arm.com> <75ed74af-6946-b86d-092e-42dc16e55308@codeaurora.org> <91a90daa-9e14-2d2e-e633-2ddfdc0955bf@arm.com> <3906faf1-abbd-9c28-ad55-ed3800f06352@codeaurora.org> <5b54c6e0-7d22-ecee-486f-31333f49f84a@codeaurora.org> <18b70426-60fe-4871-6388-6e09fd5feb37@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Mathieu Poirier Cc: Suzuki K Poulose , Rob Herring , Leo Yan , Alexander Shishkin , Andy Gross , David Brown , Vivek Gautam , Doug Anderson , Stephen Boyd , Bjorn Andersson , devicetree@vger.kernel.org, Mark Rutland , Rajendra Nayak , Sibi Sankar , linux-arm-kernel , Linux Kernel Mailing List , linux-arm-msm , John Horley List-Id: devicetree@vger.kernel.org On 1/28/2019 10:45 PM, Mathieu Poirier wrote: >> For SDM845(A75 based): >> >> *0xB_B8_03* does indicate that the JEP106 identification >> code is 0x3B and continuation code is 0x4 which is of ARM and not >> QCOM(JEP106 ID is 0x70) which is expected. >> >> And the other values of PIDR0[0:7] and PIDR1[3:0] are *Implementation >> defined part numbers* and can be different from ARM A75/A55. >> >> I think this clears up case for SDM845. >> >> As for MSM8996, it is not based on any ARM derivative and hence the >> JEP106 ID is of QCOM(0x70) from the value of pid = *0xF_02_11* >> based on PIDR1[7:4] and PIDR2[2:0]. This clears this as well. >> >> Please correct me if I am wrong and also let me know if I can >> continue with PID addition to table. > > Please proceed. > Thanks Mathieu, posted the next version now. -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation