From mboxrd@z Thu Jan 1 00:00:00 1970 From: vigneshr@ti.com (Vignesh R) Date: Wed, 15 Mar 2017 17:12:17 +0530 Subject: [PATCH] serial: 8250: 8250_core: Use dev_name() during request_irq() In-Reply-To: References: <20170308121943.29340-1-vigneshr@ti.com> <2a0cf043-6e3f-6807-0794-d9d6f46b77f5@ti.com> Message-ID: <01911ed2-d64b-6f81-5ca2-7efa9b63d70f@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tuesday 14 March 2017 09:29 PM, Andy Shevchenko wrote: > On Tue, Mar 14, 2017 at 3:44 PM, Vignesh R wrote: >> On Monday 13 March 2017 01:35 AM, Andy Shevchenko wrote: >>> On Wed, Mar 8, 2017 at 2:19 PM, Vignesh R 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. > > (The world is not DT-centric) > >>> 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? > > Yes. > Ok thanks, I will send on incremental fix as this patch is already applied. -- Regards Vignesh