Hi Matthias,
On Mon, Sep 7, 2020 at 4:40 AM Matthias Schiffer
wrote:
> My rationale here is the following: As broken as the native CS of these
> controllers is, it isn't an unreasonable assumption that it is working
> fine with *some* devices or for some usecases - after all the support
> was im
On Fri, 2020-09-04 at 12:42 -0300, Fabio Estevam wrote:
> Hi Mark,
>
> On Fri, Sep 4, 2020 at 12:05 PM Mark Brown
> wrote:
> >
> > On Fri, Sep 04, 2020 at 04:34:43PM +0200, Matthias Schiffer wrote:
> >
> > > Nevertheless, I don't see why we should deliberately remove the
> > > native
> > > CS s
Hi Mark,
On Fri, Sep 4, 2020 at 12:05 PM Mark Brown wrote:
>
> On Fri, Sep 04, 2020 at 04:34:43PM +0200, Matthias Schiffer wrote:
>
> > Nevertheless, I don't see why we should deliberately remove the native
> > CS support - my understanding was that we try to avoid breaking changes
> > to DT inte
On Fri, Sep 04, 2020 at 04:34:43PM +0200, Matthias Schiffer wrote:
> Nevertheless, I don't see why we should deliberately remove the native
> CS support - my understanding was that we try to avoid breaking changes
> to DT interpretation even for unknown/out-of-tree DTS.
Yes, we should try to main
On Fri, 2020-09-04 at 10:57 -0300, Fabio Estevam wrote:
> On Fri, Sep 4, 2020 at 10:02 AM Matthias Schiffer
> wrote:
>
> > This would make num_chipselect default to 1 again (set by
> > __spi_alloc_controller()), breaking every i.MX board that uses more
> > than 1 native CS.
>
> Which boards are
5 matches
Mail list logo
