mbox series

[0/7] add LCD support for SAM9X60

Message ID 1551284609-14594-1-git-send-email-claudiu.beznea@microchip.com (mailing list archive)
Headers show
Series add LCD support for SAM9X60 | expand

Message

Claudiu Beznea Feb. 27, 2019, 4:24 p.m. UTC
From: Claudiu Beznea <claudiu.beznea@microchip.com>

Hi,

These patches adds support for SAM9X60's LCD controller.

First patches add option to specify if controller clock source is fixed.
Second patch avoid a variable initialization in atmel_hlcdc_crtc_mode_set_nofb().
The 3rd one adds specific bindings for SAM9X60 LCD controller.
The 4th and 5th add compatibles in the driver.
The 6th patch enables sys_clk in probe since SAM9X60 needs this.
Specific support was added also in suspend/resume hooks.
The work in the 6th patch was done based on support added in 1st patch.
The 7th patch adds SAM9X60's LCD configuration and enabled it. 

I kept a big series including PWM, MFD, LCD changes due to shared DT
bindings. If you prefer, I'm available to send them separately. Please let
me know.

Thank you,
Claudiu Beznea

Claudiu Beznea (5):
  drm: atmel-hlcdc: add config option for clock selection
  drm: atmel-hlcdc: avoid initializing cfg with zero
  dt-bindings: mfd: add bindings for SAM9X60 HLCD controller
  mfd: atmel-hlcdc: add compatible for SAM9X60 HLCD controller
  pwm: atmel-hlcdc: add compatible for SAM9X60 HLCDC's PWM

Sandeep Sheriker Mallikarjun (2):
  drm: atmel-hlcdc: enable sys_clk during initalization.
  drm: atmel-hlcdc: add sam9x60 LCD controller

 .../devicetree/bindings/mfd/atmel-hlcdc.txt        |   1 +
 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c     |  17 ++-
 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c       | 120 ++++++++++++++++++++-
 drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.h       |   2 +
 drivers/mfd/atmel-hlcdc.c                          |   1 +
 drivers/pwm/pwm-atmel-hlcdc.c                      |   3 +
 6 files changed, 134 insertions(+), 10 deletions(-)

Comments

Sam Ravnborg Feb. 28, 2019, 6:21 p.m. UTC | #1
Hi Claudiu

On Wed, Feb 27, 2019 at 04:24:11PM +0000, Claudiu.Beznea@microchip.com wrote:
> From: Claudiu Beznea <claudiu.beznea@microchip.com>
> 
> Hi,
> 
> These patches adds support for SAM9X60's LCD controller.
Can you elaborate a little more which chips that are relevant.
To be able to look into the right data-sheet, while reviewing.
Link to data-sheet would be nice too.

Thanks in advance,
	Sam
Alexandre Belloni Feb. 28, 2019, 8:52 p.m. UTC | #2
On 28/02/2019 19:21:19+0100, Sam Ravnborg wrote:
> Hi Claudiu
> 
> On Wed, Feb 27, 2019 at 04:24:11PM +0000, Claudiu.Beznea@microchip.com wrote:
> > From: Claudiu Beznea <claudiu.beznea@microchip.com>
> > 
> > Hi,
> > 
> > These patches adds support for SAM9X60's LCD controller.
> Can you elaborate a little more which chips that are relevant.
> To be able to look into the right data-sheet, while reviewing.
> Link to data-sheet would be nice too.
> 

sam9x60 is the chip name (i.e. x is not a wildcard). I don't think the
datasheet is finished/public yet.
Sam Ravnborg Feb. 28, 2019, 9:13 p.m. UTC | #3
Hi Alexandre.

> > > 
> > > These patches adds support for SAM9X60's LCD controller.
> > Can you elaborate a little more which chips that are relevant.
> > To be able to look into the right data-sheet, while reviewing.
> > Link to data-sheet would be nice too.
> > 
> 
> sam9x60 is the chip name (i.e. x is not a wildcard). I don't think the
> datasheet is finished/public yet.

Thanks. I will take a look at the patches but not knowing
the specifics of the implementation/IP will makes this less valueable.

	Sam
Claudiu Beznea March 1, 2019, 10:09 a.m. UTC | #4
On 28.02.2019 23:13, Sam Ravnborg wrote:
> Hi Alexandre.
> 
>>>>
>>>> These patches adds support for SAM9X60's LCD controller.
>>> Can you elaborate a little more which chips that are relevant.
>>> To be able to look into the right data-sheet, while reviewing.
>>> Link to data-sheet would be nice too.
>>>
>>
>> sam9x60 is the chip name (i.e. x is not a wildcard). I don't think the
>> datasheet is finished/public yet.
> 
> Thanks. I will take a look at the patches but not knowing
> the specifics of the implementation/IP will makes this less valueable.

At this moment, as Alexandre specified, the datasheet is not published.

Thank you,
Claudiu Beznea

> 
> 	Sam
>