Re: [PATCH v4] reset: add support for non-DT systems

2018-02-22 17:44 GMT+01:00 David Lechner : > On 02/22/2018 05:34 AM, Philipp Zabel wrote: >> >> On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: >> [...] In your case the platform code that adds the lookup may be identical to the code that registers the

Re: [PATCH v4] reset: add support for non-DT systems

2018-02-22 17:44 GMT+01:00 David Lechner : > On 02/22/2018 05:34 AM, Philipp Zabel wrote: >> >> On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: >> [...] In your case the platform code that adds the lookup may be identical to the code that registers the struct

Re: [PATCH v4] reset: add support for non-DT systems

On 02/22/2018 05:34 AM, Philipp Zabel wrote: On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: [...] In your case the platform code that adds the lookup may be identical to the code that registers the struct reset_controller_dev, but that doesn't have to be the case. I'm not sure how that

Re: [PATCH v4] reset: add support for non-DT systems

On 02/22/2018 05:34 AM, Philipp Zabel wrote: On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: [...] In your case the platform code that adds the lookup may be identical to the code that registers the struct reset_controller_dev, but that doesn't have to be the case. I'm not sure how that

Re: [PATCH v4] reset: add support for non-DT systems

2018-02-22 12:34 GMT+01:00 Philipp Zabel : > On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: > [...] >> > In your case the platform code that adds the lookup may be identical to >> > the code that registers the struct reset_controller_dev, but that >> > doesn't have

Re: [PATCH v4] reset: add support for non-DT systems

2018-02-22 12:34 GMT+01:00 Philipp Zabel : > On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: > [...] >> > In your case the platform code that adds the lookup may be identical to >> > the code that registers the struct reset_controller_dev, but that >> > doesn't have to be the case. I'm not

Re: [PATCH v4] reset: add support for non-DT systems

On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: [...] > > In your case the platform code that adds the lookup may be identical to > > the code that registers the struct reset_controller_dev, but that > > doesn't have to be the case. I'm not sure how that is supposed to work > > for the phy

Re: [PATCH v4] reset: add support for non-DT systems

On Tue, 2018-02-20 at 10:40 -0600, David Lechner wrote: [...] > > In your case the platform code that adds the lookup may be identical to > > the code that registers the struct reset_controller_dev, but that > > doesn't have to be the case. I'm not sure how that is supposed to work > > for the phy

Re: [PATCH v4] reset: add support for non-DT systems

On 02/20/2018 04:39 AM, Philipp Zabel wrote: Hi Bartosz, David, On Mon, 2018-02-19 at 18:21 -0600, David Lechner wrote: On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The reset framework only supports device-tree. There are some

Re: [PATCH v4] reset: add support for non-DT systems

On 02/20/2018 04:39 AM, Philipp Zabel wrote: Hi Bartosz, David, On Mon, 2018-02-19 at 18:21 -0600, David Lechner wrote: On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The reset framework only supports device-tree. There are some platforms however, which need to

Re: [PATCH v4] reset: add support for non-DT systems

Hi Bartosz, David, On Mon, 2018-02-19 at 18:21 -0600, David Lechner wrote: > On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: > > From: Bartosz Golaszewski > > > > The reset framework only supports device-tree. There are some platforms > > however, which need to use

Re: [PATCH v4] reset: add support for non-DT systems

Hi Bartosz, David, On Mon, 2018-02-19 at 18:21 -0600, David Lechner wrote: > On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: > > From: Bartosz Golaszewski > > > > The reset framework only supports device-tree. There are some platforms > > however, which need to use it even in legacy,

Re: [PATCH v4] reset: add support for non-DT systems

On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The reset framework only supports device-tree. There are some platforms however, which need to use it even in legacy, board-file based mode. An example of such architecture is the DaVinci

Re: [PATCH v4] reset: add support for non-DT systems

On 02/19/2018 10:58 AM, Bartosz Golaszewski wrote: From: Bartosz Golaszewski The reset framework only supports device-tree. There are some platforms however, which need to use it even in legacy, board-file based mode. An example of such architecture is the DaVinci family of SoCs which

[PATCH v4] reset: add support for non-DT systems

From: Bartosz Golaszewski The reset framework only supports device-tree. There are some platforms however, which need to use it even in legacy, board-file based mode. An example of such architecture is the DaVinci family of SoCs which supports both device tree and

[PATCH v4] reset: add support for non-DT systems

From: Bartosz Golaszewski The reset framework only supports device-tree. There are some platforms however, which need to use it even in legacy, board-file based mode. An example of such architecture is the DaVinci family of SoCs which supports both device tree and legacy boot modes and we don't