From: Gwendal Grignou
EC returns a counter when there is an event on camera vsync.
This patch comes from chromeos kernel 4.4
Signed-off-by: Gwendal Grignou
Signed-off-by: Fabien Lahoudere
CROS EC sync sensor was originally designed as an IIO device.
Now that the counter subsystem will
Some chromebook EC provides a counter to get all vsync coming from the back
camera.
This series introduces a patch coming from chromebook kernel 4.4 designed as an
IIO counter. As IIO counter will be deprecated in favor of counter, I rebase the
original patch and support the new counter API.
The s
cros_ec_* sensors provides frequencies values in sysfs like this:
"0 min max". 0 is always true to disable the sensor.
Default frequencies are provided for earlier protocol.
Signed-off-by: Nick Vaccaro
Signed-off-by: Fabien Lahoudere
Acked-by: Jonathan Cameron
---
.../common/cros_
- Drop clean up patches
- Fix minor changes
Changes since v2:
- use read_avail callback
- rework core functions to avoid code duplication
Changes since v1:
- Add a cover letter
- Add Nick Vaccaro SoB to patch 1
- Drop fifo size related code
Fabien Lahoudere (1):
iio: common: cros_ec_sensors
Le dimanche 14 juillet 2019 à 17:19 +0100, Jonathan Cameron a écrit :
> On Tue, 2 Jul 2019 10:49:38 +0200
> Fabien Lahoudere wrote:
>
> > This patch adds a function to determine which version of the
> > protocol is used to communicate with EC.
> >
> >
Le dimanche 14 juillet 2019 à 18:31 +0100, Jonathan Cameron a écrit :
> On Tue, 9 Jul 2019 13:53:45 +0200
> Fabien Lahoudere wrote:
>
> > Embedded controller return minimum and maximum frequencies,
> > unfortunately
> > we have no way to know the step for all availab
From: Gwendal Grignou
EC returns a counter when there is an event on camera vsync.
This patch comes from chromeos kernel 4.4
Signed-off-by: Gwendal Grignou
Signed-off-by: Fabien Lahoudere
CROS EC sync sensor was originally designed as an IIO device.
Now that the counter subsystem will
Some chromebook EC provides a counter to get all vsync coming from the back
camera.
This series introduces a patch coming from chromebook kernel 4.4 designed as an
IIO counter. As IIO counter will be deprecated in favor of counter, I rebase the
original patch and support the new counter API.
The s
cros_ec_* sensors provides frequencies values in sysfs like this:
"0 min max". 0 is always true to disable the sensor.
Default frequencies are provided for earlier protocol.
Signed-off-by: Nick Vaccaro
Signed-off-by: Fabien Lahoudere
---
.../common/cros_ec_sensors/cros_ec_senso
callback
- rework core functions to avoid code duplication
Changes since v1:
- Add a cover letter
- Add Nick Vaccaro SoB to patch 1
- Drop fifo size related code
Fabien Lahoudere (1):
iio: common: cros_ec_sensors: Expose cros_ec_sensors frequency range
via iio sysfs
.../common/cros_ec_sensors
Le samedi 22 juin 2019 à 11:21 +0100, Jonathan Cameron a écrit :
> On Tue, 18 Jun 2019 11:06:39 +0200
> Fabien Lahoudere wrote:
>
> > The documentation give some exemple on what format can be expected
> > from sampling_frequency_available sysfs attribute
> >
> >
semicolon
- Add Enric Acked-by
Changes since v2:
- Use patch 1 from v1 after discussion on ML
Changes since v1:
- Drop second patch
- return ENODEV if version is 0
Fabien Lahoudere (1):
iio: common: cros_ec_sensors: determine protocol version
.../cros_ec_sensors/cros_ec_sensors_core.c| 36
This patch adds a function to determine which version of the
protocol is used to communicate with EC.
Signed-off-by: Fabien Lahoudere
Signed-off-by: Nick Vaccaro
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal Grignou
Acked-by: Enric Balletbo i Serra
---
.../cros_ec_sensors
Hi,
There is a double semi colon in that patch.
Let me send a v4 without it.
Le lundi 01 juillet 2019 à 10:14 +0200, Fabien Lahoudere a écrit :
> This patch adds a function to determine which version of the
> protocol is used to communicate with EC.
>
> Signed-off-by: Fabien Lahoude
This patch adds a function to determine which version of the
protocol is used to communicate with EC.
Signed-off-by: Fabien Lahoudere
Signed-off-by: Nick Vaccaro
Reviewed-by: Gwendal Grignou
Tested-by: Gwendal Grignou
---
.../cros_ec_sensors/cros_ec_sensors_core.c| 36
after discussion on ML
Changes since v1:
- Drop second patch
- return ENODEV if version is 0
Fabien Lahoudere (1):
iio: common: cros_ec_sensors: determine protocol version
.../cros_ec_sensors/cros_ec_sensors_core.c| 36 ++-
1 file changed, 35 insertions(+), 1 deletion
This patch adds a function to determine which version of the
protocol is used to communicate with EC.
Signed-off-by: Fabien Lahoudere
Signed-off-by: Nick Vaccaro
---
.../cros_ec_sensors/cros_ec_sensors_core.c| 40 ++-
1 file changed, 39 insertions(+), 1 deletion(-)
diff
- return ENODEV if version is 0
Fabien Lahoudere (1):
iio: common: cros_ec_sensors: determine protocol version
.../cros_ec_sensors/cros_ec_sensors_core.c| 40 ++-
1 file changed, 39 insertions(+), 1 deletion(-)
--
2.19.2
with this patch once you're fine with
> > it.
> >
> > Thanks,
> > ~ Enric
> >
> > [1] https://patchwork.kernel.org/patch/11014329/
> > [2] https://patchwork.kernel.org/patch/11014327/
> >
> > On 27/6/19 16:04, Fabien Lahoudere wrote:
> > > This
Hi Enric
Le jeudi 27 juin 2019 à 17:48 +0200, Enric Balletbo i Serra a écrit :
> Hi Fabien,
>
> On 27/6/19 16:04, Fabien Lahoudere wrote:
> > Version 3 of the EC protocol provides min and max frequencies for
> > EC sensors.
> > Default frequencies are pr
also like to carry with this patch once you're fine with
> > it.
> >
> > Thanks,
> > ~ Enric
> >
> > [1] https://patchwork.kernel.org/patch/11014329/
> > [2] https://patchwork.kernel.org/patch/11014327/
> >
> > On 27/6/19 16:04, Fabien Lahou
This patch adds a function to determine which version of the
protocol is used to communicate with EC.
Signed-off-by: Fabien Lahoudere
Signed-off-by: Nick Vaccaro
---
.../cros_ec_sensors/cros_ec_sensors_core.c| 36 ++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff
Version 3 of the EC protocol provides min and max frequencies for EC sensors.
Default frequencies are provided for earlier protocol.
Signed-off-by: Fabien Lahoudere
Signed-off-by: Nick Vaccaro
---
.../cros_ec_sensors/cros_ec_sensors_core.c| 44 +++
.../linux/iio/common
This series is a split of the following patch:
https://lkml.org/lkml/2019/6/18/268
To fix Enric comments from https://lkml.org/lkml/2019/6/25/949
I extract it from the other serie to speed up acceptance because
other patches need it to be upstreamed.
Fabien Lahoudere (2):
iio: common
with a couple of errors.
>
> I just have a few comments that I think should be quick to respin.
>
> [1] https://lkml.org/lkml/2019/6/24/1464
>
> On 22/6/19 12:15, Jonathan Cameron wrote:
> > On Tue, 18 Jun 2019 11:06:37 +0200
> > Fabien Lahoudere wrote:
> >
Le mardi 18 juin 2019 à 11:06 +0200, Fabien Lahoudere a écrit :
> Chromebooks EC sensors must expose a range of frequencies for each
> sensors using
> the standard ABI sampling_frquency_available.
>
> Changes since v2:
>
> - use read_avail callback
> - rework core
In order to avoid code duplication and make future works easier,
we add an iio_info structure to cros_ec_sensors_core_state structure.
Signed-off-by: Fabien Lahoudere
---
drivers/iio/common/cros_ec_sensors/cros_ec_sensors.c | 8 ++--
drivers/iio/common/cros_ec_sensors
Drivers based on cros_ec_sensors_core have structure containing the
core structure. In order to simplify, we drop all the specific and
useless structure to use the same one in all drivers.
If a future driver need specific field, we can add a private pointer
to that data.
Signed-off-by: Fabien
To avoid code duplication, we move channels initialization in
cros_ec_sensors_core.
Signed-off-by: Fabien Lahoudere
---
.../common/cros_ec_sensors/cros_ec_sensors.c | 49 ++-
.../cros_ec_sensors/cros_ec_sensors_core.c| 25 +-
drivers/iio/light/cros_ec_light_prox.c
In order to simplify derivated drivers from cros_ec_sensors_core,
a new core function is created to registered IIO stricture.
Signed-off-by: Fabien Lahoudere
---
.../common/cros_ec_sensors/cros_ec_sensors.c | 9 +-
.../cros_ec_sensors/cros_ec_sensors_core.c| 97
cros_ec_* sensors provides frequencies values in sysfs like this:
"0 min max".
0 is always true to disable the sensor.
Signed-off-by: Fabien Lahoudere
---
.../cros_ec_sensors/cros_ec_sensors_core.c| 22 +++
.../linux/iio/common/cros_ec_sensors_core.h | 4 +++-
2 fil
Version 3 of the EC protocol provides min and max frequencies for EC sensors.
Signed-off-by: Fabien Lahoudere
Signed-off-by: Nick Vaccaro
---
.../cros_ec_sensors/cros_ec_sensors_core.c| 85 ++-
.../linux/iio/common/cros_ec_sensors_core.h | 3 +
2 files changed, 87
The documentation give some exemple on what format can be expected
from sampling_frequency_available sysfs attribute
Signed-off-by: Fabien Lahoudere
---
Documentation/ABI/testing/sysfs-bus-iio | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/ABI/testing
- Drop fifo size related code
Fabien Lahoudere (8):
iio: common: cros_ec_sensors: move iio_info management to core
iio: common: cros_ec_sensors: move channels to core structure
iio: common: cros_ec_sensors: move registration to core
iio: common: cros_ec_sensors: clean code
iio: common
Drop redundant initialization previously set in cros_ec_sensors_init
Signed-off-by: Fabien Lahoudere
---
drivers/iio/light/cros_ec_light_prox.c | 2 --
drivers/iio/pressure/cros_ec_baro.c| 2 --
2 files changed, 4 deletions(-)
diff --git a/drivers/iio/light/cros_ec_light_prox.c
b/drivers
Le mercredi 12 juin 2019 à 09:42 +0100, Lee Jones a écrit :
> On Thu, 23 May 2019, Fabien Lahoudere wrote:
>
> > Version 3 of the EC protocol provides min and max frequencies and
> > fifo
> > size for EC sensors.
> >
> > Signed-off-by: Fabien Lahoud
Le mardi 28 mai 2019 à 04:04 -0700, Gwendal Grignou a écrit :
> On Mon, May 27, 2019 at 2:55 AM Fabien Lahoudere
> wrote:
> > Le dimanche 26 mai 2019 à 18:45 +0100, Jonathan Cameron a écrit :
> > > On Thu, 23 May 2019 11:07:36 +0200
> > > Fabien Lahoudere wro
Le lundi 03 juin 2019 à 13:55 +0100, Lee Jones a écrit :
> On Wed, 22 May 2019, Fabien Lahoudere wrote:
>
> > Version 3 of the EC protocol provides min and max frequencies and
> > fifo
> > size for EC sensors.
> >
> > Signed-off-by: Fabien Lahoude
Le dimanche 26 mai 2019 à 18:45 +0100, Jonathan Cameron a écrit :
> On Thu, 23 May 2019 11:07:36 +0200
> Fabien Lahoudere wrote:
>
> > In order to provide minimum and maximum frequencies for each
> > sensors,
> > we use a standard API (sampling_frequency_available)
The documentation give some exemple on what format can be expected
from sampling_frequency_available sysfs attribute
Signed-off-by: Fabien Lahoudere
---
Documentation/ABI/testing/sysfs-bus-iio | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/ABI/testing
Version 3 of the EC protocol provides min and max frequencies and fifo
size for EC sensors.
Signed-off-by: Fabien Lahoudere
Signed-off-by: Nick Vaccaro
---
.../cros_ec_sensors/cros_ec_sensors_core.c| 83 ++-
.../linux/iio/common/cros_ec_sensors_core.h | 4 +
include
quot;
with their callback. This change impact drivers using that function.
Then cros_ec_* sensors provides frequencies range in sysfs like this:
[min step max]
Signed-off-by: Fabien Lahoudere
---
.../common/cros_ec_sensors/cros_ec_sensors.c | 6 +--
.../cros_ec_sensors/cros_ec_sensors_core
Chromebooks EC sensors must expose a range of frequencies for each sensors using
the standard ABI sampling_frquency_available.
Changes since v1:
- Add a cover letter
- Add Nick Vaccaro SoB to patch 1
- Drop fifo size related code
Fabien Lahoudere (3):
iio: common: cros_ec_sensors: support
Version 3 of the EC protocol provides min and max frequencies and fifo
size for EC sensors.
Signed-off-by: Fabien Lahoudere
---
.../cros_ec_sensors/cros_ec_sensors_core.c| 98 ++-
.../linux/iio/common/cros_ec_sensors_core.h | 7 ++
include/linux/mfd/cros_ec_commands.h
The documentation give some exemple on what format can be expected
from sampling_frequency_available sysfs attribute
Signed-off-by: Fabien Lahoudere
---
Documentation/ABI/testing/sysfs-bus-iio | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/ABI/testing
quot;
with their callback. This change impact drivers using that function.
Then cros_ec_* sensors provides frequencies range in sysfs like this:
[min step max]
Signed-off-by: Fabien Lahoudere
---
.../common/cros_ec_sensors/cros_ec_sensors.c | 6 +--
.../cros_ec_sensors/cros_ec_sensors_core
m.googlesource.com/chromiumos/platform/ec/+/master/include/ec_commands.h
>
> That include file is converted to remove ACPI and Embedded only code.
Hi,
I reviewed patches of the series and they looks good to me.
Reviewed-by: Fabien Lahoudere
7;Septembre' by 'September'.
Signed-off-by: Gwendal Grignou
Signed-off-by: Fabien Lahoudere
---
Documentation/ABI/testing/sysfs-bus-iio-cros-ec| 10 +-
.../common/cros_ec_sensors/cros_ec_sensors_core.c | 14 ++
2 files changed, 19 insertions(+), 5 deletions(-)
Hi Greg,
On Mon, 2018-10-15 at 16:01 +0200, Greg KH wrote:
> On Thu, Oct 11, 2018 at 11:25:03AM +0200, Fabien Lahoudere wrote:
> > In order to optimize serial communication on imx53 and imx6, we may
> > need to tweak DMA period and buffer length per period.
>
> Why can you n
*/dma_buffer_size
/sys/class/tty/ttymxc*/dma_buffer_count
Signed-off-by: Fabien Lahoudere
---
Changes since v2:
- Improve attribute documentation
- Fix various typo
- Remove useless debug message
- Clean code
Documentation/ABI/stable/sysfs-driver-imx-uart | 13
drivers/tty/serial/imx.c
Hi Peter
On Fri, 2017-06-09 at 08:26 +, Peter Chen wrote:
>
> >
> > I have a look at your patches
> > (http://www.spinics.net/lists/linux-usb/msg157134.html)
> > and I wonder if power sequence is applicable only on hub node?
>
> No, power sequence can be used for any devices which needs t
Hi Peter
I have a look at your patches
(http://www.spinics.net/lists/linux-usb/msg157134.html) and I wonder
if power sequence is applicable only on hub node? hub are probed too late
(after ci_ulpi_init). Do
you think it is possible to read a power sequence in dts from ci_ulpi_init?
Thanks
Fabi
On Wed, 2017-06-07 at 09:43 +0800, Peter Chen wrote:
> On Tue, Jun 06, 2017 at 07:36:10PM +0200, Fabien Lahoudere wrote:
> > Hi Peter,
> >
> > On Tue, 2017-06-06 at 09:55 +0800, Peter Chen wrote:
> > > On Mon, Jun 05, 2017 at 11:52:26AM +0200, Fabien Lahoudere wrote:
Hi Peter,
On Tue, 2017-06-06 at 09:55 +0800, Peter Chen wrote:
> On Mon, Jun 05, 2017 at 11:52:26AM +0200, Fabien Lahoudere wrote:
> > On Mon, 2017-06-05 at 17:43 +0800, Peter Chen wrote:
> > > On Mon, Jun 05, 2017 at 10:57:00AM +0200, Fabien Lahoudere wrote:
> > > &g
On Mon, 2017-06-05 at 17:43 +0800, Peter Chen wrote:
> On Mon, Jun 05, 2017 at 10:57:00AM +0200, Fabien Lahoudere wrote:
> > On Fri, 2017-06-02 at 15:00 -0700, Stephen Boyd wrote:
> > > On 05/26, Fabien Lahoudere wrote:
> > > > Hello
> > > >
> > >
On Fri, 2017-06-02 at 15:00 -0700, Stephen Boyd wrote:
> On 05/26, Fabien Lahoudere wrote:
> > Hello
> >
> > I modify ci_hrdc_imx_probe to bypass "data->phy =
> > devm_usb_get_phy_by_phandle(&pdev->dev,
> > "fsl,usbphy", 0);". E
is not out of reset state.
The conclusion is that using ulpi_bus to manage our phy doesn't improve and we
reach the same issue.
I will try to check if we don't do bad things in hw_phymode_configure.
If anyone have an idea it is welcome??
Fabien
On Thu, 2017-05-25 at 12:36 +0200, F
On Tue, 2017-05-23 at 14:00 -0700, Stephen Boyd wrote:
> On 05/23, Fabien Lahoudere wrote:
> > Hi,
> >
> > We investigate on the topic and now our device tree look like:
> >
> > in imx53.dtsi:
> >
> > usbh2: usb@53f80400 {
> > compatible
SC USB3315 clock and regulator to always be initialized.
> > We also need the PHY driver to take the PHY out of reset. This patch
> > extends the existing USB generic nop phy driver to include a new
> > initialization path.
> >
> > A new compatible string "smsc,u
From: Csaba Kertesz
Add a hwmon entry to get the temperature from the die of imx53
SATA.
The original patch was made by Richard Zhu for kernel 2.6.x:
ENGR00134041-MX53-Add-the-SATA-AHCI-temperature-monitor.patch
Signed-off-by: Fabien Lahoudere
---
drivers/ata/ahci_imx.c | 195
From: Csaba Kertesz
Add a hwmon entry to get the temperature from the die of imx53
SATA.
The original patch was made by Richard Zhu for kernel 2.6.x:
ENGR00134041-MX53-Add-the-SATA-AHCI-temperature-monitor.patch
Signed-off-by: Fabien Lahoudere
---
drivers/ata/ahci_imx.c | 225
From: Csaba Kertesz
Add a hwmon entry to get the temperature from the die of imx53
SATA.
The original patch was made by Richard Zhu for kernel 2.6.x:
ENGR00134041-MX53-Add-the-SATA-AHCI-temperature-monitor.patch
Signed-off-by: Fabien Lahoudere
---
drivers/ata/ahci_imx.c | 225
Add New Vision Display 7.0" 800 RGB x 480 TFT LCD panel
Signed-off-by: Fabien Lahoudere
Acked-by: Rob Herring
---
.../devicetree/bindings/display/panel/nvd,9128.txt | 7 ++
.../devicetree/bindings/vendor-prefixes.txt| 1 +
drivers/gpu/drm/panel/panel-simple.c
ating with specific USB based data acquisition
devices which are connected to it, extracting the required data and
providing it to the host via other methods. SPI is used as an out-of-band
configuration channel.
Signed-off-by: Fabien Lahoudere
---
drivers/spi/spidev.c | 1 +
1 file changed, 1 insertio
Hi,
On 30/09/16 19:35, Geert Uytterhoeven wrote:
On Fri, Sep 30, 2016 at 12:15 PM, Fabien Lahoudere
wrote:
Entries are needed in the spidev ID list to configure configure it from a
device tree. Add entries for the following devices:
- "exar,xra1403" : a GPIO expander
Lo
Entries are needed in the spidev ID list to configure configure it from a
device tree. Add entries for the following devices:
- "fsl,mk20fn1m0vmd12" : a cortex m4 based chip
- "exar,xra1403" : a GPIO expander
Signed-off-by: Fabien Lahoudere
---
drivers/spi/spidev.c | 2 +
ing because we can disable the feature by using an
existing binding
Fabien Lahoudere (2):
usb: chipidea: imx: configure imx for ULPI phy
usb: chipidea: imx: Disable internal 60Mhz clock with ULPI PHY
drivers/usb/chipidea/ci_hdrc_imx.c | 4 ++
drivers/usb/chipidea/ci_hdrc_imx
for features if they exist for this index.
This patch also remove useless test of reg and val. Those two values cannot
be NULL.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c | 4 ++
drivers/usb/chipidea/ci_hdrc_imx.h | 1 +
drivers/usb/chipidea/usbmi
The internal 60Mhz clock for host2 and host3 are useless in ULPI
phy mode, so we disable it when configuring ULPI PHY node for
those host.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/usbmisc_imx.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/usb/chipidea
Hi,
On 23/09/16 21:47, Rob Herring wrote:
On Wed, Sep 21, 2016 at 11:07:07AM +0200, Fabien Lahoudere wrote:
This binding allow to disable the internal 60Mhz clock for USB host2 or
host3.
Signed-off-by: Fabien Lahoudere
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 1
Hi,
On 26/09/16 10:18, Sascha Hauer wrote:
On Wed, Sep 21, 2016 at 11:07:07AM +0200, Fabien Lahoudere wrote:
This binding allow to disable the internal 60Mhz clock for USB host2 or
host3.
Signed-off-by: Fabien Lahoudere
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 1
This binding allow to disable the internal 60Mhz clock for USB host2 or
host3.
Signed-off-by: Fabien Lahoudere
---
Documentation/devicetree/bindings/usb/ci-hdrc-usb2.txt | 1 +
drivers/usb/chipidea/ci_hdrc_imx.c | 2 ++
drivers/usb/chipidea/ci_hdrc_imx.h
for features if they exist for this index.
This patch also remove useless test of reg and val. Those two values cannot
be NULL.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c | 5 +++
drivers/usb/chipidea/ci_hdrc_imx.h | 1 +
drivers/usb/chipidea/usbmi
n the same column as switch)
- Remove useless test in "Change switch order"
Changes in V5:
- Squash "Change switch order" and "configure imx for ULPI phy"
- Add device tree binding documentation
Fabien Lahoudere (2):
usb: chipidea: imx: co
Hi,
On 21/09/16 09:12, Peter Chen wrote:
On Mon, Sep 19, 2016 at 01:45:39PM +0200, Fabien Lahoudere wrote:
In order to use ULPI phy with usb host 2 and 3, we need to configure
controller register to enable ULPI features.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c
Hi,
On 21/09/16 08:57, Peter Chen wrote:
On Mon, Sep 19, 2016 at 01:45:38PM +0200, Fabien Lahoudere wrote:
Each USB controller have different behaviour, so in order to avoid to have
several "swicth(data->index)" and lock/unlock, we prefer to get the index
switch and then test fo
annot
be NULL.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/usbmisc_imx.c | 38 --
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git a/drivers/usb/chipidea/usbmisc_imx.c
b/drivers/usb/chipidea/usbmisc_imx.c
index 20d02a5..9549821 100644
In order to use ULPI phy with usb host 2 and 3, we need to configure
controller register to enable ULPI features.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c | 5 +
drivers/usb/chipidea/ci_hdrc_imx.h | 1 +
drivers/usb/chipidea/usbmisc_imx.c | 37
This binding allow to disable the internal 60Mhz clock for USB host2 and
host3.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c | 2 ++
drivers/usb/chipidea/ci_hdrc_imx.h | 1 +
drivers/usb/chipidea/usbmisc_imx.c | 13 +
3 files changed, 16 insertions
n the same column as switch)
- Remove useless test in "Change switch order"
Fabien Lahoudere (3):
usb: chipidea: imx: Change switch order
usb: chipidea: imx: configure imx for ULPI phy
usb: chipidea: imx: Add binding to disable USB 60Mhz clock
drivers/usb/chipidea/ci_hd
From: Kalle Kankare
Add clocks configuration for CSI, FIRI and IEEE1588.
Signed-off-by: Fabien Lahoudere
---
drivers/clk/imx/clk-imx51-imx53.c | 20
include/dt-bindings/clock/imx5-clock.h | 15 ++-
2 files changed, 34 insertions(+), 1 deletion(-)
diff
Please forget this submission.
On 19/09/16 12:18, Fabien Lahoudere wrote:
Each USB controller have different behaviour, so in order to avoid to have
several "swicth(data->index)" and lock/unlock, we prefer to get the index
and then test for features if they exist for this index.
This binding allow to disable the internal 60Mhz clock for USB host2 and
host3.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c | 2 ++
drivers/usb/chipidea/ci_hdrc_imx.h | 1 +
drivers/usb/chipidea/usbmisc_imx.c | 17 +
3 files changed, 20 insertions
Each USB controller have different behaviour, so in order to avoid to have
several "swicth(data->index)" and lock/unlock, we prefer to get the index
and then test for features if they exist for this index.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/usbmi
In order to use ULPI phy with usb host 2 and 3, we need to configure
controller register to enable ULPI features.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c | 5 +
drivers/usb/chipidea/ci_hdrc_imx.h | 1 +
drivers/usb/chipidea/usbmisc_imx.c | 37
Each USB controller have different behaviour, so in order to avoid to have
several "swicth(data->index)" and lock/unlock, we prefer to get the index
and then test for features if they exist for this index.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/usbmi
Hi,
On 18/09/16 02:24, Shawn Guo wrote:
On Sun, Sep 18, 2016 at 08:21:59AM +0800, Shawn Guo wrote:
On Thu, Sep 15, 2016 at 08:42:33PM +0300, Alexander Shiyan wrote:
Четверг, 15 сентября 2016, 13:13 +03:00 от Fabien Lahoudere
:
From: Kalle Kankare < kalle.kank...@vincit.fi >
Add
This binding allow to disable the internal 60Mhz clock for USB host2 and
host3.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c | 2 ++
drivers/usb/chipidea/ci_hdrc_imx.h | 1 +
drivers/usb/chipidea/usbmisc_imx.c | 17 +
3 files changed, 20 insertions
In order to use ULPI phy with usb host 2 and 3, we need to configure
controller register to enable ULPI features.
Signed-off-by: Fabien Lahoudere
---
drivers/usb/chipidea/ci_hdrc_imx.c | 5 +++
drivers/usb/chipidea/ci_hdrc_imx.h | 1 +
drivers/usb/chipidea/usbmisc_imx.c | 81
From: Kalle Kankare
Add clocks configuration for CSI, FIRI and IEEE1588.
Signed-off-by: Fabien Lahoudere
---
drivers/clk/imx/clk-imx51-imx53.c | 20
include/dt-bindings/clock/imx5-clock.h | 15 ++-
2 files changed, 34 insertions(+), 1 deletion(-)
diff
Add New Vision Display 7.0" 800 RGB x 480 TFT LCD panel
Signed-off-by: Fabien Lahoudere
Acked-by: Rob Herring
---
.../devicetree/bindings/display/panel/nvd,9128.txt | 7 ++
.../devicetree/bindings/vendor-prefixes.txt| 1 +
drivers/gpu/drm/panel/panel-simple.c
dmaengine_terminate_all() is deprecated and should be replaced by
dmaengine_terminate_sync() in non-atomic context or dmaengine_terminate_async()
with dmaengine_synchronize().
See commit b36f09c3c441 ("dmaengine: Add transfer termination synchronization
support")
Signed-off-by: Fabien
From: Martyn Welch
The UART DMA was only being configured on i.MX6Q compatible devices. We
know that the DMA also works for i.MX53 devices, so enable uart DMA for
imx53 and let the device tree to configure if DMA should be used or not.
Signed-off-by: Martyn Welch
Signed-off-by: Fabien
Hello,
Thanks for your comments
On 05/08/2016 15:39, Mark Rutland wrote:
On Fri, Aug 05, 2016 at 03:31:25PM +0200, Fabien Lahoudere wrote:
+/*
+ * Hardware uses CKO2 at 24MHz at several places. Set the parent clock of
+ * CKO2 to OSC.
+ */
+#define CKO2_CONFIGURATION \
+ clock-frequency
From: Csaba Kertesz
Add a hwmon entry to get the temperature from the die of imx53
SATA.
The original patch was made by Richard Zhu for kernel 2.6.x:
ENGR00134041-MX53-Add-the-SATA-AHCI-temperature-monitor.patch
Signed-off-by: Fabien Lahoudere
---
drivers/ata/ahci_imx.c | 225
In order to use sdma with UART, we need to add DMA configuration
in device tree.
Signed-off-by: Fabien Lahoudere
---
arch/arm/boot/dts/imx53.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/imx53.dtsi b/arch/arm/boot/dts/imx53.dtsi
index cd17037..c1bc97c
From: Martyn Welch
The UART DMA was only being configured on i.MX6Q compatible devices. We
know that the DMA also works for i.MX53 devices, so allow DMA to be
configured on those devices too.
Signed-off-by: Martyn Welch
Signed-off-by: Fabien Lahoudere
---
drivers/tty/serial/imx.c | 17
PPD is a product from GE Healthcare to monitor vital biometric signals.
In order to support it upstream, we add its device tree file
imx53-ppd.dts.
Signed-off-by: Fabien Lahoudere
---
arch/arm/boot/dts/Makefile |1 +
arch/arm/boot/dts/imx53-ppd.dts | 1024
Adding spidev in the compatible list, let configure spidev from device tree
instead of C source code.
Signed-off-by: Fabien Lahoudere
---
Documentation/devicetree/bindings/spi/spidev.txt | 16
drivers/spi/spidev.c | 1 +
2 files changed, 17
Add New Vision Display 7.0" 800 RGB x 480 TFT LCD panel
Signed-off-by: Fabien Lahoudere
---
.../devicetree/bindings/display/panel/nvd,9128.txt | 7 ++
.../devicetree/bindings/vendor-prefixes.txt| 1 +
drivers/gpu/drm/panel/panel-simple.c
1 - 100 of 110 matches
Mail list logo
