netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Yoshihiro Kaneko <ykaneko0929@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-renesas-soc@vger.kernel.org,
	Linux-sh list <linux-sh@vger.kernel.org>
Subject: Re: [PATCH/RFC v6 net-next] ravb: Add dma queue interrupt support
Date: Wed, 2 Mar 2016 21:50:37 +0300	[thread overview]
Message-ID: <56D735FD.10605@cogentembedded.com> (raw)
In-Reply-To: <CAH1o70JpRZAKSSPGe6MYfw0OGSaC9d7jDd9D71mn9bxLSy3qtQ@mail.gmail.com>

On 03/02/2016 09:16 PM, Yoshihiro Kaneko wrote:

>>> From: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
>>>
>>> This patch supports the following interrupts.
>>>
>>> - One interrupt for multiple (timestamp, error, gPTP)
>>> - One interrupt for emac
>>> - Four interrupts for dma queue (best effort rx/tx, network control rx/tx)
>>>
>>> This patch improve efficiency of the interrupt handler by adding the
>>> interrupt handler corresponding to each interrupt source described
>>> above. Additionally, it reduces the number of times of the access to
>>> EthernetAVB IF.
>>> Also this patch prevent this driver depends on the whim of a boot loader.
>>>
>>> [ykaneko0929@gmail.com: define bit names of registers]
>>> [ykaneko0929@gmail.com: add comment for gen3 only registers]
>>> [ykaneko0929@gmail.com: fix coding style]
>>> [ykaneko0929@gmail.com: update changelog]
>>> [ykaneko0929@gmail.com: gen3: fix initialization of interrupts]
>>> [ykaneko0929@gmail.com: gen3: fix clearing interrupts]
>>> [ykaneko0929@gmail.com: gen3: add helper function for request_irq()]
>>> [ykaneko0929@gmail.com: gen3: remove IRQF_SHARED flag for request_irq()]
>>> [ykaneko0929@gmail.com: revert ravb_close() and ravb_ptp_stop()]
>>> [ykaneko0929@gmail.com: avoid calling free_irq() to non-hooked interrupts]
>>> [ykaneko0929@gmail.com: make NC/BE interrupt handler a function]
>>> [ykaneko0929@gmail.com: make timestamp interrupt handler a function]
>>> [ykaneko0929@gmail.com: timestamp interrupt is handled in multiple
>>>    interrupt handler instead of dma queue interrupt handler]
>>> Signed-off-by: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
>>> Signed-off-by: Yoshihiro Kaneko <ykaneko0929@gmail.com>
>>
>>     OK, you are very close now! Just a few comments...
>>
[...]
>>> diff --git a/drivers/net/ethernet/renesas/ravb_main.c
>>> b/drivers/net/ethernet/renesas/ravb_main.c
>>> index c936682..22ef65d 100644
>>> --- a/drivers/net/ethernet/renesas/ravb_main.c
>>> +++ b/drivers/net/ethernet/renesas/ravb_main.c
[...]
>>>
>>> +static irqreturn_t ravb_rx_tx_interrupt(int irq, void *dev_id, int
>>> ravb_queue)
>>
>>    Please, please shorten this 'ravb_queue'...
>
> I will fix it.
>
>>     Also, would make sense to rename it to ravb_dma_interrupt()...
>
> I have renamed it from ravb_dmaq_interrupt() in this version as you
> suggested in the previous review. Did you not mean it?

    Yes, I meant that, though perhaps got somewhat muddled up. Another variant 
is to call the current ravb_queue_interrupt() ravb_dma_interrupt_unlocked() 
(after adding the register reads there) calling this one ravb_dma_interrupt() 
but I don't insist on the former, ravb_queue_interrupt() is good enough as is; 
just rename this function please.

>> [...]
>>
>>     Unfortunately, I still can't do a full gen2 regression testing as both
>> Alt and Porter boards don't work with the recent kernel due to AVB_MDIO
>> stuck at 1... But perhaps such testing isn't even necessary.
>
> Thanks,
> kaneko

MBR, Sergei

  reply	other threads:[~2016-03-02 18:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 15:41 [PATCH/RFC v6 net-next] ravb: Add dma queue interrupt support Yoshihiro Kaneko
2016-02-29 20:30 ` Sergei Shtylyov
2016-03-02 18:16   ` Yoshihiro Kaneko
2016-03-02 18:50     ` Sergei Shtylyov [this message]
2016-03-07 16:27       ` Yoshihiro Kaneko
2016-03-08 17:18 ` Yoshihiro Kaneko

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=56D735FD.10605@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=davem@davemloft.net \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=ykaneko0929@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).