Mon, 11 Aug 2014 19:06:54 +0300 от Grygorii Strashko <[email protected]>:
> Hi Alexander, Linus,
>
> On 07/23/2014 06:19 PM, Alexander Shiyan wrote:
> > Wed, 23 Jul 2014 17:10:26 +0200 от Linus Walleij <[email protected]>:
> >> On Wed, Jul 16, 2014 at 12:43 PM, Grygorii Strashko
> >> <[email protected]> wrote:
> >>
> >>> From: Murali Karicheri <[email protected]>
> >>>
> >>> 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 <[email protected]>
> >>> Signed-off-by: Grygorii Strashko <[email protected]>
> > ...
> >> And if you proceed with this, please integrate it with
> >> drivers/gpio/gpio-syscon.c, I don't need more special
> >> syscons GPIO handlers.
>
> Thanks for your comments.
>
> I'm going to update it for using "gpio-syscon".
> But "gpio-syscon" driver itself will need to be modified to support our
> device specific callbacks:
> - gpiochip.set(): it should set bit 0 to 1 always to physically apply GPIO
> values
> - gpiochip.direction_output(): it should do nothing in our case, just return 0
>
> So, I'll extend struct syscon_gpio_data to support custom implementation of
> set/direction_output callbacks. Will it be ok for you?
Let's make a patch and I will test it for possible regressions.
---
N�����r��y����b�X��ǧv�^�){.n�+����{�����{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�m��������zZ+�����ݢj"��!�i
