mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikunj Kela <quic_nkela@quicinc.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v5 0/2] Allow parameter in smc/hvc calls
Date: Fri, 30 Jun 2023 08:14:46 -0700	[thread overview]
Message-ID: <0c9e5d7e-effc-6601-bc09-98ca74479833@quicinc.com> (raw)
In-Reply-To: <20230630094441.fxwd4eagtj5wmbbg@bogus>


On 6/30/2023 2:44 AM, Sudeep Holla wrote:
> On Wed, Jun 28, 2023 at 01:38:32PM -0700, Nikunj Kela wrote:
>> On 5/31/2023 5:26 AM, Sudeep Holla wrote:
>>> On Sat, 06 May 2023 11:24:26 -0700, Nikunj Kela wrote:
>>>> Currently, smc/hvc calls are made with parameters set
>>>> to zeros. We are using multiple scmi instances within
>>>> a VM. We are sharing the same smc-id(func_id) with all
>>>> scmi instance. The hypervisor needs a way to distinguish
>>>> among hvc calls made from different instances.
>>>>
>>>> This patch series introduces new compatible string which
>>>> can be used to pass shmem channel address as parameters
>>>> to smc/hvc calls.
>>>>
>>>> [...]
>>> Applied to sudeep.holla/linux (for-next/scmi/updates), thanks!
>> Hi Sudeep, our hypervisor team is evaluating other scmi transport
>> options(including new qcom specific transport) along with this one so there
>> is a possibility that we might not use this solution. If you think this
>> patch is not useful to others, you can hold off its merge. Sorry about the
>> last minute inconvenience.
> Firstly, not sure why you took this in private. I am going to reply on the
> list and from now on I will never trust or rush to take any Qualcomm changes.
> Nothing personal but I have to follow that to keep it simple. It is in
> Linux tree yesterday or today and yes it is too late.
I understand your frustration and trust me I am even more disappointed 
by the decision by our hypervisor team and that too this late.  My 
efforts on this series are all wasted. If you like me to post a revert 
of this patch series, I will be happy to do that. Please don't let this 
one example reflect whole Qualcomm culture. Again, extremely sorry about 
all the efforts you put in.
>

      parent reply	other threads:[~2023-07-04 19:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 18:24 Nikunj Kela
2023-05-06 18:24 ` [PATCH v5 1/2] dt-bindings: firmware: arm,scmi: support for parameter in smc/hvc call Nikunj Kela
2023-05-08 17:47   ` Florian Fainelli
2023-05-06 18:24 ` [PATCH v5 2/2] firmware: arm_scmi: Augment SMC/HVC to allow optional parameters Nikunj Kela
2023-05-08 17:46   ` Florian Fainelli
2023-05-09 16:01 ` [PATCH v5 0/2] Allow parameter in smc/hvc calls Sudeep Holla
2023-05-31 12:26 ` Sudeep Holla
     [not found]   ` <110da0da-211d-1a3f-e007-ddab272aece7@quicinc.com>
     [not found]     ` <20230630094441.fxwd4eagtj5wmbbg@bogus>
2023-06-30 15:14       ` Nikunj Kela [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=0c9e5d7e-effc-6601-bc09-98ca74479833@quicinc.com \
    --to=quic_nkela@quicinc.com \
    --cc=sudeep.holla@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®