[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200804064154.GE696690@kroah.com>
Date: Tue, 4 Aug 2020 08:41:54 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Daniel Gutson <daniel@...ypsium.com>
Cc: Derek Kiernan <derek.kiernan@...inx.com>,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Arnd Bergmann <arnd@...db.de>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Richard Hughes <hughsient@...il.com>,
Alex Bazhaniuk <alex@...ypsium.com>
Subject: Re: [PATCH] Platform lockdown information in SYSFS
On Mon, Aug 03, 2020 at 07:04:56PM -0300, Daniel Gutson wrote:
> > > > Think of this as an input device. You don't put the random input
> > > > attributes all in one place, you create a new device that represents the
> > > > input interface and register that.
>
> I'm having trouble with this. What's the dev_t for the child devices?
> I'm doing
> child_device = device_create(&my_class, &pdev->dev, MKDEV(0, 0),
> NULL, "child");
> pdev is the pci_device (intel-spi-pci)
> dmesg shows
>
> sysfs: cannot create duplicate filename '/class/my-class'
> (call trace)
> kobject_add_internal failed for my-class with -EEXIST, don't try
> to register things with the same name in the same directory.
Without seeing all of your code, I can't tell you what you are doing
wrong, but the kernel should be giving you a huge hint here...
Don't create duplicate names in the same subdirectory.
thanks,
greg k-h
Powered by blists - more mailing lists