Well the patch works (and is cleaner and uses slightly less resources
and is how it should have been done originally)...but it breaks my
current API (the path parsing will need to be modified) (parsing the
parent device name (old fromat "i2c-%d" new "i2c-%d/%d-%04x" id to
determine the parent adapter id). I can modify lsi2c to work with this
new API, and it shouldn't be too difficult. But I cant update the tool
until this is committed.

OLD:

lrwxrwxrwx 1 admin root 0 Nov 12 06:01 i2c-15 ->
../../../devices/soc.0/ffe03100.i2c/i2c-1/i2c-15
lrwxrwxrwx 1 admin root 0 Nov 12 06:01 i2c-16 ->
../../../devices/soc.0/ffe03100.i2c/i2c-1/i2c-16
lrwxrwxrwx 1 admin root 0 Nov 12 06:01 i2c-17 ->
../../../devices/soc.0/ffe03100.i2c/i2c-1/i2c-17

NEW:

lrwxrwxrwx 1 root root 0 Nov 12 05:50 i2c-15 ->
../../../devices/soc.0/ffe03100.i2c/i2c-1/1-0074/i2c-15
lrwxrwxrwx 1 root root 0 Nov 12 05:50 i2c-16 ->
../../../devices/soc.0/ffe03100.i2c/i2c-1/1-0074/i2c-16
lrwxrwxrwx 1 root root 0 Nov 12 05:50 i2c-17 ->
../../../devices/soc.0/ffe03100.i2c/i2c-1/1-0074/i2c-17

On Wed, Nov 12, 2014 at 4:42 AM, Wolfram Sang <[email protected]> wrote:
> On Wed, Nov 12, 2014 at 04:29:13AM -0800, Danielle Costantino wrote:
>> Could you send an aggregated patch, I want to be sure I test exactly
>> what is planned in the final patch (the patch says it includes part of
>> the next patch "[PATCH v2] i2c: mux: create proper topology in sysfs".
>
> ? V2 *is* the final patch :) https://patchwork.ozlabs.org/patch/408381/



-- 
- Danielle Costantino
--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to