AM43x has a few IP's that are not present in AM335x,
1. qspi
2. hdq1w
3. vpfe (two instances)
4. pka
5. des
6. rng
7. synctimer
In addition it has a few new instances of existing IP's,
1. timer8-11
2. ehrpwm3-5
3. spi2-4
Also a different pruss interconnect.
Update hwmod with the above details an
AM43x PKA module has sysconfig bitmap different from that of the
existing available types, hence add a new one.
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/omap_hwmod.h | 5 +
arch/arm/mach-omap2/omap_hwmod_common_data.c | 6 ++
2 files changed, 11 insertions(+)
di
Build AM43x power domain, clock domain and hwmod data.
Many of AM43x IP's and interconnects are similar as that in AM335x,
hence AM335x hwmod data is being reused with necessary changes.
Earlier the plan was to reuse AM335x specific PRCM code, but as AM43x
PRCM is much similar to OMAP4/5, AM335x
From: Ambresh K
Add the data file to describe clock domains in AM43x SoC.
Signed-off-by: Ambresh K
Signed-off-by: Afzal Mohammed
---
Note: domain operations to be used would have to modified as mentioned in
the cover letter
arch/arm/mach-omap2/clockdomain.h | 1 +
arch/a
Update AM43x CLKCTRL, RSTCTRL, RSTST offsets, clockdomain & ocpif clk
that differ with AM335x at runtime. This helps in resuing much of the
AM335x hwmod data's for AM43x.
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 110 +
1 file chan
From: Ambresh K
Initialise AM43x HWMOD, powerdomains and clockdomains.
Signed-off-by: Ambresh K
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/io.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-omap2/io.c b/arch/arm/mach-omap2/io.c
index 7325ba6..901acf6 10064
From: Ambresh K
Reuse OMAP4 operations on AM43x.
Signed-off-by: Ambresh K
Signed-off-by: Afzal Mohammed
---
Note: This may have to modified as mentioned in the cover letter.
arch/arm/mach-omap2/omap_hwmod.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-om
From: Ambresh K
Add the data file to describe all power domains in AM43x SoC.
Signed-off-by: Ambresh K
Signed-off-by: Afzal Mohammed
---
Note: domain operations to be used would have to modified as mentioned in
the cover letter
arch/arm/mach-omap2/powerdomain.h | 1 +
ar
Add AM43x CMINST, CDOFFS, RM_RSTST & RM_RSTCTRL definitions - minimal
ones that would be used.
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/prcm43xx.h | 148 +
1 file changed, 148 insertions(+)
create mode 100644 arch/arm/mach-omap2/prcm43xx.h
d
Hwmod common to AM43x & AM335x has some of fields different (CLKCTRL,
RSTCTRL, RSTST, ocpif clk and clockdomain). It is now updated based
on SoC detection at run time, hence remove statically initialized
entries.
Signed-off-by: Afzal Mohammed
---
arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 79 -
From: Ankur Kishore
Most of the AM43x CM reg address offsets are with MSB bit '1' (on
16-bit value) leading to arithmetic miscalculations while calculating
CLOCK ENABLE register's address because cm_inst field was a type of
"const s16", so make it "const u16".
Also modify relevant functions so a
Update AM335x CLKCTRL, RSTCTRL, RSTST offsets, clockdomain & ocpif clk
that differ with AM43x at runtime. This is being done so that static
initialization of these details (which are different between AM335x
and AM43x) can be removed to aid in sharing of hwmod data between both
platforms as much as
AM335x & AM43x have most of the interconnects, IPs similar. Instead of
adding new hwmod data for AM43x, reuse AM335x hwmod data as much as
possible.
In the hwmod entries that could be reused on AM43x, major changes are
in register offsets and different ocpif clock for most of peripherals
that come
Hi,
AM43x PRCM support (excluding clock tree) is being added with this
series. AM43x reuses most of the IP's from AM335x, as that is the
case, it was felt that reusing AM335x code as much as possible for
AM43x is better - it also helps to keep LOC less.
This RFC is being
* Felipe Balbi [130710 09:18]:
>
> On Wed, Jul 10, 2013 at 07:07:04PM +0300, Felipe Balbi wrote:
> > how about something like below ? It makes omap_device/hwmod and
> > pm_runtime agree on the initial state of the device and will prevent
> > ->runtime_resume() from being called on first pm_runtim
* Rajendra Nayak [130710 23:25]:
> On Wednesday 10 July 2013 07:56 PM, Tony Lindgren wrote:
> >
> > Felipe is right, looks like all we need is to check if context is
> > initialized or not. So no need for mach-omap2/serial.c or hwmod tinkering.
> >
> > After that having DEBUG_LL and cmdline with
On Wednesday 10 July 2013 07:56 PM, Tony Lindgren wrote:
> * Kevin Hilman [130710 01:29]:
>> Felipe Balbi writes:
Right, but calling serial_omap_restore_context() even when the context
is not lost, should not ideally cause an issue.
>>>
>>> it does in one condition. If context hasn
* Linus Walleij [130710 13:42]:
> On Thu, Jun 27, 2013 at 4:01 PM, Grygorii Strashko
> wrote:
>
> > I think, In the future the OMAP pinctrl configurations would be manged in
> > more flexible way then now (thanks to "pinctrl PM helpers" and you;))
> > - "Idle" state will be splitted to "Idle"/"s
On Wed, Jul 10, 2013 at 09:36:24PM +0530, a-bin...@ti.com wrote:
> From: Amarinder Bindra
>
> OMAP's hs_mmc driver is used for MMC controller operation on many
> omap2plus SoCs (OMAP2430, OMAP3, 4, 5 and AM335x).
>
> Considering that the device tree entries are already present for these,
> allow
On 21:36-20130710, a-bin...@ti.com wrote:
> From: Amarinder Bindra
>
> OMAP's hs_mmc driver is used for MMC controller operation on many
> omap2plus SoCs (OMAP2430, OMAP3, 4, 5 and AM335x).
>
> Considering that the device tree entries are already present for these,
&
On Thu, Jun 27, 2013 at 4:45 PM, Tony Lindgren wrote:
> The off mode bits can be enabled continuously, the mux hardware
> automatically sets them. So sounds like you don't need any
> separate "idle" "sleep" and "off" states, the following should
> do:
>
> "default" (or "static") static pins that
On Thu, Jun 27, 2013 at 4:01 PM, Grygorii Strashko
wrote:
> I think, In the future the OMAP pinctrl configurations would be manged in
> more flexible way then now (thanks to "pinctrl PM helpers" and you;))
> - "Idle" state will be splitted to "Idle"/"sleep"
> - "default" state will be splitted to
Dear Wolfram Sang,
> Since commit ab78029 (drivers/pinctrl: grab default handles from device
> core), we can rely on device core for setting the default pins. Compile
> tested only.
>
> Acked-by: Linus Walleij (personally at LCE13)
> Signed-off-by: Wolfram Sang
Something like that is already i
Hello My Dear,
How are you today? I hope fine,I came across your contact today while browsing
looking for reliable friend and i became interested, my name is miss Famatta. I
wish to have you as a friend, if you care. I have important reasons to request
your interest for a serious relationship, i
On Wed, 10 Jul 2013, Roger Quadros wrote:
> Some platforms e.g. ehci-omap can generate an interrupt
> (i.e. remote wakeup) even when the controller is suspended i.e.
> HW_ACCESSIBLE is cleared.
>
> Introduce a flag "has_wakeup_irq" in struct usb_hcd to indicate
> such cases.
>
> We tackle this c
On Wed, 10 Jul 2013, Roger Quadros wrote:
> Call ehci_suspend/resume() during runtime suspend/resume
> as well as system suspend/resume.
>
> Use a flag "bound" to indicate that the HCD structures are valid.
> This is only true between usb_add_hcd() and usb_remove_hcd() calls.
>
> The flag can be
On Wed, 10 Jul 2013, Roger Quadros wrote:
> Some platforms e.g. ehci-omap can generate an interrupt
> (i.e. remote wakeup) even when the controller is suspended i.e.
> HW_ACCESSIBLE is cleared.
>
> Introduce a flag "has_wakeup_irq" in struct usb_hcd to indicate
> such cases.
>
> We tackle this c
On Wed, Jul 10, 2013 at 02:59:04PM +0200, Pali Rohár wrote:
> Other secure functions omap_smc1() and omap_smc2() calling instruction smc #0
> but Nokia RX-51 board needs to call smc #1 for PPA access.
>
> Signed-off-by: Ivaylo Dimitrov
> Signed-off-by: Pali Rohár
> ---
> arch/arm/mach-omap2/oma
Call ehci_suspend/resume() during runtime suspend/resume
as well as system suspend/resume.
Use a flag "bound" to indicate that the HCD structures are valid.
This is only true between usb_add_hcd() and usb_remove_hcd() calls.
The flag can be used by omap_ehci_runtime_suspend/resume() handlers
to a
Some platforms e.g. ehci-omap can generate an interrupt
(i.e. remote wakeup) even when the controller is suspended i.e.
HW_ACCESSIBLE is cleared.
Introduce a flag "has_wakeup_irq" in struct usb_hcd to indicate
such cases.
We tackle this case by disabling the IRQ, scheduling a
hub resume and enabl
In order to support wake up from suspend use the pinctrl
framework to put the USB host pins in IDLE state during suspend.
CC: Samuel Ortiz
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 22 ++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/
Add the Idle state pins for USB host and enable WAKEUP on
DIR, DAT0-3, so that the PHY can wakeup the OMAP SoC from
sleep on any USB activity (e.g. remote wakeup or connect/disconnect).
Signed-off-by: Roger Quadros
---
arch/arm/boot/dts/omap3-beagle-xm.dts | 29 +++--
1
We no longer need to be initialized in any particular order
so move driver initialization to the standard place i.e. module_init()
CC: Samuel Ortiz
Signed-off-by: Roger Quadros
---
drivers/mfd/omap-usb-host.c | 23 +++
drivers/mfd/omap-usb-tll.c | 20 ++-
To ensure hardware context is restored while resuming from
OFF mode we need to enable the Hardware SAR bit for the
USB Host power domain.
Signed-off-by: Roger Quadros
---
arch/arm/mach-omap2/powerdomains3xxx_data.c |8 +---
1 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/a
Hi,
This series implements suspend/resume for the OMAP EHCI host controller during
runtime idle. This will cause its parent, the OMAP USB Host Module as well
as the USB TLL Module to be put in suspend and hence allow the USB power domain
to be put in a lower power state. Then we no longer prevent
Hi,
On Wed, Jul 10, 2013 at 07:07:04PM +0300, Felipe Balbi wrote:
> how about something like below ? It makes omap_device/hwmod and
> pm_runtime agree on the initial state of the device and will prevent
> ->runtime_resume() from being called on first pm_runtime_get*() done
> during probe.
>
> Thi
Hi,
On Wed, Jul 10, 2013 at 07:26:34AM -0700, Tony Lindgren wrote:
> * Kevin Hilman [130710 01:29]:
> > Felipe Balbi writes:
> > >>
> > >> Right, but calling serial_omap_restore_context() even when the context
> > >> is not lost, should not ideally cause an issue.
> > >
> > > it does in one con
From: Amarinder Bindra
OMAP's hs_mmc driver is used for MMC controller operation on many
omap2plus SoCs (OMAP2430, OMAP3, 4, 5 and AM335x).
Considering that the device tree entries are already present for these,
allow the driver to be built using the config ARCH_OMAP2PLUS rather
than individuall
Since commit ab78029 (drivers/pinctrl: grab default handles from device core),
we can rely on device core for setting the default pins. Compile tested only.
Acked-by: Linus Walleij (personally at LCE13)
Signed-off-by: Wolfram Sang
---
drivers/mmc/host/mvsdio.c |6 --
drivers/mm
Since commit ab78029 (drivers/pinctrl: grab default handles from device core),
we can rely on device core for setting the default pins. Compile tested only.
Acked-by: Linus Walleij (personally at LCE13)
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-omap.c | 13 -
1 file c
Barry,
> >> On Mon, Jul 8, 2013 at 10:31 AM, Barry Song <21cn...@gmail.com> wrote:
> >>> hi Ohad/all,
> >>> i am trying to find some real users of rpmsg, here i only get
> >>> samples/rpmsg/rpmsg_client_sample.c, does it mean other real drivers
> >>> are out of mainline?
> >>
> >> Yes
> >>
> >>> w
With the lists this time
On Wed, Jul 10, 2013 at 6:17 PM, Ohad Ben-Cohen wrote:
> The following changes since commit 9e895ace5d82df8929b16f58e9f515f6d54ab82d:
>
> Linux 3.10-rc7 (2013-06-22 09:47:31 -1000)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kern
* Kevin Hilman [130710 01:29]:
> Felipe Balbi writes:
> >>
> >> Right, but calling serial_omap_restore_context() even when the context
> >> is not lost, should not ideally cause an issue.
> >
> > it does in one condition. If context hasn't been saved before. And that
> > can happen in the case o
On Wednesday 10 July 2013 04:57 PM, Felipe Balbi wrote:
> On Wed, Jul 10, 2013 at 04:29:22PM +0530, Kishon Vijay Abraham I wrote:
>> commit 09fc7d (usb: musb: fix incorrect usage of resource pointer)
>> assumes musb core will always have only 2 resources. But for OMAP
>> platforms there can be 3 re
On 07/10/2013 03:24 PM, Tony Lindgren wrote:
> * Roger Quadros [130710 05:16]:
>> Hi Tony,
>>
>> On 06/07/2013 11:50 PM, Tony Lindgren wrote:
>>> Hi all,
>>>
>>> Here are few patches to add support for SoC specific features
>>> to pinctrl-single. This is needed at least for omaps to support
>>> IO
* On RX-51 probing for acx565akm driver is later then for omapfb which cause
that omapfb probe fail and framebuffer is not working
* EPROBE_DEFER causing that kernel try to probe for omapfb later again which
fixing this problem
* Without this patch display on Nokia RX-51 (N900) phone not working
Other secure functions omap_smc1() and omap_smc2() calling instruction smc #0
but Nokia RX-51 board needs to call smc #1 for PPA access.
Signed-off-by: Ivaylo Dimitrov
Signed-off-by: Pali Rohár
---
arch/arm/mach-omap2/omap-secure.h |1 +
arch/arm/mach-omap2/omap-smc.S| 22
Closed and signed Nokia X-Loader bootloader stored in RX-51 nand does not set
IBE bit in ACTLR and starting kernel in non-secure mode. So direct write to
ACTLR by our kernel does not working and the code for ARM errata 430973 in
commit 7ce236fcd6fd45b0441a2d49acb2ceb2de2e8a47 that sets IBE bit is a
This patch adds RX-51 specific SMC support and sets IBE bit in ACTLR during
board init code for ARM errata 430973 workaround.
This is second version of patch which simplifing API and moving all board
functions to one file board-rx51.c. Wrapper around smc #1 instruction is in
omap-smc.S file becaus
* Tony Lindgren [130710 05:17]:
> * Kevin Hilman [130710 01:29]:
>
> If the problem is omap-serial.c idling things while earlycon is
> running, then omap-serial.c should be fixed.
If this is the case, then delaying the idling in omap-serial.c
should take care of the issue as earlycon gets disab
Hi,
On Wed, Jul 10, 2013 at 03:16:54PM +0300, Grygorii Strashko wrote:
> >Imagine the device is marked as suspended even though it's fully enabled
> >(it hasn't been suspended by hwmod due to NO_IDLE flag). In that case
> >your context structure is all zeroes (context has never been sa
* Roger Quadros [130710 05:16]:
> Hi Tony,
>
> On 06/07/2013 11:50 PM, Tony Lindgren wrote:
> > Hi all,
> >
> > Here are few patches to add support for SoC specific features
> > to pinctrl-single. This is needed at least for omaps to support
> > IO chain wake-up events from deeper idle states.
>
On 07/09/2013 10:41 PM, Felipe Balbi wrote:
Hi,
On Tue, Jul 09, 2013 at 09:59:28PM +0300, Grygorii Strashko wrote:
Imagine the device is marked as suspended even though it's fully enabled
(it hasn't been suspended by hwmod due to NO_IDLE flag). In that case
your context structure is all zeroes
* Kevin Hilman [130710 01:29]:
> Felipe Balbi writes:
>
> > Hi,
> >
> > On Mon, Jul 08, 2013 at 06:50:01PM +0530, Rajendra Nayak wrote:
> >> >> I wonder if this is because the timeouts get now initialized to 0
> >> >> instead
> >> >> of -1 for the serial driver?
> >> >>
> >> >>>
Hi Tony,
On 06/07/2013 11:50 PM, Tony Lindgren wrote:
> Hi all,
>
> Here are few patches to add support for SoC specific features
> to pinctrl-single. This is needed at least for omaps to support
> IO chain wake-up events from deeper idle states.
>
> With this patch series, device drivers can re
On Wed, Jul 10, 2013 at 04:29:22PM +0530, Kishon Vijay Abraham I wrote:
> commit 09fc7d (usb: musb: fix incorrect usage of resource pointer)
> assumes musb core will always have only 2 resources. But for OMAP
> platforms there can be 3 resources (2 irq resource and 1 iomem
> resource). Fixed it her
commit 09fc7d (usb: musb: fix incorrect usage of resource pointer)
assumes musb core will always have only 2 resources. But for OMAP
platforms there can be 3 resources (2 irq resource and 1 iomem
resource). Fixed it here.
Signed-off-by: Kishon Vijay Abraham I
---
Changes from v1:
*) Removed redun
On Tue, Jul 09, 2013 at 11:04:23AM -0500, Nishanth Menon wrote:
> On 07/09/2013 10:29 AM, Mark Brown wrote:
> >This seems like something we should be able to cope with by for example
> >adding a bus for the custom PMIC interface or otherwise finding a way to
> I had considered introducing a custo
Felipe Balbi writes:
> Hi,
>
> On Mon, Jul 08, 2013 at 06:50:01PM +0530, Rajendra Nayak wrote:
>> >> I wonder if this is because the timeouts get now initialized to 0
>> >> instead
>> >> of -1 for the serial driver?
>> >>
>> >
>> > You meant initialized to -1, right? Ther
This patch adds
- HS USB nodes
- phy nodes
- usb control module nodes.
Signed-off-by: George Cherian
---
changes from v2
change synopsis to snps
use simple node names
add both USB and PHY instances
add usbctrl node
changes from v1
renamed synopsis to snps
removed flag
Hi Benoit,
2013/7/6 Javier Martinez Canillas :
> On Fri, Jul 5, 2013 at 11:38 PM, Enric Balletbo i Serra
> wrote:
>> IGEP Processor Boards based on OMAP3 have the MCBSP2 connected to the TDM
>> interface. The kernel should configure the pinmux for these pins in order
>> to get TWL4030 codec worki
The following changes since commit ddcf6600b133697adbafd96e080818bdc0dfd028:
Merge tag 'hwmon-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging (2013-07-03
19:56:35 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/
The GPADC is general purpose ADC found on TWL6030,
and TWL6032 PMIC, known also as Phoenix and PhoenixLite.
The TWL6030 and TWL6032 have GPADC with 17 and 19
channels respectively. Some channels have current
source and are used for measuring voltage drop
on resistive load for detecting battery ID
GPADC is the general purpose ADC present on twl6030.
The dt data is interrupt used to trigger end of ADC
conversion.
Signed-off-by: Oleksandr Kozaruk
---
arch/arm/boot/dts/twl6030.dtsi |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/twl6030.dtsi b/arch/arm/boot/dts
Hello,
This is version 2 - the driver put in drivers/iio, and
converted using iio facilities as suggested by Graeme.
TWL603[02] GPADC is used to measure battery voltage,
battery temperature, battery presence ID, and could
be used to measure twl603[02] die temperature.
This is used on TI blaze, bl
65 matches
Mail list logo
