Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751837AbbFYJfv (ORCPT ); Thu, 25 Jun 2015 05:35:51 -0400 Received: from lb1-smtp-cloud3.xs4all.net ([194.109.24.22]:56921 "EHLO lb1-smtp-cloud3.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751197AbbFYJfn (ORCPT ); Thu, 25 Jun 2015 05:35:43 -0400 Message-ID: <1435224937.16792.19.camel@tiscali.nl> Subject: Re: [PATCHv5 2/2] mailbox: Adding driver for Xilinx LogiCORE IP mailbox. From: Paul Bolle To: Michal Simek , Moritz Fischer , jassisinghbrar@gmail.com Cc: linux-kernel@vger.kernel.org, robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, soren.brinkmann@xilinx.com, akpm@linux-foundation.org, gregkh@linuxfoundation.org, mchehab@osg.samsung.com, arnd@arndb.de, joe@perches.com, jingoohan1@gmail.com, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org Date: Thu, 25 Jun 2015 11:35:37 +0200 In-Reply-To: <558BB217.5080200@xilinx.com> References: <1435082402-29239-1-git-send-email-moritz.fischer@ettus.com> <1435082402-29239-3-git-send-email-moritz.fischer@ettus.com> <1435178205.4528.77.camel@tiscali.nl> <558BA5D4.8060903@xilinx.com> <1435217491.16792.5.camel@tiscali.nl> <558BB217.5080200@xilinx.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.3 (3.16.3-2.fc22) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1403 Lines: 36 On Thu, 2015-06-25 at 09:47 +0200, Michal Simek wrote: > It has to be platform_device somewhere for sure. > In past we had folder in arch/microblaze/platform folder. > Currently you can add this code to for example > arch/microblaze/kernel/platform.c > > But as I said I don't think it is really important. There will be a > lot > of others drivers in the kernel which can be used as platform drivers > but you are not able to find out platform_device for it. Because, like probably happens with this driver, the OF infrastructure makes sure the .probe and .remove functions will eventually called? > The important part is that driver can work as is. Sure. But I was talking about the MODULE_ALIAS() macro. Trivial as it is, since I still don't see where a "MODALIAS=platform:xilinx-mailbox" uevent could come from I still don't see the point of this line. As I asked in my first message: what breaks if this line is dropped? > Also it is quite common that users create own BSP for their custom > boards but they don't push it to mainline. I can't recall what BSP means. Anyhow, why should we care about boards not pushed into mainline? Paul Bolle -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/