All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rob Herring <robh@kernel.org>,
	Alexey Klimov <alexey.klimov@arm.com>, Loc Ho <lho@apm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	"arnd@arndb.de" <arnd@arndb.de>,
	Jassi Brar <jaswinder.singh@linaro.org>,
	Roy Franz <roy.franz@cavium.com>,
	Harb Abdulhamid <harba@codeaurora.org>,
	Matt Sealey <neko@bakuhatsu.net>,
	ALKML <linux-arm-kernel@lists.infradead.org>,
	DTML <devicetree@vger.kernel.org>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH 3/9] firmware: arm_scmi: add basic driver infrastructure for SCMI
Date: Mon, 24 Jul 2017 17:21:38 +0100	[thread overview]
Message-ID: <cd935dab-06b8-a91b-d393-cfc2f085c600@arm.com> (raw)
In-Reply-To: <CABb+yY3NNUE7YXAhBLpMzVZkB7Kgx6iZk8a--crHa9Wpw6Ls4Q@mail.gmail.com>



On 24/07/17 16:41, Jassi Brar wrote:
> On Mon, Jul 24, 2017 at 3:20 PM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>
>>
>> On 08/07/17 06:32, Jassi Brar wrote:
>>> Hi Roy, Matt, Nishant, Harb Abdulhamid, Loc,
>>>
>>> I have a gut feeling you guys were part of the SCMI spec committee. If
>>> so, could you please chime in?
>>>
>>
>> I take complete silence as no objection.
>>
> I take it as no self respecting developer/architect would stand by
> your FUBAR implementation of SCMI.
>

Wow really ? This is exactly how ACPI PCC works today IIUC.

> SCMI  calls
>     mbox_send_message(struct mbox_chan *chan, struct scmi_xfer *xfer);
> 
> whereas the API expects
>     mbox_send_message(struct mbox_chan *chan, struct controller_specific *xfer);
> 

That's not hard to change but you seem to have combined my ARM MHU
changes into this which is totally wrong and now I say also stupid after
mentioning the same thing so many times. Consider them independently and
try to understand.

> As the maintainer I have tried to explain it to you in a dozen ways.
> If you still can't see how it's broken, you can't be helped.
> 

Sorry but you wanted driver to explain initially. I posted them. But you
haven't answer my specific questions yet.

-- 
Regards,
Sudeep

WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>
To: Jassi Brar <jassisinghbrar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org>,
	Linux Kernel Mailing List
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Alexey Klimov <alexey.klimov-5wv7dgnIgG8@public.gmane.org>,
	Loc Ho <lho-qTEPVZfXA3Y@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	"arnd-r2nGTMty4D4@public.gmane.org"
	<arnd-r2nGTMty4D4@public.gmane.org>,
	Jassi Brar
	<jaswinder.singh-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Roy Franz <roy.franz-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
	Harb Abdulhamid <harba-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	Matt Sealey <neko-HhXTZounMxbZATc7fWT8Dg@public.gmane.org>,
	ALKML
	<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	DTML <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH 3/9] firmware: arm_scmi: add basic driver infrastructure for SCMI
Date: Mon, 24 Jul 2017 17:21:38 +0100	[thread overview]
Message-ID: <cd935dab-06b8-a91b-d393-cfc2f085c600@arm.com> (raw)
In-Reply-To: <CABb+yY3NNUE7YXAhBLpMzVZkB7Kgx6iZk8a--crHa9Wpw6Ls4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>



On 24/07/17 16:41, Jassi Brar wrote:
> On Mon, Jul 24, 2017 at 3:20 PM, Sudeep Holla <sudeep.holla-5wv7dgnIgG8@public.gmane.org> wrote:
>>
>>
>> On 08/07/17 06:32, Jassi Brar wrote:
>>> Hi Roy, Matt, Nishant, Harb Abdulhamid, Loc,
>>>
>>> I have a gut feeling you guys were part of the SCMI spec committee. If
>>> so, could you please chime in?
>>>
>>
>> I take complete silence as no objection.
>>
> I take it as no self respecting developer/architect would stand by
> your FUBAR implementation of SCMI.
>

Wow really ? This is exactly how ACPI PCC works today IIUC.

> SCMI  calls
>     mbox_send_message(struct mbox_chan *chan, struct scmi_xfer *xfer);
> 
> whereas the API expects
>     mbox_send_message(struct mbox_chan *chan, struct controller_specific *xfer);
> 

That's not hard to change but you seem to have combined my ARM MHU
changes into this which is totally wrong and now I say also stupid after
mentioning the same thing so many times. Consider them independently and
try to understand.

> As the maintainer I have tried to explain it to you in a dozen ways.
> If you still can't see how it's broken, you can't be helped.
> 

Sorry but you wanted driver to explain initially. I posted them. But you
haven't answer my specific questions yet.

