The signature for `debugfs_create_regset32` changed from
returning a `struct dentry *` to `void`.
Error checking is no longer possible.

Signed-off-by: Gwenhael GOAVEC <gwenhael.goavec@femto-st.fr>
Signed-off-by: Mathis MARION <mathis.marion@grenoble-inp.org>

When the FPGA is not programmed it could happen that some ALIx interrupt
get asserted due to noise. To avoid to scare users, we hide those errors
when the FPGA is not configured.

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>

Signed-off-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>

Signed-off-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

The following patch introduced a fix and a bug because I forgot to change
the negation:

7b3d1da4

 drv:gn412x_gpio: fix direction get/set

Here we try to fix it, definitively.

To check, do:

  cat /sys/kernel/debug/gpio

Reported-by: Dimitris Lampridis <dimitris.lampridis@cern.ch>
Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

It looks like there is a bug somewhere that make the system panic
on resource releasing. I can't provide any evidence that devm_* is
related to the issue, but removing it seems to solve the problem
(or at least is not as frequent as before: I can load/unload 100 times
without problems).

The problem was mitigated also by introducing delays (mdelay/printk)
in the fcl/gpio remove functions.

My guess is that MFD removal and devres clean up conflicts at some
point. MFD uses platform_unregister() which does resource_release(),
and because of devres, only after that we will release all resources
that we took on probe(). The flow does not sound right, we should
release resources we took **before** platform releases/remove the
resource from the system (not viceversa).

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

While drivers are processing a level interrupts, the bit in GPIO_INT_STATUS
get set and it sticks there. Only when drivers processed the level interrupts
we are sure that the bit does not get set again. Therefore, only at this
point we can properly clean the GPIO_INT_STATUS. Then we may have problems,
with the edge interrupts, so we put them (edge interrupts) back in the
GPIO_INT_STATUS. About this last point we are not sure that is going to work,
but in all our installation we are not going to use edge interrupts because
they are risky.

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

The hardware does not keep in count the INT_MASK, but on our side
we do no want to handle interrupts that have not been requested.

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

It also updates the Copyright year and fix the copyright in LICENSES

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

We do not want any GPIO usage to overwrite a bypass mode

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>

Implement the GPIO chip interface and use it for selecting the
FPGA programming mode

Signed-off-by: Federico Vaga <federico.vaga@cern.ch>