From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Jassi Brar <jaswinder.singh@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Suman Anna <s-anna@ti.com>, Alexander Shiyan <shc_work@mail.ru>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
ivan.khoronzhuk@ti.com,
Muralidharan Karicheri <m-karicheri2@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] gpio: keystone: add dsp gpio controller driver
Date: Thu, 24 Jul 2014 13:22:52 -0400 [thread overview]
Message-ID: <53D140EC.9020609@ti.com> (raw)
In-Reply-To: <CAJe_ZhdnjyjvEsvK2u7SgS1hJ2fpsXh+=ViGhzakRd+c4ReBaw@mail.gmail.com>
On Thursday 24 July 2014 01:19 PM, Jassi Brar wrote:
> On 23 July 2014 20:40, Linus Walleij <linus.walleij@linaro.org> wrote:
>> On Wed, Jul 16, 2014 at 12:43 PM, Grygorii Strashko
>> <grygorii.strashko@ti.com> wrote:
>>
>>> From: Murali Karicheri <m-karicheri2@ti.com>
>>>
>>> On Keystone SOCs, ARM host can send interrupts to DSP cores using the
>>> DSP GPIO controller IP. Each DSP GPIO controller provides 28 IRQ signals for
>>> each DSP core. This is one of the component used by the IPC mechanism used
>>> on Keystone SOCs.
>>>
>>> Keystone 2 DSP GPIO controller has specific features:
>>> - each GPIO can be configured only as output pin;
>>> - setting GPIO value to 1 causes IRQ generation on target DSP core;
>>> - reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still
>>> pending.
>>>
>>> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>>
>> Pardon me. How is this GENERAL PURPOSE Input/Output?
>>
>> It seems very very much SPECIAL PURPOSE to me, it's like
>> you're just shoehorning some IPC mechanism into the GPIO
>> subsystem, and this may be because the datasheet calls it
>> GPIO when it's not.
>>
>> What other stuff than DSP is connected to these lines, and is it
>> really even external lines? Aren't these just polysilicon rails
>> pretty much hammered to be used by the DSP and nothing else.
>>
>> What is the difference between this and a mailbox IRQ line
>> and the kind of stuff handled by drivers/mailbox?
>>
>> I'd like Suman and Jassi to have a look at this to see if it's
>> actually a mailbox before we proceed.
>>
> The controller seems like most others, only incapable of reading
> signals (output only).
> The userspace driving those signals to communicate with a DSP isn't
> enough to call it a mailbox usecase, because on a different board the
> userspace may drive those signals to control LEDs :)
>
Exactly !!
And that was my point. Thanks for echo.
Regards,
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Jassi Brar <jaswinder.singh@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Suman Anna <s-anna@ti.com>, Alexander Shiyan <shc_work@mail.ru>,
Alexandre Courbot <gnurou@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
<ivan.khoronzhuk@ti.com>,
Muralidharan Karicheri <m-karicheri2@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] gpio: keystone: add dsp gpio controller driver
Date: Thu, 24 Jul 2014 13:22:52 -0400 [thread overview]
Message-ID: <53D140EC.9020609@ti.com> (raw)
In-Reply-To: <CAJe_ZhdnjyjvEsvK2u7SgS1hJ2fpsXh+=ViGhzakRd+c4ReBaw@mail.gmail.com>
On Thursday 24 July 2014 01:19 PM, Jassi Brar wrote:
> On 23 July 2014 20:40, Linus Walleij <linus.walleij@linaro.org> wrote:
>> On Wed, Jul 16, 2014 at 12:43 PM, Grygorii Strashko
>> <grygorii.strashko@ti.com> wrote:
>>
>>> From: Murali Karicheri <m-karicheri2@ti.com>
>>>
>>> On Keystone SOCs, ARM host can send interrupts to DSP cores using the
>>> DSP GPIO controller IP. Each DSP GPIO controller provides 28 IRQ signals for
>>> each DSP core. This is one of the component used by the IPC mechanism used
>>> on Keystone SOCs.
>>>
>>> Keystone 2 DSP GPIO controller has specific features:
>>> - each GPIO can be configured only as output pin;
>>> - setting GPIO value to 1 causes IRQ generation on target DSP core;
>>> - reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still
>>> pending.
>>>
>>> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>>
>> Pardon me. How is this GENERAL PURPOSE Input/Output?
>>
>> It seems very very much SPECIAL PURPOSE to me, it's like
>> you're just shoehorning some IPC mechanism into the GPIO
>> subsystem, and this may be because the datasheet calls it
>> GPIO when it's not.
>>
>> What other stuff than DSP is connected to these lines, and is it
>> really even external lines? Aren't these just polysilicon rails
>> pretty much hammered to be used by the DSP and nothing else.
>>
>> What is the difference between this and a mailbox IRQ line
>> and the kind of stuff handled by drivers/mailbox?
>>
>> I'd like Suman and Jassi to have a look at this to see if it's
>> actually a mailbox before we proceed.
>>
> The controller seems like most others, only incapable of reading
> signals (output only).
> The userspace driving those signals to communicate with a DSP isn't
> enough to call it a mailbox usecase, because on a different board the
> userspace may drive those signals to control LEDs :)
>
Exactly !!
And that was my point. Thanks for echo.
Regards,
Santosh
next prev parent reply other threads:[~2014-07-24 17:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 10:43 [PATCH v1] gpio: keystone: add dsp gpio controller driver Grygorii Strashko
2014-07-16 10:43 ` Grygorii Strashko
2014-07-16 10:05 ` Varka Bhadram
2014-07-21 14:20 ` Grygorii Strashko
2014-07-21 14:20 ` Grygorii Strashko
2014-07-23 15:10 ` Linus Walleij
2014-07-23 15:19 ` Alexander Shiyan
2014-08-11 16:06 ` Grygorii Strashko
2014-08-11 15:26 ` Alexander Shiyan
[not found] ` <CACRpkdYY_a_9G-VLBbv2a22Cg4j0t3Wv4W1h0n6-ccCXgVJXsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-23 15:25 ` Santosh Shilimkar
2014-07-23 15:25 ` Santosh Shilimkar
2014-07-24 14:12 ` Linus Walleij
2014-07-24 14:21 ` Santosh Shilimkar
2014-07-24 14:21 ` Santosh Shilimkar
2014-07-24 15:23 ` Linus Walleij
[not found] ` <CACRpkdbBeySnCBD4H2bBmievHYyPabL8sKXKiBp-D6PtNTV9YQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-24 15:40 ` Santosh Shilimkar
2014-07-24 15:40 ` Santosh Shilimkar
2014-07-24 17:19 ` Jassi Brar
2014-07-24 17:22 ` Santosh Shilimkar [this message]
2014-07-24 17:22 ` Santosh Shilimkar
2014-07-24 18:12 ` Jassi Brar
2014-07-24 18:52 ` Suman Anna
2014-07-24 18:52 ` Suman Anna
2014-07-24 23:41 ` Santosh Shilimkar
2014-07-24 23:41 ` Santosh Shilimkar
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=53D140EC.9020609@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=ivan.khoronzhuk@ti.com \
--cc=jaswinder.singh@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=shc_work@mail.ru \
/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.