From: Jisheng Zhang <jszhang@marvell.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Vignesh R <vigneshr@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Jiri Slaby <jslaby@suse.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] serial: 8250: 8250_core: Use dev_name() during request_irq()
Date: Wed, 15 Mar 2017 14:10:01 +0800 [thread overview]
Message-ID: <20170315141001.62c4fc67@xhacker> (raw)
In-Reply-To: <CAHp75Vc0Ap53s=6SU2o5QjgdaBDWKC24bym7HUt6jQ69HrpdCg@mail.gmail.com>
On Tue, 14 Mar 2017 17:59:01 +0200 Andy Shevchenko wrote:
> On Tue, Mar 14, 2017 at 3:44 PM, Vignesh R <vigneshr@ti.com> wrote:
> > 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
>
> > But, this change is making interrupt name more descriptive
>
> It doesn't in PCI case, it makes it worse.
indeed, in PCI case, I see
4: ... 00:03.3
what about "dev_driver_string(up->port.dev)[dev_name(up->port.dev)]" as
we did for ahci case?
Thanks
WARNING: multiple messages have this Message-ID (diff)
From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] serial: 8250: 8250_core: Use dev_name() during request_irq()
Date: Wed, 15 Mar 2017 14:10:01 +0800 [thread overview]
Message-ID: <20170315141001.62c4fc67@xhacker> (raw)
In-Reply-To: <CAHp75Vc0Ap53s=6SU2o5QjgdaBDWKC24bym7HUt6jQ69HrpdCg@mail.gmail.com>
On Tue, 14 Mar 2017 17:59:01 +0200 Andy Shevchenko wrote:
> On Tue, Mar 14, 2017 at 3:44 PM, Vignesh R <vigneshr@ti.com> wrote:
> > 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
>
> > But, this change is making interrupt name more descriptive
>
> It doesn't in PCI case, it makes it worse.
indeed, in PCI case, I see
4: ... 00:03.3
what about "dev_driver_string(up->port.dev)[dev_name(up->port.dev)]" as
we did for ahci case?
Thanks
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@marvell.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Vignesh R <vigneshr@ti.com>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Jiri Slaby <jslaby@suse.com>
Subject: Re: [PATCH] serial: 8250: 8250_core: Use dev_name() during request_irq()
Date: Wed, 15 Mar 2017 14:10:01 +0800 [thread overview]
Message-ID: <20170315141001.62c4fc67@xhacker> (raw)
In-Reply-To: <CAHp75Vc0Ap53s=6SU2o5QjgdaBDWKC24bym7HUt6jQ69HrpdCg@mail.gmail.com>
On Tue, 14 Mar 2017 17:59:01 +0200 Andy Shevchenko wrote:
> On Tue, Mar 14, 2017 at 3:44 PM, Vignesh R <vigneshr@ti.com> wrote:
> > 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
>
> > But, this change is making interrupt name more descriptive
>
> It doesn't in PCI case, it makes it worse.
indeed, in PCI case, I see
4: ... 00:03.3
what about "dev_driver_string(up->port.dev)[dev_name(up->port.dev)]" as
we did for ahci case?
Thanks
next prev parent reply other threads:[~2017-03-15 6:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 12:19 [PATCH] serial: 8250: 8250_core: Use dev_name() during request_irq() Vignesh R
2017-03-08 12:19 ` Vignesh R
2017-03-08 12:19 ` Vignesh R
2017-03-08 12:34 ` Greg Kroah-Hartman
2017-03-08 12:34 ` Greg Kroah-Hartman
2017-03-09 14:37 ` Vignesh R
2017-03-09 14:37 ` Vignesh R
2017-03-09 14:37 ` Vignesh R
2017-03-12 20:05 ` Andy Shevchenko
2017-03-12 20:05 ` Andy Shevchenko
2017-03-14 13:44 ` Vignesh R
2017-03-14 13:44 ` Vignesh R
2017-03-14 13:44 ` Vignesh R
2017-03-14 15:59 ` Andy Shevchenko
2017-03-14 15:59 ` Andy Shevchenko
2017-03-15 6:10 ` Jisheng Zhang [this message]
2017-03-15 6:10 ` Jisheng Zhang
2017-03-15 6:10 ` Jisheng Zhang
2017-03-15 11:42 ` Vignesh R
2017-03-15 11:42 ` Vignesh R
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=20170315141001.62c4fc67@xhacker \
--to=jszhang@marvell.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 \
--cc=vigneshr@ti.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 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.