Re: [PATCH v4 1/5] cmd: bind: allow to bind driver with driver data

2020-07-28 Thread Patrice CHOTARD
Hi Tom On 7/7/20 10:08 PM, Tom Rini wrote: > On Thu, Apr 30, 2020 at 12:06:15PM +0200, Patrice Chotard wrote: > >> Initial implementation invokes device_bind_with_driver_data() >> with driver_data parameter equal to 0. >> For driver with driver data, the bind command can't bind >> correctly this

Re: [PATCH v4 1/5] cmd: bind: allow to bind driver with driver data

2020-07-27 Thread Patrice CHOTARD
don't take care of my previous email, i did a mistake Patrice On 7/27/20 4:25 PM, Patrice CHOTARD wrote: > Hi Tom > > Sorry for the delay, i was on vacation. > > I launched dm unit tests on current master > (ada61f1ee2a4eaa1b29d699b5ba940483171df8a) > > and everything seems ok, perhaps i

Re: [PATCH v4 1/5] cmd: bind: allow to bind driver with driver data

2020-07-27 Thread Tom Rini
On Mon, Jul 27, 2020 at 02:25:06PM +, Patrice CHOTARD wrote: > Hi Tom > > Sorry for the delay, i was on vacation. > > I launched dm unit tests on current master > (ada61f1ee2a4eaa1b29d699b5ba940483171df8a) > > and everything seems ok, perhaps i don't execute them correctly, see my log >

Re: [PATCH v4 1/5] cmd: bind: allow to bind driver with driver data

2020-07-27 Thread Patrice CHOTARD
Hi Tom Sorry for the delay, i was on vacation. I launched dm unit tests on current master (ada61f1ee2a4eaa1b29d699b5ba940483171df8a) and everything seems ok, perhaps i don't execute them correctly, see my log below : ./test/py/test.py --bd sandbox --build -k ut_dm -v +make

Re: [PATCH v4 1/5] cmd: bind: allow to bind driver with driver data

2020-07-07 Thread Tom Rini
On Thu, Apr 30, 2020 at 12:06:15PM +0200, Patrice Chotard wrote: > Initial implementation invokes device_bind_with_driver_data() > with driver_data parameter equal to 0. > For driver with driver data, the bind command can't bind > correctly this driver or even worse causes data abort as shown

[PATCH v4 1/5] cmd: bind: allow to bind driver with driver data

2020-04-30 Thread Patrice Chotard
Initial implementation invokes device_bind_with_driver_data() with driver_data parameter equal to 0. For driver with driver data, the bind command can't bind correctly this driver or even worse causes data abort as shown below: As example, for debug purpose on STM32MP1 platform, ethernet