From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Varka Bhadram <varkabhadram@gmail.com>,
<santosh.shilimkar@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
<linux-gpio@vger.kernel.org>
Cc: <ivan.khoronzhuk@ti.com>, <m-karicheri2@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] gpio: keystone: add dsp gpio controller driver
Date: Mon, 21 Jul 2014 17:20:11 +0300 [thread overview]
Message-ID: <53CD219B.1060306@ti.com> (raw)
In-Reply-To: <53C64E78.4030506@gmail.com>
Hi Varka Bhadram,
On 07/16/2014 01:05 PM, Varka Bhadram wrote:
> On 07/16/2014 04:13 PM, Grygorii Strashko 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>
>> ---
>> .../devicetree/bindings/gpio/gpio-keystone.txt | 43 ++++++
>> drivers/gpio/Kconfig | 8 ++
>> drivers/gpio/Makefile | 1 +
>> drivers/gpio/gpio-keystone.c | 138
>> ++++++++++++++++++++
>> 4 files changed, 190 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/gpio/gpio-keystone.txt
>> create mode 100644 drivers/gpio/gpio-keystone.c
>>
>> diff --git a/Documentation/devicetree/bindings/gpio/gpio-keystone.txt
>> b/Documentation/devicetree/bindings/gpio/gpio-keystone.txt
>> new file mode 100644
>> index 0000000..4f92af4
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/gpio/gpio-keystone.txt
>> @@ -0,0 +1,43 @@
>> +Keystone 2 DSP GPIO controller bindings
>> +
>> +HOST OS userland running on ARM can send interrupts to DSP cores using
>> +the DSP GPIO controller IP. It provides 28 IRQ signals per each DSP
>> core.
>> +This is one of the component used by the IPC mechanism used on
>> Keystone SOCs.
>> +
>> +For example TCI6638K2K SoC has 8 DSP GPIO controllers:
>> + - 8 for C66x CorePacx CPUs 0-7
>> +
>> +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.
>> +
>> +Required Properties:
>> +- compatible: should be "ti,keystone-dsp-gpio"
>> +
>> +- ti,syscon-dev: phandle/offset pair. The phandle to syscon used to
>> + access device state control registers and the offset
>> + in order to use block of device's specific registers.
>> +
>> +- gpio-controller : Marks the device node as a gpio controller.
>> +
>> +- #gpio-cells : Should be one.
>> + See gpio.txt in this directory for a of the cells format
>
> All the properties not properly aligned. It would be more readable if
>
> Required Properties:
> - compatible : should be "ti,keystone-dsp-gpio"
> - ti,syscon-dev : phandle/offset pair. The phandle to syscon used to
> access device state control registers and the offset
> in order to use block of device's specific registers.
> - gpio-controller : Marks the device node as a gpio controller.
> - #gpio-cells : Should be one.
> See gpio.txt in this directory for a of the cells format
Unfortunately, the format of DT bindings description is not
standardized, but i will try to beautify it :)
>
>> +
>> +Please refer to gpio.txt in this directory for details of the common
>> GPIO
>> +bindings used by client devices.
>> +
>
> (...)
>
>> +static struct platform_driver keystone_gpio_driver = {
>> + .probe = keystone_gpio_probe,
>> + .remove = keystone_gpio_remove,
>> + .driver = {
>> + .name = "keystone-dsp-gpio",
>> + .owner = THIS_MODULE,
>
> We can drop owner field... :-) .It will update by module_platform_driver
>
>
Thanks for your comments - I'll wait a bit and re-send.
Regards,
- grygorii
next prev parent reply other threads:[~2014-07-21 13:35 UTC|newest]
Thread overview: 14+ 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:05 ` Varka Bhadram
2014-07-21 14:20 ` Grygorii Strashko [this message]
2014-07-23 15:10 ` Linus Walleij
2014-07-23 15:25 ` Santosh Shilimkar
2014-07-24 14:12 ` Linus Walleij
2014-07-24 14:21 ` Santosh Shilimkar
2014-07-24 15:23 ` Linus Walleij
2014-07-24 15:40 ` Santosh Shilimkar
2014-07-24 17:19 ` Jassi Brar
2014-07-24 17:22 ` Santosh Shilimkar
2014-07-24 18:12 ` Jassi Brar
2014-07-24 18:52 ` Suman Anna
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=53CD219B.1060306@ti.com \
--to=grygorii.strashko@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ivan.khoronzhuk@ti.com \
--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=santosh.shilimkar@ti.com \
--cc=varkabhadram@gmail.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;
as well as URLs for NNTP newsgroup(s).