On Wednesday 20 February 2013, Dong Aisheng wrote:
> But one question i wonder is that it may be hard to know how many poteintial
> non-dt platforms may use syscon.
Yes, good point. Of course we want as many platforms as possible to
use syscon, just like we want them to use DT, because both things
On 20 February 2013 19:14, Arnd Bergmann wrote:
> On Wednesday 20 February 2013, Dong Aisheng wrote:
>> On 20 February 2013 18:06, Arnd Bergmann wrote:
>> > I would first like to get an answer to the question I asked in my first
>> > mail,
>> > which is what the use case of non-DT support in thi
On Wednesday 20 February 2013, Dong Aisheng wrote:
> On 20 February 2013 18:06, Arnd Bergmann wrote:
> > I would first like to get an answer to the question I asked in my first
> > mail,
> > which is what the use case of non-DT support in this driver is. If this
> > is used only by a new platform
On 20 February 2013 18:06, Arnd Bergmann wrote:
> On Wednesday 20 February 2013, Alexander Shiyan wrote:
>> On 20 February 2013 13:41, Alexander Shiyan wrote:
>> >
>> > One problem is that every user needs to add their syscon compatible device
>> > support(platform_device_id) in syscon driver fir
On Wednesday 20 February 2013, Alexander Shiyan wrote:
> On 20 February 2013 13:41, Alexander Shiyan wrote:
> >
> > One problem is that every user needs to add their syscon compatible device
> > support(platform_device_id) in syscon driver first before they can use it.
> > But it looks to me just
On 20 February 2013 13:41, Alexander Shiyan wrote:
>> > ...
>> >> >> >> >> struct regmap *syscon_regmap_lookup_by_compatible(const char *s)
>> >> >> >> >> {
>> >> >> >> >> struct device_node *syscon_np;
>> >> >> >> >> struct regmap *regmap;
>> >> >> >> >> + struct syscon *syscon;
6 matches
Mail list logo
