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);
};
?
--
RafaÅ
--
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
