From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mailbox: add support for doorbell/signal mode controllers
Date: Thu, 2 Nov 2017 11:49:17 +0000 [thread overview]
Message-ID: <5af1c28f-50db-9f5a-2c60-71cacab4a3ab@arm.com> (raw)
In-Reply-To: <CABb+yY3Gd3u-_xNPSqJT_+yVHGMs7pgt3Bc4faGvN2KwOsm6_w@mail.gmail.com>
On 02/11/17 11:26, Jassi Brar wrote:
> On Thu, Nov 2, 2017 at 4:17 PM, Sudeep Holla <sudeep.holla@arm.com> wrote:
[...]
>>
>> No that non-zero value is not client specific, it's entirely controller
>> specific.
>>
> ??
> For example BCM2835 has such a controller. Have a look at
> bcm2835_send_data() and let me know what is that controller specific
> value.
>
You can keep finding one or the other platform that has a deviation.
Come on there are generic infrastructure support in many subsystem that
are just used in one or two platforms. I hope you agree for this
enhancement to the mailbox framework as it's more commonly used mode.
I am not saying this patch is final, but I just want an agreement to add
such a support.
[...]
>>> 1) Where does the "whatever_value_to_trigger_signal" come from?
>>
>> Controller specific.
>>
>>> That has to come from client.
>>
>> No.
>>
> Again, let me know what does the controller expect 'val' to be
>
> writel(val, MAILBOX_A2B_CMD(chans->idx))
>
It depends on the controller. Whatever value that can generate a signal
to remote.
>
> Your entire post is based on your assertion that the controller
> expects a particular non-zero value to trigger a signal, which is
> wrong.
Why do you think that ? There are lots of example in the mailbox today.
Please have a look at few example which don't use data passed from the
client:
1. pcc_send_data (drivers/mailbox/pcc.c)
2. sti_mbox_send_data (drivers/mailbox/mailbox-sti.c)
3. qcom_apcs_ipc_send_data (drivers/mailbox/qcom-apcs-ipc-mailbox.c)
4. tegra_hsp_doorbell_send_data (drivers/mailbox/tegra-hsp.c)
And SCMI fits the above case.
Also you keep saying I am making this change to get SCMI with ARM MHU.
Honestly I don't care much about that, I need better support from
mailbox framework if possible for any platforms running SCMI. So please
stop assuming my changes are motivated by that. SCMI is designed to
solve more generic consolidation issues, so I am more focused on that
than getting it run on some development platform I have with ARM MHU.
Believe me that's least of my concern.
--
Regards,
Sudeep
next prev parent reply other threads:[~2017-11-02 11:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 16:32 [PATCH] mailbox: add support for doorbell/signal mode controllers Sudeep Holla
2017-11-01 18:03 ` Jassi Brar
2017-11-01 18:15 ` Sudeep Holla
2017-11-01 22:17 ` Bjorn Andersson
2017-11-02 3:02 ` Jassi Brar
2017-11-02 3:27 ` Bjorn Andersson
2017-11-02 4:48 ` Jassi Brar
2017-11-02 2:39 ` Jassi Brar
2017-11-02 10:47 ` Sudeep Holla
2017-11-02 11:26 ` Jassi Brar
2017-11-02 11:49 ` Sudeep Holla [this message]
2017-11-02 12:21 ` Jassi Brar
2017-11-02 12:37 ` Sudeep Holla
2017-11-02 14:52 ` Jassi Brar
2017-11-01 22:12 ` Bjorn Andersson
2017-11-02 2:56 ` Jassi Brar
2017-11-02 10:51 ` 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=5af1c28f-50db-9f5a-2c60-71cacab4a3ab@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).