-- 
Regards,
Sudeep
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/9] firmware: arm_scmi: add basic driver infrastructure for SCMI
Date: Mon, 24 Jul 2017 17:21:38 +0100	[thread overview]
Message-ID: <cd935dab-06b8-a91b-d393-cfc2f085c600@arm.com> (raw)
In-Reply-To: <CABb+yY3NNUE7YXAhBLpMzVZkB7Kgx6iZk8a--crHa9Wpw6Ls4Q@mail.gmail.com>



On 24/07/17 16:41, Jassi Brar wrote:
> On Mon, Jul 24, 2017 at 3:20 PM, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>
>>
>> On 08/07/17 06:32, Jassi Brar wrote:
>>> Hi Roy, Matt, Nishant, Harb Abdulhamid, Loc,
>>>
>>> I have a gut feeling you guys were part of the SCMI spec committee. If
>>> so, could you please chime in?
>>>
>>
>> I take complete silence as no objection.
>>
> I take it as no self respecting developer/architect would stand by
> your FUBAR implementation of SCMI.
>

Wow really ? This is exactly how ACPI PCC works today IIUC.

> SCMI  calls
>     mbox_send_message(struct mbox_chan *chan, struct scmi_xfer *xfer);
> 
> whereas the API expects
>     mbox_send_message(struct mbox_chan *chan, struct controller_specific *xfer);
> 

That's not hard to change but you seem to have combined my ARM MHU
changes into this which is totally wrong and now I say also stupid after
mentioning the same thing so many times. Consider them independently and
try to understand.

> As the maintainer I have tried to explain it to you in a dozen ways.
> If you still can't see how it's broken, you can't be helped.
> 

Sorry but you wanted driver to explain initially. I posted them. But you
haven't answer my specific questions yet.

-- 
Regards,
Sudeep

  reply	other threads:[~2017-07-24 16:21 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 15:55 [PATCH 0/9] firmware: ARM System Control and Management Interface(SCMI) support Sudeep Holla
2017-06-26 15:55 ` Sudeep Holla
2017-06-26 15:55 ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 1/9] Documentation: dt-bindings: add support for mailbox client shared memory Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-28 22:56   ` Rob Herring
2017-06-28 22:56     ` Rob Herring
2017-06-28 22:56     ` Rob Herring
2017-06-30 10:24     ` Sudeep Holla
2017-06-30 10:24       ` Sudeep Holla
2017-06-30 10:24       ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 2/9] Documentation: add DT binding for ARM System Control and Management Interface(SCMI) protocol Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-28 23:04   ` Rob Herring
2017-06-28 23:04     ` Rob Herring
2017-06-28 23:04     ` Rob Herring
2017-06-30 10:31     ` Sudeep Holla
2017-06-30 10:31       ` Sudeep Holla
2017-06-30 10:31       ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 3/9] firmware: arm_scmi: add basic driver infrastructure for SCMI Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-07-07 16:52   ` Jassi Brar
2017-07-07 17:39     ` Sudeep Holla
2017-07-07 17:39       ` Sudeep Holla
2017-07-07 17:39       ` Sudeep Holla
2017-07-08  5:32       ` Jassi Brar
2017-07-08  5:32         ` Jassi Brar
2017-07-24  9:50         ` Sudeep Holla
2017-07-24  9:50           ` Sudeep Holla
2017-07-24  9:50           ` Sudeep Holla
2017-07-24 15:41           ` Jassi Brar
2017-07-24 15:41             ` Jassi Brar
2017-07-24 15:41             ` Jassi Brar
2017-07-24 16:21             ` Sudeep Holla [this message]
2017-07-24 16:21               ` Sudeep Holla
2017-07-24 16:21               ` Sudeep Holla
2017-07-24 17:21               ` Jassi Brar
2017-07-24 17:21                 ` Jassi Brar
2017-07-24 17:21                 ` Jassi Brar
2017-07-24 17:30                 ` Sudeep Holla
2017-07-24 17:30                   ` Sudeep Holla
2017-07-24 17:30                   ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 4/9] firmware: arm_scmi: add common infrastructure and support for base protocol Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 5/9] firmware: arm_scmi: add initial support for performance protocol Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 6/9] firmware: arm_scmi: add initial support for clock protocol Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 7/9] firmware: arm_scmi: add initial support for power protocol Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 8/9] firmware: arm_scmi: add initial support for sensor protocol Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla
2017-06-26 15:55 ` [PATCH 9/9] firmware: arm_scmi: probe and initialise all the supported protocols Sudeep Holla
2017-06-26 15:55   ` Sudeep Holla

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=cd935dab-06b8-a91b-d393-cfc2f085c600@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=alexey.klimov@arm.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=harba@codeaurora.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=lho@apm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=neko@bakuhatsu.net \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=roy.franz@cavium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.