> 2011/3/18 George Kashperko <george@xxxxxxxxxxx>:
> > The clean solution I see here is to have host code apart from
> > backplane-specific processing. The way to accomplish this is obvious as
> > actual host device responsibility is not to switch cores but rather
> > provide mappings into physical address space of the backplane regardless
> > of the target request being made to core, sprom/otp, agent or whatever.
> > This makes much cleaner model than that provided by ssb.
>
> How do you think, what interface would fit for that?
>
> Something like:
> struct host_ops {
> bool (*init)(struct device *dev);
> bool (*exit)(struct device *dev);
> bool (*set_agent_addr)(struct device *dev, u16 addr);
> bool (*set_core_addr)(struct device *dev, u16 addr);
> };
> ?
Well, I see this as following. In generic host life time there are
several states. These states are following:
1. Host just started up, underlying backplane is powered up, we issued
backplane detect/scan. At this point at least some minimal windowed
access is up (if such required), not yet cores/devices are known.
2. Backplane got identified, scanned, individual cores/devices
recognised, buscommon and buscore are registered with kernel to get them
matched with drivers, and then probed and set up.
3. Buscommon and buscore are driven, host can finish with host specific
workarounds, both buscommon and buscore can get their _init entry points
called, we can setup host device irq routine, finally we can expose the
rest cores/devices to kernel.
With that in mind here is my general host ops design pseudo code:
struct host_ops {
/* Init call we should get once both buscommon and buscore drivers are bound (state #3) */
int (*init)(struct bcmb_bus *bus);
/* Regular backplane access ops */
u8 (*read(8|16|32))(struct bcmb_bus *bus, bcmb_addr_t addr);
void (*write(8|16|32))(struct bcmb_bus *bus, bcmb_addr_t addr, u(8|16|32) val);
/* For some theoretically hard-to-set-up before scan hosts we could keep scan_read32 */
u32 scan_read32(struct bcmb_bus *bus, bcmb_addr_t addr);
};
Finally (I'm not yet decided on that - still planning on sertaing
things) I see here a place for one more op - something like
int (*device_fixup)(struct bcmb_bus *bus, u16 ven, u16 id, u8 rev, struct bcmb_device **dev);
This one is supposed to allocate and setup struct bcmb_device at scan
time with optionally extending device list with more devices the host is
confident with (in my code model each core exposes at least 2 devices -
the core agent and the core itself, first one considered as
backplane-private and thus never registered with kernel). Such a fixup
could help to get a clean decision on how to handle host-specific
resourses such as sprom/otp/flash/uarts/etc.
Have nice day,
George
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
