mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vignesh R <vigneshr@ti.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] serial: 8250: 8250_core: Use dev_name() during request_irq()
Date: Tue, 14 Mar 2017 19:14:19 +0530	[thread overview]
Message-ID: <2a0cf043-6e3f-6807-0794-d9d6f46b77f5@ti.com> (raw)
In-Reply-To: <CAHp75VeFKSbk9hvoJXdK6uOz+JYATD8D057iNv0JDuEnBFS=yw@mail.gmail.com>



On Monday 13 March 2017 01:35 AM, Andy Shevchenko wrote:
> On Wed, Mar 8, 2017 at 2:19 PM, Vignesh R <vigneshr@ti.com> wrote:
>> Passing "serial" as name during request_irq() results in all serial port
>> irqs have same name. This does not help much to easily identify which
>> irq belongs to which serial port instance. Therefore pass dev_name()
>> during request_irq() so that better identifiable name is listed for
>> serial ports in cat /proc/interrupts output.
>>
>> Output of cat /proc/interrupts
>> Before this patch:
>>  26:        689          0     GICv2 309 Edge      serial
>> After this patch:
>>  26:        696          0     GICv2 309 Edge      2530c00.serial
> 
> I don't know if it worth to mention that some (testing) tools may
> depend on this name.

I wonder how such tools will distinguish b/w different serial device
instances. But, this change is making interrupt name more descriptive
and maybe help test tools to distinguish irqs more easily

> Besides that imagine what would be the name of PCI device here. 
> I would suggest adding ID if you need one in a form like
> "serial%d", where ID may or may not be supplied by the actual 8250 drivers.
> 

Are you suggesting to use serial_index() as ID?

>>
>> Signed-off-by: Vignesh R <vigneshr@ti.com>
>> ---
>>  drivers/tty/serial/8250/8250_core.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/tty/serial/8250/8250_core.c b/drivers/tty/serial/8250/8250_core.c
>> index 76e03a7de9cc..f83b69f30987 100644
>> --- a/drivers/tty/serial/8250/8250_core.c
>> +++ b/drivers/tty/serial/8250/8250_core.c
>> @@ -218,7 +218,7 @@ static int serial_link_irq_chain(struct uart_8250_port *up)
>>                 spin_unlock_irq(&i->lock);
>>                 irq_flags |= up->port.irqflags;
>>                 ret = request_irq(up->port.irq, serial8250_interrupt,
>> -                                 irq_flags, "serial", i);
>> +                                 irq_flags, dev_name(up->port.dev), i);
>>                 if (ret < 0)
>>                         serial_do_unlink(i, up);
>>         }
>> --
>> 2.11.0
>>
> 
> 
> 

-- 
Regards
Vignesh

  reply	other threads:[~2017-03-14 13:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 12:19 Vignesh R
2017-03-08 12:34 ` Greg Kroah-Hartman
2017-03-09 14:37   ` Vignesh R
2017-03-12 20:05 ` Andy Shevchenko
2017-03-14 13:44   ` Vignesh R [this message]
2017-03-14 15:59     ` Andy Shevchenko
2017-03-15  6:10       ` Jisheng Zhang
2017-03-15 11:42       ` Vignesh R

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=2a0cf043-6e3f-6807-0794-d9d6f46b77f5@ti.com \
    --to=vigneshr@ti.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.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

all inboxes | Powered by JetHome®