Re: [PATCH v10 0/8] ARM: berlin: add AHCI support

2014-07-21 Thread Antoine Ténart
Hi Hans, On Sat, Jul 19, 2014 at 12:31:19PM +0200, Hans de Goede wrote: > On 07/19/2014 12:18 PM, Hans de Goede wrote: > > >The problem is that: > > > >1) We need to enable resources before we can do ahci_save_initial_config() > >2) We must do ahci_save_initial_config() before we can do > >ata_h

Re: [PATCH v10 0/8] ARM: berlin: add AHCI support

2014-07-19 Thread Hans de Goede
Hi, On 07/19/2014 12:18 PM, Hans de Goede wrote: The problem is that: 1) We need to enable resources before we can do ahci_save_initial_config() 2) We must do ahci_save_initial_config() before we can do ata_host_alloc_pinfo() 3) Therefor we don't have port_info at enable_resources time, whic

Re: [PATCH v10 0/8] ARM: berlin: add AHCI support

2014-07-19 Thread Hans de Goede
Hi, On 07/18/2014 03:57 PM, Tejun Heo wrote: (cc'ing Hans who's now maintaining libahci-platform.) Note I was already following this thread as I'm subscribed to linux-ide now. On Fri, Jul 18, 2014 at 02:29:59PM +0200, Antoine Ténart wrote: Tejun, Kishon, Sebastian, I looked into the AHCI

Re: [PATCH v10 0/8] ARM: berlin: add AHCI support

2014-07-19 Thread Sebastian Hesselbarth
On 07/18/2014 03:57 PM, Tejun Heo wrote: > On Fri, Jul 18, 2014 at 02:29:59PM +0200, Antoine Ténart wrote: >> In both cases we do not have time to do this for the next release, as >> the request popped up quite late. >> >> So as of now: >> - Either the series is merged as is and changes to the AH

Re: [PATCH v10 0/8] ARM: berlin: add AHCI support

2014-07-18 Thread Tejun Heo
(cc'ing Hans who's now maintaining libahci-platform.) On Fri, Jul 18, 2014 at 02:29:59PM +0200, Antoine Ténart wrote: > Tejun, Kishon, Sebastian, > > I looked into the AHCI framework to see how to map PHYs and ports > information. I see two ways of doing this: > - We can attach the ahci_port_pr

[PATCH v10 0/8] ARM: berlin: add AHCI support

2014-07-18 Thread Antoine Ténart
Tejun, Kishon, Sebastian, I looked into the AHCI framework to see how to map PHYs and ports information. I see two ways of doing this: - We can attach the ahci_port_priv to the ahci_host_priv structure, but that would require quite a lot of changes since the ahci_port_priv is initialized