On Wed, Jul 11, 2018 at 4:41 PM, Boris Brezillon
<boris.brezil...@bootlin.com> wrote:
> On Wed, 11 Jul 2018 16:01:56 +0200 Arnd Bergmann <a...@arndb.de> wrote:
>> > - the bus element is a separate object and is not implicitly described
>> >   by the master (as done in I2C). The reason is that I want to be able
>> >   to handle multiple master connected to the same bus and visible to
>> >   Linux.
>> >   In this situation, we should only have one instance of the device and
>> >   not one per master, and sharing the bus object would be part of the
>> >   solution to gracefully handle this case.
>> >   I'm not sure we will ever need to deal with multiple masters
>> >   controlling the same bus and exposed under Linux, but separating the
>> >   bus and master concept is pretty easy, hence the decision to do it
>> >   like that.
>> >   The other benefit of separating the bus and master concepts is that
>> >   master devices appear under the bus directory in sysfs.
>>
>> I'm not following here at all, sorry for missing prior discussion if this
>> was already explained. What is the "multiple master" case? Do you
>> mean multiple devices that are controlled by Linux and that each talk
>> to other devices on the same bus, multiple operating systems that
>> have talk to are able to own the bus with the kernel being one of
>> them, a controller that controls multiple independent buses,
>> or something else?
>
> I mean several masters connected to the same bus and all exposed to the
> same Linux instance. In this case, the question is, should we have X
> I3C buses exposed (X being the number of masters) or should we only
> have one?
>
> Having a bus represented as a separate object allows us to switch to
> the "one bus : X masters" representation if we need too.
...
>>
>> This feels a bit odd: so you have bus_type that can contain devices
>> of three (?) different device types: i3c_device_type, i3c_master_type
>> and i3c_busdev_type.
>>
>> Generally speaking, we don't have a lot of subsystems that even
>> use device_types. I assume that the i3c_device_type for a
>> device that corresponds to an endpoint on the bus, but I'm
>> still confused about the other two, and why they are part of
>> the same bus_type.
>
> i3c_busdev is just a virtual device representing the bus itself.
> i3c_master is representing the I3C master driving the bus. The reason
> for having a different type here is to avoid attaching this device to a
> driver but still being able to see the master controller as a device on
> the bus. And finally, i3c_device are all remote devices that can be
> accessed through a given i3c_master.
>
> This all comes from the design choice I made to represent the bus as a
> separate object in order to be able to share it between different
> master controllers exposed through the same Linux instance. Since
> master controllers are also remote devices for other controllers, we
> need to represent them.

Ok, so I think this is the most important question to resolve: do we
actually need to control multiple masters on a single bus from one OS
or not?

The problem that I see is that it breaks the tree abstraction that
we use in the dtb interface, in the driver model and in sysfs.
If we need to deal with a hardware bus structure like

              cpu
             /   \
            /     \
       platdev   platdev
           |        |
     i3c-master   i3c-master
            \      /
             \    /
            i3c-bus
             /    \
         device   device

then that abstraction no longer holds. Clearly you could build
a system like that, and if we have to support it, the i3c infrastructure
should be prepared for it, since we wouldn't be able to retrofit
it later.

What would be the point of building such a system though?
Is this for performance, failover, or something else?
IOW, what feature would we lose if we were to declare that
setup above invalid (and ensure you cannot represent it in DT)?

>> > +/**
>> > + * struct i3c_ccc_mwl - payload passed to SETMWL/GETMWL CCC
>> > + *
>> > + * @len: maximum write length in bytes
>> > + *
>> > + * The maximum write length is only applicable to SDR private messages or
>> > + * extended Write CCCs (like SETXTIME).
>> > + */
>> > +struct i3c_ccc_mwl {
>> > +       __be16 len;
>> > +} __packed;
>>
>> I would suggest only marking structures as __packed that are not already
>> naturally packed. Note that a side-effect of __packed is that here
>> alignof(struct i3c_ccc_mwl) will be '1', and architectures without efficient
>> unaligned access will have to access the field one byte at a time because
>> they assume that it may be misaligned.
>
> These are structure used to create packets to be sent on the wire.
> Making sure that everything is packed correctly is important, so I'm
> not sure I can remove the __packed everywhere.

I mean just the ones for which the __packed attribute only changes
the alignment of the outer structure but not the layout inside of the
structure. Alternatively, set both __packed and __aligned().

>> > +/**
>> > + * struct i3c_i2c_dev - I3C/I2C common information
>> > + * @node: node element used to insert the device into the I2C or I3C 
>> > device
>> > + *       list
>> > + * @bus: I3C bus this device is connected to
>> > + * @master: I3C master that instantiated this device. Will be used to send
>> > + *         I2C/I3C frames on the bus
>> > + * @master_priv: master private data assigned to the device. Can be used 
>> > to
>> > + *              add master specific information
>> > + *
>> > + * This structure is describing common I3C/I2C dev information.
>> > + */
>> > +struct i3c_i2c_dev {
>> > +       struct list_head node;
>> > +       struct i3c_bus *bus;
>> > +       struct i3c_master_controller *master;
>> > +       void *master_priv;
>> > +};
>>
>> I find this hard to follow, which means either this has to be complicated
>> and I just didn't take enough time to think it through, or maybe it can
>> be simplified.
>>
>> The 'node' field seems particularly odd, can you explain what it's
>> for? Normally all children of a bus device can be enumerated by
>> walking the device model structures. Are you doing this just so
>> you can walk a single list rather than walking the i3c and i2c
>> devices separately?
>
> The devices discovered on the bus are not directly registered to the
> device model, and I need to store them in a list to do some operations
> before exposing them. Once everything is ready to be used, I then
> iterate the list and register all not-yet-registered I3C devs.

Can you explain what those operations are and why we can't
register everything directly? This seems rather unconventional,
so I want to make sure it's done for a good reason.

      Arnd

Reply via email to