[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140530125543.GA29731@lee--X1>
Date: Fri, 30 May 2014 13:55:43 +0100
From: Lee Jones <lee.jones@...aro.org>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
grant.likely@...aro.org, linus.walleij@...aro.org,
linux-i2c@...r.kernel.org
Subject: Re: [PATCH] i2c: Make I2C ID tables non-mandatory for DT'ed and/or
ACPI'ed devices
On Fri, 30 May 2014, Wolfram Sang wrote:
> On Fri, May 30, 2014 at 01:26:36PM +0100, Lee Jones wrote:
> > Currently the I2C framework insists on devices supplying an I2C ID
> > table. Many of the devices which do so unnecessarily adding quite a
> > few wasted lines to kernel code. This patch allows drivers a means
> > to 'not' supply the aforementioned table and match on either DT
> > and/or ACPI match tables instead.
> >
> > Signed-off-by: Lee Jones <lee.jones@...aro.org>
>
> Sadly, it is not that easy...
>
> > + /*
> > + * An I2C ID table is not madatory, if and only if, a suitable Device
> > + * Tree and/or ACPI match table entry is supplied for the probing
> > + * device.
> > + */
>
> That means we end up with drivers which cannot be used for run-time
> instantiation via the 'new_device'-file in sysfs. I don't like that.
Would you mind explaining that a little please? And perhaps point me
to the code?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists