On Tue, Oct 14, 2014 at 4:53 AM, Mark Roszko wrote:
>
> > If this limitations exists
> >they are not introduced by this patch. This patch just exposes the
> >frequency so that it can be read or changed in userspace.
>
> Ah, well right now you can have an i2c bus with driver 1 and 2. Say
> the i2c
On Tue, Oct 14, 2014 at 4:53 AM, Mark Roszko mark.ros...@gmail.com wrote:
If this limitations exists
they are not introduced by this patch. This patch just exposes the
frequency so that it can be read or changed in userspace.
Ah, well right now you can have an i2c bus with driver 1 and 2.
> If this limitations exists
>they are not introduced by this patch. This patch just exposes the
>frequency so that it can be read or changed in userspace.
Ah, well right now you can have an i2c bus with driver 1 and 2. Say
the i2c bus is configured for 60khz in kernel space which normally
can't
On Sun, Oct 12, 2014 at 8:06 PM, Guenter Roeck wrote:
> On Sun, Oct 12, 2014 at 12:32:56PM +0300, Octavian Purdila wrote:
>> On Sat, Oct 11, 2014 at 11:14 PM, Mark Roszko wrote:
>>
>> > This seems limiting to arches with peripherals that can support a range of
>> > frequencies rather than fixed
On Sun, Oct 12, 2014 at 8:06 PM, Guenter Roeck li...@roeck-us.net wrote:
On Sun, Oct 12, 2014 at 12:32:56PM +0300, Octavian Purdila wrote:
On Sat, Oct 11, 2014 at 11:14 PM, Mark Roszko mark.ros...@gmail.com wrote:
This seems limiting to arches with peripherals that can support a range of
If this limitations exists
they are not introduced by this patch. This patch just exposes the
frequency so that it can be read or changed in userspace.
Ah, well right now you can have an i2c bus with driver 1 and 2. Say
the i2c bus is configured for 60khz in kernel space which normally
can't be
On Sun, Oct 12, 2014 at 12:32:56PM +0300, Octavian Purdila wrote:
> On Sat, Oct 11, 2014 at 11:14 PM, Mark Roszko wrote:
>
> > This seems limiting to arches with peripherals that can support a range of
> > frequencies rather than fixed numbers.
> > Also it creates some portability quirkiness
On Sat, Oct 11, 2014 at 11:14 PM, Mark Roszko wrote:
> This seems limiting to arches with peripherals that can support a range of
> frequencies rather than fixed numbers.
> Also it creates some portability quirkiness between platforms when all the
> i2c bus drivers have different supported freq
On Sat, Oct 11, 2014 at 11:14 PM, Mark Roszko mark.ros...@gmail.com wrote:
This seems limiting to arches with peripherals that can support a range of
frequencies rather than fixed numbers.
Also it creates some portability quirkiness between platforms when all the
i2c bus drivers have
On Sun, Oct 12, 2014 at 12:32:56PM +0300, Octavian Purdila wrote:
On Sat, Oct 11, 2014 at 11:14 PM, Mark Roszko mark.ros...@gmail.com wrote:
This seems limiting to arches with peripherals that can support a range of
frequencies rather than fixed numbers.
Also it creates some portability
This patch adds two new sysfs files, bus_frequency and
bus_supported_frequencies which allows the user to view or change the
bus frequency on a per bus level.
This is required for e.g. USB I2C buses where we can have multiple
device plugged in a system and where a module parameter does not allow
This patch adds two new sysfs files, bus_frequency and
bus_supported_frequencies which allows the user to view or change the
bus frequency on a per bus level.
This is required for e.g. USB I2C buses where we can have multiple
device plugged in a system and where a module parameter does not allow
12 matches
Mail list logo
